I have an error where lines are displayed far away from their actual position. See attached image. The lines was supposed to be right on top of the underlying ones.
Sounds like you are millions of units from the origin…
Barely a million. This one is around 600000 units away, which would never be too far in rhino 5. Given i work in mm, its quite quick to get far away from 0,0 when doing architecture.
I don’t agree… But it’s likely the cause of your problem in any case.
I’ve modelled for ages in Rhino 5, always in mm. And many huge projects. It’s never had this kind of behavior. I have noticed it on even the simplest geometry in Rhino 6. It has to be a bug. When doing a site which is a kilometer long, its hard not to be millions of units away.
OK, maybe a graphics/card driver reaction to the new display pipelines. Can you run SystemInfo in Rhino and post the results here? Also if you go into Options>View>OpenGL and uncheck “GPU Tessellation”, does the problem disappear?
Yes, just as you wrote i tried to disable the GPU tessellation, and it did the trick. I do not know what that implies. Will it slow the machine down without?
System info:
Rhino 6 SR5 2018-6-4 (Rhino 6, 6.5.18155.13161, Git hash:master @ 0e00e118078ee9a651d609817f672fb0ed8e83bf)
Licence type: Commercial, build 2018-06-04
License details: LAN Zoo Network Node
Windows 10.0 SR0.0 or greater (Physical RAM: 32Gb)
Machine name: C-CUSTOM1080
GeForce GTX 1080 Ti/PCIe/SSE2 (OpenGL ver:4.6.0 NVIDIA 391.01)
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 2-23-2018
Driver Version: 23.21.13.9101
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11 GB
C:\Program Files\Rhino 6\Plug-ins\Commands.rhp “Commands”
C:\Program Files\Rhino 6\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 6\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 6\Plug-ins\RhinoLabsTools.rhp “Rhino Labs Tools”
C:\Program Files\Rhino 6\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 6\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino 6\Plug-ins\rdk_etoui.rhp “RDK_EtoUI”
C:\Program Files\Rhino 6\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 6\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 6\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp “RhinoCycles”
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp “Toolbars”
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp “Displacement”
This is one for @stevebaer to answer - personally I do not know if unchecking this slows things down or not. Your driver looks recent enough, I have a 980Ti here with 390.77 (just earlier) and it does not exhibit this problem at 600K units from the origin even with “GPU Tessellation” checked. You could update yours “just in case” I guess… probably should update mine as well.
GPU tessellation does improve the speed of drawing all curves in Rhino 6 (this includes edges and isos of surfaces). That said, there are many cases where the speed is good enough and not noticeable with this feature turned off.
I wrote the curve drawing with GPU tessellation to be able to handle drawing objects far from the origin which is most likely why Mitch isn’t able to reproduce this issue. There must be a case that I am not handling correctly that is specific to your model. Would you be able to share your model with me so I can try and repeat the problem on my computer? I only need the bare minimum of geometry that shows the bug. Thanks.
I have seen the tendency in a few different files now. Yesterday it just went so far that it was worse than autocad without redraw, so i realized it must be a bug.
But the interesting thing is that i cannot recreate it now. After reenabeling GPU tessellation, it still looks fine. But what i have noticed, both yesterday and earlier, is that it seems to come and increase as time goes by. I will try and run with the tessellation today, and see if it slowly returns.
After using Rhino 6 on more computers at work, it becomes more evident that GPU Tessellation does not seem to work correct on all machines with GeForce GPUs.
Noticeable, when simply trying to rotate or scale an object, the live preview during the command, is drawn with wrong centerpoint or wrong increase of scale, making it less intuitive to use. Disabling Tessellation fixes it for now, but some of my colleagues have postulated that their Rhino 6 now works slower than similar models in rhino 5.
I asked for some screenshot of the error, but since it only appears while doing the movement, we cannot make a normal screenshot of it. But it should be easy to replicate.
There was a rotate and scale bug with gpu tessellation on that has been fixed in SR9 which an initial release candidate should be available for next week. This typically only showed up with geometry that is far from the origin. It wasn’t a gpu specific bug.
