I’m experiencing an odd behavior in a new file I’m working on.
Base File is a DXF import, but the lines i’m working with are new additions. My end control points are “floating” off of the line. when I try to snap end-points together from two lines, the highlighted line jumps around.
Never experienced this on v5, and haven’t noticed it in any other v6 files. Image attached. Could it be a video card issue? I can’t post the file publicly, but will send to tech@mcneel.com
Nope, same issue. It appears to be related to the GPU Tessalation setting. Off and it’s fine, on, and I get floating points. What does GPU Tesselation do? Should I be grumpy that i can’t check the box?
here are 3 different zoom levels on the same section, AA is off and Tesselation is off. The area in question is about 300mm from 0,0,0 as the crow flies.
you can see that the lines jump around, and I’m having issues joining into a closed curve.
to be fair, this is a pretty extreme zoom, but I never experienced this at any level in v5, and i’m very anal about point precision.
I still suspect you might be far from the World origin. In the status bar, you have your coordinate display set to CPlane - what happens when you change it to World?
Here are some additional screens with a line intersection moved directly on to world 0,0,0.
In the top view, you can see that the end control point of the lower line is snapped to the end of the upper line, however the lower line itself is not being drawn consistently. the first image and the second image are 1 mouse wheel click apart in zoom.
Here is a stripped version. I’ve cut and pasted into a new file, and rebuilt/re-drawn the lines repeatedly. and re-generated from surface, so i believe it’s a global issue, not just this geometry.mcneel_support.3dm (33.5 KB)
OK, thanks - you’ll want to set that check box back on. I’ll let this sit for the weekend and see if I can make it look ugly on my desk machine in the office, it has an NVidia card as well. However the upshot, I would say, is that the geometry is not off.
However, before you think I’ve found the problem, look what I had to do to get it to happen…
That means that the little square you see is only 1/100,000 mm, i.e. a ridiculous zoom-in level. At any normal zoom level it looks fine. The extracted end points also select with SelDup, so the curves themselves are fine as far as I can see. Must be something with the display then… I’ve got a 780 here, but I’m still on 390.77 (next-to-last) drivers.
I see the same thing. V6 is at least 1000 times less accurate when you zoom in than V5.
With this geometry in V5 I can zoom in until the entire viewport measures 0000000 mm from corner to corner - the endpoints of these lines are still accurately displayed at 0,0
When I zoom in on the same geometry in V6 the display of the line endpoints will start lose accuracy and jump around when the viewport measures only 0.0002211 mm across. That means you can zoom in at least 1000 times farther in V5 and still get an accurate display.
And as a side note V4 was even more accurate than V5. In V4 you can zoom in on these endpoints to the point where display starts to degrade and then measure corner to corner of viewport and it measures 8.49143e-12 mm across.
It looks like every new version has degraded the users ability to zoom in and inspect what is going on accurately.
" the line endpoints will start lose accuracy and jump around when the viewport measures only 0.0002211 mm across"
Hard for me to understand why this is significant for most of us using Rhino. Can you please explain? From my experience if I have to zoom in this tight I should be looking at my modeling tolerances, not needing to visually inspect really tiny bits.
