BooleanUnion behaving unexpectedly?

[CD_Lewis]

I didn’t recall using any tool that should have yielded a polysurface that wasn’t closed, but the “cap” command closed 74 polysurfaces and then the BooleanUnion succeeded.

Thanks!

For history on why I had 74 polysurfaces that needed to be capped, I’ve had to fall back on using Split because BooleanSplit didn’t seem to be doing what the instructions said:

Boolean Split joining cutting object to cut object

I am seeing the same thing. I select an object to split: [Select object to split] then I pick a cutting object [Select cutting object] but Rhino chooses to conduct BooleanUnion instead [Discover the cutting and split object have been booleanUnioned] … and discover as a bonus that Rhino has also conducted a split but it hasn’t split the target object but the cutting object: [Screenshot 2024-01-28 at 2.30.03 PM] I am having to spend a lot of time making extra copies of things to replace o…

I really appreciate the heads-up the Boolean was failing due to unnoticed open surfaces. Thanks again!