Compare Utility and Helical Sweeps

Not on helical, but I have on other algorithmic geometry. My guess is that geometry compare attempts a boolean function between the models to show what has changed. Just like when we try to combine-add/subtract two bodies and it fails due to a zero-thickness geometry error, I suspect that geometry-compare fails due to the same reason (because in the background it attempts the same boolean operation to derive the resulting difference). Think drawing sections that fail - attempt the same cut in the assembly, and it will fail (in my admittedly limited experience - check it out for yourself. Things may have changed). With Swx, in my experience, it all goes back to the root processes used behind-the-scenses to generate the function. Ed