Hi, I managed (by observing other scripts on the forum) to create a function that flattens 3D objects, but they are not parallel to the x or y axis (it does not matter which axis). Can someone help me set them parallel to the axis?
Thank you for your answer. Iâm sorry I wasnât specific enough in my description. When I wrote flattened objects, I didnât mean that they should be surfaces, but still 3D objects placed on the xy surface at the same level. So the script I sent rotates 3D objects and places them on the xy surface, and thatâs how I would like it to be. The problem is that 3D objects are placed at different angles to the x and y axes and I would like them to be parallel to the x axis.
Sounds like you want OpenNest for these shelves?
This is R7 OpenNest:
Wow. Itâs amazing. Yes, ultimately I wanted to connect it to OpenNest. As always, there are a few buts 
I tried this on R8, had to download/install OpenNest when prompted, and it worked.
That gets into the weeds of OpenNest, which I donât want to do today. You will have to understand the code. OpenNest works only with curves, not thick parts.
OK, I added the yellow group to avoid extruding faces. Not sure itâs optimal.
P.S. On closer inspection I can see that parts are below the âsheetâ surfaces. I was hasty and thought some might be above and some below because of how I picked the reference planeâŠ
P.P.S. This purple group flips parts over so they are on top of the âsheetsâ, but again, I donât know why they are all the same since reference planes from EvalSrf are arbitrary?
I tried as you did in R8 with ON 1.5 and 1.51 but an error message appeared.
â1. Solution exception:Could not load file or assembly âOpenNestLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=nullâ. Could not find or load a specific file. (0x80131621)â
When I tried to connect to ON 2.0, it didnât work either.
However, I tried your script in R7 and ON 1.51 and it works great. Itâs exactly what I was looking for. Thank you for adding additional features. Maybe when the new version ON 2.1 comes out, it will be easier to connect 3D objects because in version 1.51 there were no problem.
Now I canât open any of the GH files I posted in R8. I see this (which appears to show OpenNest2 already installed):
When I click âDownload and Installâ, it shows this:
Wait, I just tried R8 again and it opened and worked fine:
But I canât repeat it reliably - sometimes yes, sometimes no 
grrr⊠R8 is such a mess! So I tried using OpenNest2 components but havenât paid attention to changes so it fails with two errors:
- Invalid cast: Curve » nest_geo
- Solution exception:Object reference not set to an instance of an object.
I HATE being helpless 
I donât know if these threads are useful, I havenât read them yet: (What a PITA!)
I still havenât read these pages in detail but messed around with OpenNest2 and got something. Looks like trash to me.
This is R7 version âcâ (posted previously):
And this is the same code in R8 adapted to OpenNest2:
Is this any way to do an upgrade? NO
I am working on this. Soon will be fixed. I will highly likely completely remove transformation matrix or keep both. But for sure wording like âTrashâ should be avoidedâŠ
Where never is heard a discouraging word
And the sky is not clouded all day.
What do you call it? Some people get offended by the old programming term GIGO, but that doesnât apply here because the same input works fine in R7 OpenNest.
Could you just simply ping me to the post once you see it? I can answer myself, specially in the case like this when i need to transfer code from R7 to R8âŠ
I just realized something that might be very important? Part of the problem I am seeing has nothing to do with OpenNest Itâs strictly a difference between R7 and R8. To prove and demonstrate that, I removed OpenNest from R7 and R8 versions I posted this morning.
This is the R7 version - note the result of Orient: (yellow group)
This is the R8 version - note the result of Orient: (yellow group)
I donât know if it explains everything but clearly, this is yet another anomaly (flaw?) with R8.
P.S. Actually, both these versions of GH are identical, now that OpenNest was removedâŠ
Changed the code so that transforms works in the same order.
Since everyone is using those transforms anyway, I will add an option to geometry for âattributesâ, so that this GH wiring wont be needed.
Seems evaluate component is giving different results between R7 and R8.
Can be that some updates where made on BRep on Rhino8.
To be honest, if this shelf would be a serious production, the developer would need to create his own frame per panel. Else it is a bit of a guess. For example a rhino object would have a user string that has a defined frame or any other class like representation of a panel element.
