Hello everyone and @Petras_Vestartas!
Together with my students, we are preparing a parametric pavilion for assembly and encountered a problem at the nesting stage. Rhino freezes and doesn’t respond. As an experiment, I waited for several days and tested it on fairly powerful computers. But unsuccessfully.
Contours for nesting consist of lines and arcs. I converted arcs to polylines, but the result is the same.
Tell me what could be the problem?
Just in case, I’ve attached the Grasshopper definition to the post.
I’ve tried various things including reducing ‘Rotations’ to 2, surrounding rectangles and partitioning but my laptop overheats so I kill Rhino before anything completes. The basic problem appears to be so many parts (1144). I don’t want to fry my laptop.
It works OK with 50 or 100 surrounding rectangles but struggles with more than that. Using raw parts instead of rectangles, it fails sooner. Too bad.
Rajeev, indeed, your solution works. I changed it a little so that there was less geometry distortion and to maintain a minimum gap between the parts.
If I’m right, the rendering speed was affected by the “Rotation” parameter, not the complexity of the geometry. I set its value as 360, but you set it to 3. Now I set the Rotation value to 6.
I left the rest of the parameters as in your example. On my computer, the calculation lasted 1 hour and 20 minutes.
Thank you, Rajeev!
Also thanks to Joseph_Oster and Petras_Vestartas for participating in solving my problem. Joseph_Oster, I hope everything is fine with your laptop
While my topic was hanging here on the forum, I was looking for alternative solutions using third-party software. Something interesting happened with NestFab. If you are interested, I can tell you here in a separate message.
The undoubted advantage of OpenNest is that it is a plugin for Grasshopper and produces Transformations as a result. How to get Transformations without OpenNest? Of course, this is a “crutch”, but it works:
In Grasshopper, add “anchors” to each part. Anchors must be Polyline. A polyline must consist of two lines. The line directions determine the direction of the XY axes, and the length determines the part number or data tree path. For example, part {0,1} with lengths 10 and 11 or part {7, 3} with lengths 17 and 13, etc.
Next, you can use any nesting program that accepts different types of geometry, such as cutting and engraving. I used NestFab, 7 day trial. It’s a good program, I would even buy it if it weren’t for its high cost.
So, you now need to distribute the parts and export just the engraving layer.
Then import the geometry into Rhino and compare the original polyline anchors and those that were imported. Convert Polylines to Planes and their lengths to paths. Profit.
