We have an early fix for the “total number of children” error already on our beta tester server latest.speckle.dev (let me know if you’d like an invite 
)
When it passes our internal testing, it will make its way to speckle.xyz.
2 Likes
No hurry,
I just want to miss it 
On the other hand,
what I currently did by activating Betas in Manager is just the local part,
like Beta Managers and access to Connector Betas ?
So it would be a completely different/separate Server (?) looking basically
the same, just with pre release server stuff running for testing (?)
would make my humble unreleased testing more complete ?
Hope I will manage the twin Setup,
but Yes, I would like to get an invitation 
1 Like
Yes, exactly. We release new “Web” features on this server first and test them there. Once testing is done, they go live on the public “Speckle.xyz” server.
That will give you access to Beta releases of Manager. We are constantly improving manager as well. So it works in different setups. It is not related to connectors.
You can already access pre-release versions of our connectors by going to the versions tab on the connectors page in Manager.
2 Likes
Thanks,
yes, I use these already.
But I thought I can see them only because I have Betas activated.
But now I have tripple Beta status
2 Likes
If you check your profile, you now officially have a Tripple Beta badge. Thanks, from all of us, for all the testing you’ve been doing!
3 Likes
Great,
so now the one with the least knowledge has the biggest badge 
1 Like
OK, not unexpected, but I can confirm that Blender Connector Installation …
and my IFC, on Blender Dev Server, works by Blender Receive,
also on Windows 11 for me …
2 Likes
Hmmh, but the latest Blender 2.12.0 Beta Connector is broken for my IFC Stream.
The Warning was a bit longer this time.
Went back to 2.11.3 and it works again …
1 Like
Is this ifc file in latest.speckle.dev? If yes can you share the stream url? If not, please upload the ifc file to latest and try receiving from there.
If it still doesn’t work, please share the ifc file with us.
Yes,
Jedd has it already and I sent the link to you now via PM.
Will try to upload again later.
Is the 1st repair for my IFC already on XYZ now ?
1 Like
Hey zoomer,
Link you shared is on XYZ which confirms my suspicions. We had an issue with IFC upload service which is fixed on “latest” now. it will make its way into XYZ in the next release. In the meantime try uploading same ifc file to “latest” and receive that on blender. Let me know if it works.
1 Like
I can reproduce an issue when receiving some of our internal IFC commits that have with int values larger than int32.
When setting the custom object properties on received blender objects, I was getting this exception
OverflowError: Python int too large to convert to C int
Unsure if this is an issue anyone else has come across. but should be a quick change to simply ignore attaching any property to the blender object that is out of range.
My last experience is,
My IFC upload to XYZ did not stream down to Blender with 2.11.3.
Jedd fixed it on “latest” Server.
My IFC re-upload to “latest” did stream down to Blender with 2.11.3.
When 2.12.0 Beta came out, I tried downstream again and it did not work,
with a longer warning message.
Went back to 2.11.3 and it works again.
So I would expect it is about the Connector Beta ?
Does that mean my IFC is corrupt with too large numbers inside,
or that the uploader converts to too large numbers.
If you need, I can mail the IFC’s too you.
I exported as IFC 2x3, 4.0 and 4x1.
As BlenderBIM recommended using newest IFC versions, I just tried
4x1 version first. And as it worked for my own usage internally between
Bricscad, Vectorworks and BlenderBIM so far without problems,
I also used the 4x1 version here for Speckle testing.
Yep! ok this is a nice catch.
I can reproduce the issue on 2.12.0-beta
The problem is related to the attaching of custom properties of types that blender doesn’t support.
I’ve just implemented a fix which will skip the attaching of any property that fails to attach.
Just testing, your geometry receives fine.
My guess is that 2.11 is unaffected, simply because the problematic objects weren’t directly converted (in 2.12 we’ve made some improvements to how nested objects are converted).
I’ll push a 2.12.1-beta shortly, with this fix.
1 Like
Unlikely that I attach custom properties in BIM intentionally.
But yes, in Bricscad V23 there were some new Classification Options,
with a warning that these are not backward compatible, which I used.
As I had to go back to V22 for editing, maybe I even corrupted these
this way, but did not notice problems locally.
And thanks for the fix.
Do I still need to upload the IFC again (on the Beta Server) or was it all about
the Connector only ?
And generally, when upload options like IFC get updated on Servers over time,
this means that we also should re-upload our direct upload files from time to time ?
There’s nothing wrong with your IFC or Speckle Objects. Simply, there are a few property types that IFC & Speckle supports, that Blender doesn’t support attaching as custom properties.
Those properties are visible here, and accessible via python scripting.
It looks like blender only supports the following types: int, float, string, int[], float[]
With my fix, any property with unsupported types will now simply be ignored, instead of it causing the whole object to fail to be converted. 
e.g. I see some polar coordinates (int[][]) fail to attach.
If you really need those properties, you can always inject a python receive script to re-attach those properties see Get window dimensions in Blender - #5 by gokermu
But most users just care about getting their geometry into Blender, the properties are a 
on top.
This would be a fix just to the Blender connector
Thanks !
Found your Connector Update and installed. It is loading fine now.
And I see I have Objects with names.
I just miss the hierarchies.
E.g. there are 3-4 “Empties”, from my BIM Stories, but the Objects
are not parented under these like it is for the most top parent : Site.
Same for some Objects in Blocks/Symbols, their Empties are not above
but at the same level as the child Objects.
I get these hierarchies in BlenderBIM, which allows faster Visibility switching
by Story. Would that be tedious to implement in Speckle ?
BlenderBIM
Speckle
1 Like