Snap to isoparm?

(eobet) #1

I tried searching, but the nomenclature in Rhino seems different from the software I’m used to, so I’ll try an illustration instead:

How do I snap to an isoparm?


This is an imported .step file, and red markings are isoparm end points, while blue are mid points (and the free floating is the center of a span).



You need to use OnSurface (OnSrf) one-shot object snap. One-shot object snaps are transparent (work while a command is running). Before picking a point you can either type OnSrf, or hold the Ctlr key down and select it from the osnap Toolbar.
You can also use Between one-shot object snap to snap on midway between two specified locations.

(eobet) #3

Thank you!

Wow, that was super unintuitive. I would never have found that out myself.

I’m still not 100% I’m doing it correctly, because when I hold down control on the snap option, and they switch to the “one shot” options, they’re all greyed out, and when I click OnSrf, the checkbox mark disappears when I let go of the mouse button.



One-shot object snaps only work when Rhino is requesting a point, are turned on for one pick only, and override all persistent object snaps for that pick.


(Pascal Golay) #5

Hello - The one-shots will be ‘live’ when Rhino is actually looking for the point - wait until you actually need it to ask for it. Note the ‘PersistentOnSrf’ as well, btw. Along surface edges the Knot osnap will find the ends of isocurves that are at knots.



(eobet) #6

There is a very nice option in Rhino called “export with origin” that seemingly lets you select a new origin for your exported selection.

However, I wasn’t able to get any of the one shot surface snapping to work with that feature. It just says “OnSrf” on the snap popup, but ignores all iso curves.


(Wim Dekeyser) #7

Hi - I’m not seeing that here - but you will, of course, have to enable the Int snap to be able to snap to intersecting isocurves. So, when you have gotten to the point where the cursor says “OnSrf”, type Int.

1 Like

(eobet) #8

Thank you!


(Wim Dekeyser) #9

Well - you’ll notice that this causes the export to fail - I’m writing up a bug report on that now.


(eobet) #10

Ah, yes. The resulting file is empty. That’s unfortunate.


(Wim Dekeyser) #11

That’s correct.
I see that it was like that in Rhino 5 as well, so this one will have to be fixed in Rhino 7.


(eobet) #12

Oh, aren’t point releases years between them in Rhino, with an associated upgrade cost as well? There’s no service pack releases each year for bug fixes?


(Wim Dekeyser) #13

Hi - yes, traditionally there have been a few years between each major Rhino version, and this is associated with an upgrade cost.

For Rhino 6 for Windows, we are now at Service Release 13, with SR 14 being around the corner. The last SR for Rhino 5 was SR 14.

At this point, we are focused to release Rhino 6 for Mac. Fixes to the Windows version are limited to crash fixes, regressions from Rhino 5, and critical SDK enhancements.

Note that fixes in Rhino 7 are available in the regular WIP versions, and as such, it is possible that your access to this particular fix is not years away.


(eobet) #14

Thank you for the information!

There’s at least two workarounds that I can think of so in this case it’s not a very big issue.

1 Like