I’m exporting surfaces to a program called Maxsurf which tends to read the original untrimmed surface.
I have tried ShrinkTrimmedSrf and ShrinkTrimmedSrfToEdge but after each command the surface can still be untrimmed in Rhino and Maxsurf still reads the untrimmed surface.
Is there something I’m missing? or a better way of approaching this?
Hi Tom - Not all surfaces can be shrunk back to their trims if the trims are arbitrary. If the trims are not on isocurves, there will always be some of the underlying surface ‘sticking out’ someplace. Feel free to post one of the surfaces…
ShrinkTrimmedSrf and ShrinkTrimmedSrfToEdge shrink the underlying surface to isocurves, not the trim curve unless it happens to coincide with one or more isocurves.
Yep - if you turn on points for this surface you can see that the underlying surface is still there in the notch - it is not trimmed on an isocurve there on the long side of the notch. There is no way around it - if the target application cannot see trimmed surfaces as trimmed, you cannot use this surface as is. However you can split it in two, in this case and suck the smaller part over to thge trim curve using MatchSrf - I’m not sure if that will work for you. To be a little more sure, I moved the points by hand over to that red curve in the file before matching and I used the 'match by closest points setting. To move the points with some control in this particular case, use Ortho or Gumball, but in an arbitrary orientation, you can force points to stay locked into the line to the next point (the ‘control polygon’ segment) by setting DragMode to ‘ControlPolygon’.