Hello, I discovered some strange behavior when using the BoundingBox component. Is there anyone who would explain to me what I’m doing wrong or where the mistake is? If I have curves that are planar and use the Scale NU component and I make a bounding box, then the Flat Box suddenly becomes a Box in some cases (if the scale is below 10 it is a Flat Box, if above 10 it is a Box), even though the curve is planar. What do you think about it? The gh script is only for a test, I use it in a much more complete definition.
BoundinBox_strange_behavior.gh (12.6 KB)
Interesting. I duplicated your definition and deleted the curve component after the circle is created.
I think I would not rely on the bounding box component since you already know the box is supposed to be a flat box and use a plane through shape component instead.
BoundingBox_strange_behavior.gh (32.4 KB)
Thank you for your quick reply. Yes, the component “Plane through shape” solves the “problem”. Great advice. I will use it for planar curve. But I would still like to know why it happened
Without being able to look into the definition via phone I would suggest checking is the height of the resulting box falls within tolerance. That could cause it to be flat.
Even if the planes are offset with values without decimals, some of the boxes are flat while others have edges with a length of zero units.
BoundingBox_strange_behavior.gh (36.5 KB)
I would not rely on the panel for showing what data you have if you pipe into it directly.
You’ll have to make sure you use enough places after decimal comma to be able to determine what the values are. The panel does a lot of simplification.
Here’s a stripped Rhino model and a Grasshopper definition:
array_ellipse.3dm (62.2 KB)
array_ellipse.gh (31.8 KB)
Select all ellipses with the gumball and scale in x direction. Some of the flat boxes turn into a box. It’s not just the panel thinking the box is too thin I’ll call it a flat box. Brep deconstruct shows six faces for some of the boxes…