Beta vers. 7.0.20273.15003 encounters serious delay (3-4 sec) when selecting objects behind geometry in Ghosted view.
mac, pc, systeminfo?
Rhino 7 SR0 2020-10-13 (Rhino 7 BETA, 7.0.20287.16003, Git hash:master @ 4e4df7bee6cc4158620b7d1105625b9e7e57abde)
License type: Commercial, build 2020-10-13
License details: Stand-Alone
Expires on: 2020-11-27
Windows 10.0 SR0.0 or greater (Physical RAM: 32Gb)
Non-hybrid graphics.
Primary display and OpenGL: NVIDIA Quadro P4000 (NVidia) Memory: 8GB, Driver date: 2-24-2020 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 442.50
Secondary graphics devices.
- NVIDIA Quadro GP100 (NVidia) Memory: 16GB, Driver date: 2-24-2020 (M-D-Y).
- NVIDIA Quadro GP100 (NVidia) Memory: 16GB, Driver date: 2-24-2020 (M-D-Y).
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Hi -
Could you please post the entire SystemInfo data?
Does this also behave like you describe when you start a new file from a factory-default template and add two boxes?
-wim
Hi Wim,
when I have only 2 boxes with MM (small model) its immediate. With more complex geometry is completely slows down. I’ve tested the same model in v6 and v7 and v7 is just extremely laggy. Only plugins installed are VisualArq and Vray yet am testing models with no VisualArq elements and have set renderer to Rhino. Here’s the complete SYSInfo - I do have an NVLINK with 2 x GP100’s as a render device but this shouldn’t affect it. Thank you in advance.
Rhino 7 SR0 2020-10-13 (Rhino 7 BETA, 7.0.20287.16003, Git hash:master @ 4e4df7bee6cc4158620b7d1105625b9e7e57abde)
License type: Commercial, build 2020-10-13
License details: Stand-Alone
Expires on: 2020-11-27
Windows 10.0 SR0.0 or greater (Physical RAM: 32Gb)
Non-hybrid graphics.
Primary display and OpenGL: NVIDIA Quadro P4000 (NVidia) Memory: 8GB, Driver date: 2-24-2020 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 442.50
Secondary graphics devices.
NVIDIA Quadro GP100 (NVidia) Memory: 16GB, Driver date: 2-24-2020 (M-D-Y).
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 2-24-2020
Driver Version: 26.21.14.4250
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 16 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros\V7\VRayForRhino.rhp “V-Ray for Rhino”
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7 WIP\Plug-ins\Commands.rhp “Commands” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7 WIP\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 7 WIP\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino 7 WIP\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 7 WIP\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 7 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7 WIP\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 7 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7 WIP\Plug-ins\Displacement.rhp “Displacement”
how many monitors are you using?
Why is your gp100 set up as your secondary card? Which card is your primary monitor set to use?
Kyle,
I use a P4000 as the display card connecting two 4K monitors. I also have 2 x GP100 (NVLINK) as a dedicated VRAY engine.
ok in your windows monitor set up, is the main display set to be the monitor that is on your p4000? (use the identify monitors and make sure that monitor is plugged into your p4000) there is an issue with the latest version of windows where the main display has to be on the main display card or windows freaks out…
Thanks Kyle. I only have the P4000 plugged in. The GP100’s are set up with TCC and are dedicated GPU compute so do not affect the display pipeline.