Karamba v2.2.0 Assemble Model issue

Grasshopper Karamba3D
1

I have a really large GH script ( ~ 15000 components) with Karamba components in it.
Since I update Karamba to v2.2, if I have too many Assemble Model Components active at the same time, then rhino will be frozen, showing as not responding and cannot get out of that state. If I have them all disabled from the beginning and enable them one by one then it would be fine up until a certain points, it will be lagging again.
This never happens on Karamba v1.3, even with structure that is 5-10 times bigger than this test.
Somehow when I internalize this component the GH file gets really big so here is the google drive link for it:

Also that one is from karamba v1.3 because when I tried to internalize data on v2.2 Rhino got frozen.
Edit: My PC has i9-9900, 64GB RAM, RTX2080 so it should be enough to run this.

2

Hi, your script with internalized geometry is over 160mb. This would be impossible to handle. Can you send your script with the rhino geometry and a simplified version of your script?

3

Even with just the geometry it would be over 120mb, mostly comes from the load (50 branches, total 399 items, mesh-load mostly) so if you want it I can upload them

4

Hi, you should still upload, as we cannot troubleshoot your current file that has internalised geometry of 120mb.

5

Hi Matthew,
Thank you for your response. Attached is Rhino Geometry but I don’t think it carries any information for loads, joins…?
KarambaIssue.3dm (769.6 KB)
Also the link below is the assemble model component with internalized data for the above geometry. This is the smallest model I could do and normally our models are easily 20 times bigger than this

6

Hi, sorry for the late reply. Are there still elements in the grasshopper script internalised? I just see the Assemble model component when I open the file

7

Hi Matthew,
I’m not sure if I understand your question, but in the script I sent there is just 1 internalized assemble model component. We have at 4-5 of this component in our script but the input data structures are very similar to each other. Thanks

8

The script does not load with the internalised geometry, it would be good if you can provide the original script that references the rhino geometry

In my experience, internalised geometry slows down the processing of grasshopper scripts dramatically

9

I downloaded the script from that link and still can see all internalized geometries so I’m not sure why it doesn’t show up for you. As for the original script, we have custom components that pop up a form for user to specify the geometries (i.e number of bay, type of roof, size of each elements…) and then create all of those geometries using another custom component. What would be the best way to upload that? thanks

10

Hi, please write us an email at info@karamba3d.com