Was allowing users to use mesh objects as splitters/trimmers ever considered? Wondering if there is a reason behind not allowing these or it’s more or a legacy of Rhino not being a mesh modeling software. A lot of progress has been made with meshes recently and also seems like a lot of users work with meshes or as we do over here hybrid models that consists of all sorts of object types, meshes being used a lot.
Now if I want to trim/split bunch of curves with a mesh object, we need to either MeshToNurbize or do other more complex operations for a simple split/trim.
Splitting or trimming shouldn’t really pose a problem as it’s easy to determine the intersections - especially in the case of curves. However, for surfaces (imagine the intersection of a mesh with a Nurbs sphere) you might still have to nurbsify the mesh to calculate the intersection…
Hi Mitch, thanks - I thought so with curves, that it should be “simple”… and that’s what inspired me to post this after needing to trim curves with mesh for the 100th time today…
I understand that trimming NURBS with meshes is more complicated - I think if it was implemented under the hood there would not be a need to MeshToNURBify the whole mesh - just the faces that are detected to be intersecting with the suface, which could speed things up. I wish meshes were treated as other objects when it comes to picking trimmers/cutters.
I think that the problem is that the mesh/curve intersector does not exist yet… So right now all you can do is something like approximate the curve with a polyline, get the intersection of that with the mesh and then try to perhaps refine it (iteratively?) for each intersection. Below is what’s currently available in the WIP…
RhinoScript has CurveMeshIntersection method, so it must be available out there, somewhere.
To be clear - I am not looking for a script, just thought why not implement this in core Rhino…
Hmm, odd, Python rhinoscriptsyntax has that too, but I don’t see it in Rhinocommon. It has to be calling some Rhinocommon method behind the scenes, but my computer is off now, so I can’t look…
Ah, found it on Github… it actually converts the curve to a polyline within a given tolerance and uses mesh polyline intersection… so there actually is no real curve mesh intersector. That said, the polyline conversion should be “close enough” within tolerance…
hi @pascal, would you know there is a chance to have using mesh as trimmers and splitters implemented in Rhino? Seems like the methods to do so already exist in rhino api.
I am really frustrated i cant trim or intersect my nurbs obects with meshes. Mesh facets are just planar objects and should easily be able to truncate nurbs objects! I need this everyday in my work and its huge frustration this does not work in rhino…
we work in team and i get railway track as meshes and i just use those for the bridge design. it takes incredible amount of useless energy to workaround each and every time since its solvable by computer. tedious…
