This age old problem still persists. Can you please fix this once and for all?
The simples workaround is to script SplitDisjoinedMesh into the boolean operation and then join back up the result
@piac even a simple fix like that would go a long way for us, so we don’t have to manually fix this every time.
Here is an old example:
MeshBooleanDifference Disjoined mesh issue.3dm (312.3 KB)
And here is a new example:
MeshBooleanDifference Disjoined mesh issue 2.3dm (277.2 KB)
More on the topic here:
@pascal and @piac can you take a look at this?)
I think it is about hight time you fix the mesh boolean issue with disjoined meshes:
This should seriously be easy to fix and has been reported too many times.
Having to split disjoined meshes before mesh boolean and then manually delete the objects within the boolean and rejoin shouldn’t be necessary.
This is supereasy to recreate, but here is a file none the less:
MeshBooleanDifference Disjoined mesh issue.3dm (312.3 KB) …
Yes. I am aware of this problem. We are rewriting all the code. So it takes time. I’ve added
for Robert McNeel & Associates
Yeah, good luck on that.
Make sure you cover overlapping geometries too then. So if we boolean a big sphere away from a small sphere, that is fully enclosed by the big sphere then the small one is deleted.
Today nothing happens. (it just deletes the big sphere)
sample.3dm (115.4 KB)
This is a sample of what you asked.