This is one example of occasional incomplete intersections that I’ve seen both in Rhino and using Rhinocommon which baffles me slightly, since I would (granted, with my human brain) consider this to be a fairly rudimentary intersection - fairly simple horizontal and vertical surfaces.
that is one crappy surface you have there. i have no idea how you managed it that parts are folding in on each other you have boarders duplicating, you have to clean that up. use curveboolean on the duped boarder then planar surface, that should work again.
I’m assuming the crappy surface you’re referring to is the smaller planar brep? It was created programmatically using Rhinocommon, it’s an exploded surface that was part of a closed polysurface.
Thanks for the tips - I’ll look into incorporating that into my code.
What checks are you performing that signals to you that parts are folding in on each other? Can this be done using any Rhinocommon (v5) calls?
ic, well something happened there, when you use SolidPtOn and zoom in in that area, one solid point is moved slightly away causing the rendermesh to freak and overlap. the surface itself might not be folded but that will most likely be part of why intersect does not work. i guess its not the only issue, but at this point i will not scrutinize it any further, its clear that something is with your scripted surface rather than rhino having a bug.
Thanks for that, your clues led me to discover that the surface was created from an exploding a polysurface that was extruded from an closed curve which was the result of joining curves that overlapped each other (if that makes sense).
I’m assuming the crappy surface you’re referring to is the smaller planar brep? It was created programmatically using Rhinocommon, it’s an exploded surface that was part of a closed polysurface.
