Intersection not accurate

This is relevent to the tiny problem I’m experiencing.

Why does the intersection point not occur at the interesection. If there’s no intersection then why does the point appear at all?

There’s not enough information in the video to tell.
Send a file with the two curves in it.

Okay, and here’s another aspect I just discovered.

TinyHole.3dm (757.4 KB)

Also, after selecting all duplicates and deleting there’s nothing left at all.

Where is this little overlap?
The coordinates of the end of the short overlap would work.

Did you run SelDup, or SelDupAll?
SelDupAll does what you described.

Sorry, I had to step out. I used command D to select duplicates. I’ve used this in the past when I was having so many problems with that issue.

IN the past, a single copy of everthing would remain.

The over lap occurse here.

Capto_2016-06-22_12-07-17_PM.capto.zip (859.4 KB)

I looked closely at that spot in the TinyHole.3dm file in both Windows and Rhino V5 and I could not find an overlap like your screenshot displays. Very odd.

There is an extra line segment just to the right of the intersection, following around the corner, but I don’t think that has anything to do with it.

I am running the potential release build so maybe you’re seeing a glitch in 5.1.
Did you try it in the WIP?

Hi John,
I just updated as per the application today.

So which build of Mac Rhino are you running?

Rhinoceros > About Rhinoceros

Here’s the issue again:

Capto_2016-06-22_02-13-06_PM.capto.zip (4.5 MB)

Even running that identical build (5C249w) I can not see the longer line.
I don’t know what to suggest. Until we can duplicate a problem, we can’t find and fix it.

Could this be a display problem? I submitted another issue that is directly related to this here:

http://discourse.mcneel.com/t/tiny-fail-question/33715?u=jkayten

I couldn’t say.
Perhaps @marlin or @dan might have an idea as they are the Mac guys.

here’s another version to try with

TinyHole.3dm.zip (8.0 MB)

Can you Zoom in and use the Distance command with Osnaps between the Intersection and Endpoint?
I’m guessing it is a very tiny distance so you may have to tighten up your absolute modeling tolerance setting.

OK. In TinyHole 2.3dm, with a tolerance and display precision of 0.00001 mm,
I can measure the distance from the end of the curve to the point on the other curve as 0.00093 mm.
Since that is less than twice the tolerance setting you were using at the time of 0.001mm, that is considered within tolerance.

What downstream process are you using that this will be a problem?
For reference, a human hair has a diameter of 0.100 mm

As far as the intersection thing goes, the default setting for Osnaps (Rhinoceros > Preferences > Modeling aids), is to accept Apparent intersections. Intersection osnap picks are view based instead of tolerance based. I
In this case, if you turned off the apparent intersection tool, AND tightened up your modeling tolerance to 0.0001, then the Intersection osnap would not have found the apparent intersection

Thanks John,
At this point I’m building a portfolio of objects so as to eventually find paying gigs. But I also want to create objects that I’m confident enough of to submit for profit in such sites as ‘turbo squid’.

I’ve now disabled the appaerent intersection option in the prefs. This particualar feature has been a general nuisance for the most part. I’d refrained from using it in the osnaps options but I didn’t know it was still operative.

I’ve left the tolerance at the small items default for everything I’ve done so far and unless there’s a compelling reason to do otherwise
, I’ll continue with it.