Will not fillet again

Rhino Rhino for Windows
21

I think “joinedge” is to be regarded a “last resort” command that should be considered only when everything else has failed AND when you are sure that you have no further modeling operations to perform on the polysurface. Like for instance when you have to have a watertight solid for use in other applications and can’t fix those naked edges.
Then again in these cases 80 % of the time it fails to fix all edges so I would revise my advice to “avoid at all cost”

I didn’t know of the “CrvDeviation” command. Good to know.
Sadly it has the same usability issues as the new “EdgeContinuity” in Rhino 7 Wip: edges need to be selected one by one. Even worse: (for “CrvDeviation”) polysurfaces need to be exploded to test edge to edge deviations.
So for efficient examination of complex polysurfaces both of these options are not practical at all in their current form.

22

CrvDeviation works on pairs of naked edges in the same polysurface without exploding the polysurface. It can be used to test the deviation of pairs of naked edges. It does not work on pairs of non-naked edges without exploding the polysurface or extracting the individual surfaces.

If a pair of edges is joined and not naked then the edges should be within twice the absolute deviation of each other unless the absolute tolerance has been changed since the polysurface was created or JoinEdge was used to force the edges to join.

2 Likes