If I have large elements made in Grasshopper they will disappear when I zoom out in the Rhino doc (perspective viewport only, the rest works fine).
They start to appear if I select them on the GH canvas or if I zoom back in again.
Any Idea how to prevent this behaviour?
(Placing something as large as the GH objects helps also, but its not really a nice workaround)
How large?
When drawing selected previews, the camera transformation in the viewport is slightly bumped so that selected objects are always drawn slightly in front of other geometry in the same location. This may explain why there’s a difference between selected and unselected.
But it shouldn’t be happening either way, so it would be nice if you could upload a file that shows this effect.
So either 6.10 somehow fixed it, or there was something completely different off.
The GH file it self is old – it was made 2015 – but right now I can’t reproduce the effect.
Sorry for razzing!
Phew, close one that.
Aaaaand there it is again (new file created today):
This is just rotating the view a bit, but zooming out has the same effect.
Putting a Rhino Object helps to prevent this.
I’m unable to replicate that behavior here.
Can you run the Rhino SystemInfo command and post the result here?
Sure!
Rhino 6 SR10 2018-11-7 (Rhino 6, 6.10.18311.20531, Git hash:master @ 0f9089a0035dcc6955732d57071445ecc29390f0)
Licence type: Kommerziell, Build 2018-11-07
License details: Stand-Alone
Windows 10.0 SR0.0 or greater (Physical RAM: 7.9Gb)
Machine name: MSI
GeForce GTX 960M/PCIe/SSE2 (OpenGL ver:4.5.0 NVIDIA 382.05)
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.5
Shading Language: 4.50 NVIDIA
Driver Date: 5-1-2017
Driver Version: 22.21.13.8205
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 2 GB
C:\Program Files\Rhino 6\Plug-ins\Commands.rhp "Commands" 6.10.18311.20531
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp "Renderer Development Kit"
C:\Program Files\Rhino 6\Plug-ins\RhinoRender.rhp "Rhino Render"
C:\Program Files\Rhino 6\Plug-ins\rdk_etoui.rhp "RDK_EtoUI" 6.10.18311.20531
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\IronPython\RhinoDLR_Python.rhp "IronPython" 6.10.18311.20531
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp "RhinoCycles" 6.10.18311.20531
C:\Program Files\Rhino 6\Plug-ins\Grasshopper\GrasshopperPlugin.rhp "Grasshopper" 6.10.18311.20531
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp "Toolbars" 6.10.18311.20531
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp "3Dconnexion 3D Mouse"
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp "Displacement"
C:\Program Files\Rhino 6\Plug-ins\Calc.rhp "Calc"Hi - first thing to try is to get updated drivers for the GPU.
This one is getting old.
Driver Date: 5-1-2017
Is the Rhino file entirely empty? Is it fixed if you add any regular object, such as a Point or Line to Rhino?
You are right, didn’t do it for some time, since I had problems at one point with newer ones. But I updated now und it seems, it’s gone now (atleast the same file now behaves fine).
To David: Yes, if you put something into the Rhino file like a point etc. it’s fixed as well.
Okay, it still happens…
To me it seems like a plane infront of the view with a fix offset and everything behind this imaginary plane gets cut off.
Yes it’s a problem with the OpenGL clipping planes. Before you can start drawing stuff in ogl you have to specify the nearest and furthest points you want to include. Normally Rhino collects the bounding boxes of all the things it’s going to draw. But when the Rhino document is empty it sometimes thinks that it doesn’t have to include grasshopper previews as well. “We’re not drawing anything, so no need to set everything up properly”…
Thank you for the technical explanation, David. Exactly something like this I had in mind, just didn’t expected this to be some OGL thing, but makes totally sense.
It was a bug a while ago, but got fixed in more recent versions. Since you’re running a recent version either someone put it back in again or it’s a different bug which manifests in the same way.