Boolean Intersection Issue.

Hi All

I've developed a component that takes a series of volumes and calculates all the possible intersections amongst the volumes. The problem I'm running into is, if the volumes are generated in grasshopper, they boolean code reacts in an unusual way. If the volumes are generated through the rhino UI the code act as intended. I've tried trouble shooting this in a few different ways but can't find a work around. Does anybody have insight as to why this may be happening? The input volumes are closed skewed (6 sided) boxes.

Thanks,

[C]

Replies to This Discussion

Permalink Reply by David Rutten on October 16, 2013 at 3:57pm

Have you checked the normal directions of the boxes? If they're closed they should be oriented correctly, but maybe there's a bug there.

David Rutten

david@mcneel.com

Seattle, WA

Permalink Reply by Charles Portelli on October 16, 2013 at 4:15pm

Hi David, Thanks for the quick reply.

The volumes are closed and the normals point in the appropriate direction. I uploaded a rhino file and gh file.

Cheers,

[C]

Attachments:

Intersecting_Volumes_01.3dm, 658 KB
Intersecting_Volumes_01.gh, 133 KB

Permalink Reply by Andy VanMater on October 22, 2013 at 4:08pm

I can't be sure but I do know that booleans fail all the time if you have whats called a non-manifold edge (2 exterior edges shared, or 3+ edges shared), as well as coincident exterior points like two box corners, co-planar faces can sometimes screw things up, or simply too many objects at once. I tried your script with simple boxes and it works great so I'm guessing its a geometry issue not a coding problem.

Permalink Reply by zadeira on July 21, 2015 at 10:39am