Choose curve at apparent intersection?

Hello.
When 2 curves don’t touch each other how to choose the proper curve to snap to during apparent intersection snap?

It highlights both curves, but when snapped it snaps to one of them, so how do I choose which curve it snaps to? So, for example, I could add a point on each curve at that apparent intersection.

In Onshape hitting TAB button brings up a list of nearby objects to choose to snap to. It also has another method to select proper “mate connector” by holding SHIFT key which “freezes” current available points and then you point at the one you want to select.

Is there anything similar in Rhino?

Thank you

Hi Vano -

When you minimize the viewport so that you also see the perspective viewport, you will see that the line that the mouse pointer is closest to is getting snapped to. By moving the mouse from one line to the other, you can see the snap point move along.

That said, the feedback in this case should be such that only the line that is getting snapped to is getting highlighted; not both.
RH-93733 OSnap:Int: Apparent Intersection Feedback
-wim

Oh, yes, I see it. Thanks!
But it is so finicky, very “twitchy” especially when there are more than 2 lines involved (feels like moving 1px is enough to effect which line is snapping to)
Perhaps holding a Shift key would “freeze” the intersection point, so cursor could move away and click on the needed line to snap to?

I think all involved lines should be highlighted, but the line being snapped to highlighted differently? This way when there are other lines very close it will show exactly what intersection is in affect.

what exactly is your workflow to rely on ( imprecise ) apparent intersection ?
if you struggle with multiple stacked objects, organize your drawing with more layers.

kind regards -tom

I’m working with scans from a Proliner. So, most of the time scans have some sort of loop or C-shaped objects, often symmetric. When they are perfectly rotated in the world and looked from the side, it’s practically impossible to tell which line is what side as they overlap. And when I need add a point at one side where it intersects with some other line, it was like 50/50 chance for me before.

But as you suggested having multiple viewports opened helps a lot in this regard. I’ve never used this method before because of monitor resolution, but it sure helps significantly!

if you have a predefined hierarchy, and it is a repetitive, daily workflow a macro or script might help.
with hierachy i mean:
“i always need points on black curves, that apparently intersect with blue curves in top view”
a small script can generate those points, and they can be snapped to via “point” object snap.

My method for selecting an apparent intersection point on the desired curve:

Cursor tooltip for Osnap active
Int Osnap and Near Osnap on

Move cursor to desired curve near but not at the intersection until the Near Osnap displays

Slide the cursor along the desired curve until the Apparent Int Osnap displays. The apparent intersection will be on the desired curve.

Left click or right click as appropriate

RH-93733 is fixed in Rhino WIP

If it only highlights snapping line, how do we know which intersection it belong to? (in case of 3+ involved lines)

The snap will be on the highlighted line at the apparent intersection which is at or near the cursor position.

I understand that, but when there are several apparent intersections at very close proximity, how would we know which of other lines the intersection belongs to? Or am I overthinking it?

Hi Vano -

It sounds like it, yes.
The change is in a public version of the WIP. Please use that version and let us know if the scene you are imagining is not behaving as expected.
-wim

It actually works very well!