Show messages: All
1-6
7-9
From: Michael Gibson
Hi jki,
re:
> In one step, adding a detail the solid is "broken" to a joined surface... despite the operation does NOT
> affect the areas which are now marked as naked edges.
Non-manifold or self intersecting geometry can affect operations on other areas of the model too. Particularly mechanisms that involve traversing connected faces.
> So it means there is something wrong with faces... Is there a way how to identify it and prevent such situation?
Is this on the same model that you posted above? Because like I wrote above, the thing that is wrong there is having places where 4 surfaces are touching at a single edge making a non-manifold structure.
> Is there an the explanation why in some cases the "boolean Union" end up as Boolean Difference?
One of the things that non-manifold/self-intersections can mess up is the algorithm that identifies which side of a closed skin is the outside.
If it ends up classifying the wrong side as the outside it can invert which pieces are kept and discarded in booleans.
- Michael
From: Michael Gibson
Hi Larry,
re:
> If so, would it be reasonable (possible) for MOI to warn when an operation produces object(s) whose
> "type" is lower in the hierarchy than they were when the operation commenced?
It would be hard to do this for everything because there are some functions (Edit > Separate, Trim) where their job is specifically to produce a "lower" result.
It could be good for booleans though.
The complication is that there is not an established UI mechanism for reporting a command specific error.
I have some ideas on making a command "epilogue" dialog that could work for that, I hope to be able to experiment with it in v6.
Thanks,
- Michael
From: Larry Fahnoe (FAHNOE)
Thanks Michael,
Sounds like this would make a good wish-list item combined with your command "epilogue" dialog to check for degraded object types from certain ops like the booleans.
--Larry
Show messages: All
1-6
7-9
