Hi,
I have an issue since the last software update (7.23): when I use the command DupBorder to extract a silhouette, if I then explode the obtained curve to have (for example) the 4 edges of a like-squared face, it doesn’t split in the 4 main edges but it fragments into as many segment as the number of isocurves that originated the surface.
Here you may see what I mean: rhino issue while duplicating borders - YouTube (as shown at the end of the video, it doesn’t still happen while duplicating “edges” instead of “borders”, but this command is unusable when you have many surfaces with edges in common).
Is it possible to set Rhino to prevent this from happening and return to the previous setting?
Where did that surface come from? I can’t repeat this here. Are you sure that this is a single surface and not a polysurface (possibly imported from a mesh program or made from a polyline)? If it’s a polysurface, then the behavior is normal. Please post the file with the object otherwise.
Hi, yes, I’m sure it’s a surface and not a polysurface, it come from the tapered extrusion of an ellipse (here it’s just a part of the original surface, but it does the same also with the uncutted original one, and also with every moderate complex surface that has many isocurves).
So it’s not about isocurves, but key-points that generated the curves (like quadrants of those circles).
But it’s still an annoying issue: it didn’t happen before the last update. On complex surfaces, using duplicate border was exactly the same as using the command duplicate edge right now
Yep, I definitely see something wrong in your file I downloaded. V6 DupBorder does not explode the edge curves of the full circular object at all - message “Cannot explode single curve segments.” - but V7 does into 364 separate elements. Definitely buggy. @pascal - one to check?
Your round surface is definitely a mess with 1093 control points around its circumference, but that still shouldn’t cause the issue.
V6 sees a Nurbs curve, V7 a polycurve. My W.A.G is that this is related to V7 keeping the identity and structure, so to speak, of sub-curves in a curve, possibly.
Do you have any solution? Otherwise, is it possible to download and reinstall a previous Rhino version (like 7.20, I’m pretty sure that version didn’t have this issue)?
