One thing is Rhino allowing me to produce bad results, another is Rhino itself making bad results for me. [quote=“Gijs, post:10, topic:96525”]
IMO it should not be that difficult to check for errors caused by solid edit tools. When things go wrong they either fail completely or you get very dense surfaces in the result or the bad edges like in the example posted by Martin.
Yeah it’s very simple of your model is also very simple. The problem is when you try to edit something like an internal rib/boss height in a fully featured part for molding (made out of tens or hundreds of surfaces). And you are looking/editing at that part with a bunch of other parts visible at the time. Having isoparms visible in that simulation would lot let you see anything.
Most of the bad decisions of McNeel come from “This works fine in my test file of 2 cubes and a cylinder”.
In real production workflows SolidEditing is a model destroyer. I’d love McNeel to address it. Tools like Boolean give you warnings when results are out of tolerance. This tool can make a complete mess and say nothing about it. This is careless work.