MeshSplit MeshTrim

Meshtools in Rhino like booleans, trimming and splitting have always
been broken. In my opinion they are of such poor quality, they are best
avoided.

I sometimes read harsh statements like this, which I can understand there are some things that drive me nuts too, but for me these are not so much on the mesh side of things. For Rhino being a NURBS modeller and a tool with a very wide scope I was still delighted to see the improvements in the Mesh tools from v3 to v4. I agree the advancement since then has not been progressing very fast, but still I mesh booled this STL model with +4000 intersection into a single closed mesh for stl printing back then, using the 4.0 WIP. So saying they a broken is not right imho.
Of course things could be much better and I hope they will be soon, with work being done in the sub-D area too.
but for companies doing time/project critical work on meshes often, the investment into something like magics can be a fast turnaround, such software is very expensive, for a reason.

1 Like

Hi John,
I understand the frustration.
I discovered that meshpatch and the delaunay f*cks up and creates bad meshes if it has duplicate inputs. They are not intelligent enough to sort out two points in the same spot. So I added a CullPt to my grasshopper script and rebuilt the mesh from the initial post, but splitting still fails.

Here’s the v2 of the file:
MeshTrim MeshSplit, good mesh.3dm (357.8 KB)

I don’t know if this is of any help, but the new code in MeshSplit is now able to address this case:

More info in the The new code for MeshSplit thread.

Thanks,

Giulio


Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com