SO yeahhhhhh
welcome to my life.
Try ungrouping it and unionizing in a different order. That’s how I get around those errors a lot of the time. If worse comes to worse (which it has for me), you’ll have to cut down on some of the very fine details.
Specifically the thing that is happening to your model is that the polygons are too small. Try sinking those negative parts in further to make the polygons larger.
Looks like you’re using a SpecialMesh with a Torso meshtype. As far as I know, that mesh type is legacy stuff.
Have you tried changing the mesh to something else?
It’s actually not a torso mesh – I put a block on a box of wedges and chopped the corners off. I actually got it working though. I’ve found that unions don’t work too well with UNIONED negations, so what I did was I just built the wedge thing, inverted it, and then unioned the whole thing together without using any negations.
Lesson learned: Don’t use negations.
that’s the opposite for me, I’ve been far more successful in negating objects than unionizing them.
We’re working on fixing these errors and know why occur but have not yet figured out the math to solve them. Our goal, if we handle these coincident cases correctly is to be completely rid of this dialog.
Could we potentially get a list of what causes the unsolvable solutions? It would really help us because we could avoid the scenarios until the bugs are patched.