Control Points NOT NEARLY exact?

Hey guys,

When I’m drawing (let’s just stick with 2D for now) - and I look carefully, my lines are not terminating or lining up correctly with other crv.

If I zoom in, the control points are not actually “on the end of my crv.” (see image and file)

I’ve tried changing the file’s tolerance and angle tolerance, etc.

What can I do to fix this, please?

Thanks

End points wrong - maybe tolerance issue.3dm (9.0 MB)

I suspect this is a display side effect of GPU Tessellation.
If you go into Options > View > OpenGL, uncheck the GPU Tessellation option then OK the dialog, the points will move to their correct position.
However, the Rhino display will probably slow down.

The developer is working on trying to fine tune this so you don’t get the confusing display, but it is just that; a confusing display. It is not a lack of modeling accuracy.

Nope - that did not help any in this example file. But I will try on the larger and see if it at least makes a difference for now. Thanks

Can we have a link to follow the work being done on this one?

How far in are you zoomed? For example, if you put your cursor on the end of the line in your sample case and note the x-coord, then move it to the control point how much does the x-coord change? I ask because I’ve noted (and frequently use) the fact that it is possible to zoom in so far that moving the cursor 1/4" or so on the screen doesn’t change the coord at all out to .001" coord display precision.

It worked for me as I described.
Did you forget to OK the dialog and leave Options?

image

https://mcneel.myjetbrains.com/youtrack/issue/RH-44895

This is a display issue and has nothing to do with tolerances in your model. Zooming in extremely close to an object suffers the same numerical problems that we have when attempting to display geometry that is very far from the origin. I am looking into ways to improve this situation.

1 Like

IMHO, at least one can live with this issue if he/she knows what’s happening. What you get when far from origin: not so much.

I think I can detect this case and perform the accurate display calculations necessary. These calculations are much slower, but when zoomed in at this level you typically don’t have a lot of geometry on the screen to deal with.