When running this command on many selected mesh objects, in case there is a single bad mesh that cannot be split by this command, the entire operation fails with this message:
Rhino does not split/disjoint the meshes it actually could split. Since not all bad meshes are selectable by SelBad, sometimes it is hard to quickly find and identify the offender. Ideally this command would do the job on all that it can, then give a message that some could not be processed; better yet maybe there would be a way to highlight/select them?
not really, the problem is a single mesh that would not splitdisjoint causes all selected ones (100s sometimes) to fail, and going one by one is too much. Exploding all of them is too much also as it creates millions of individual face objects. SplitDisjoint command just should not be “lazy” and quit the whole thing when it encounters one input problem - instead it should ignore that one and move on with whatever it can actually do.
The steps to repeat would be just select all and run SplitDisjointMesh - you should see the message from my original post. If you select most of the objects one by one the command works just fine.
It probably can be scripted to make it work error-free, but it would be great if the command just worked.
