Has anyone else noticed inconsistencies between how rhino performs geometry operations when scripted vs. when used manually? For example, I’ve been using Offset() a lot during scripting for a CAM script. In order to get the output I want, i have converted closed curves to polylines, OK fine. I then want to offset inward to compensate for tool width, and i want the result to be a polyline as well, so i can easily extract points for the machine code. When i script this offset operation, however, i get another NURBS curve out, and this curve may or may not even be closed still. In contrast, when i offset the same curve myself in the graphics window I get the nice, closed polyline i desire. And these are not overly complicated shapes, either; think “lima bean”-like, fairly smooth. Is Rhino doing something different under the hood in each case? It would be nice to be able to trust my scripts to do everything the same as it works in the viewport.
Any insight would be much appreciated, as I’d rather not have to sample the curve myself, i feel it would be much more resource intensive for a file with a few thousand such objects
EDIT: I also noticed that when the scripted Offset() command does produce a polyline, Rhino will tell me that the offset polyline is open, even though the start and end points have identical coordinates in the details view. Could the implementation of Offset() be forgetting to alter the open/closed attribute of the object properly?
EDIT2: Actually, manually doing the offset in this case produces the same result, an open polyline with (closed) coordinates. Does Rhino have more trouble offsetting polylines with small segments?