Bug: Severely Laggy Viewport When Maximized (Solved)

Rhino Rhino for Windows
1

Hi All,

I’ve recently noticed a severe performance dip when maximising viewports. Here’s the most basic example with a completely empty file:

And from my current project running the Testmaxspeed command (in Wireframe):

Running this system:

Rhino 6 SR17 2019-8-6 (Rhino 6, 6.17.19218.13231, Git hash:master @ 62456cca9a849f28b1a160168ce8c7a1bc26010f)
License type: Commercial, build 2019-08-06
License details: LAN Zoo Network Node

Windows 10.0 SR0.0 or greater (Physical RAM: 32Gb)
Machine name: CPH-PC0042

Non-hybrid graphics.
Primary display and OpenGL: NVIDIA NVS 510 (NVidia) Memory: 2GB, Driver date: 3-16-2018 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 391.25

Secondary graphics devices.
  Intel(R) HD Graphics P530 (Intel) Memory: 1GB, Driver date: 2-7-2019 (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: 3-16-2018
  Driver Version: 23.21.13.9125
  Maximum Texture size: 16384 x 16384
  Z-Buffer depth: 24 bits
  Maximum Viewport size: 16384 x 16384
  Total Video Memory: 2 GB

Rhino plugins
  C:\Program Files\Rhino 6\Plug-ins\Commands.rhp	"Commands"	6.17.19218.13231
  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\RPC.rhp	"RPC"	
  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"	6.17.19218.13231
  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\IronPython\RhinoDLR_Python.rhp	"IronPython"	6.17.19218.13231
  C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp	"RhinoCycles"	6.17.19218.13231
  C:\Program Files\Rhino 6\Plug-ins\Grasshopper\GrasshopperPlugin.rhp	"Grasshopper"	6.17.19218.13231
  C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp	"Toolbars"	6.17.19218.13231
  C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp	"3Dconnexion 3D Mouse"	
  C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp	"Displacement"

Hope you have a fix :pray:

Best and thanks,

Anders

2

I’m not sure what McNeel would expect from an NVS 510, but the card is almost prehistoric by today’s standards:

https:// www.techpowerup.com /gpu-specs/ nvs - 510 .c1868

The NVS 510 was a high-end professional graphics card by NVIDIA, launched in October 2012 . Built on the 28 nm process, and based on the GK107 graphics processor, in its GK107-301-A2 variant, the card supports DirectX 12.0. The GK107 graphics processor is an average sized chip with a die area of 118 mm² and 1,270 million transistors.

It’s 2GB is on the low end by today’s standards yet still better than the newer Intel’s 1 GB.

The Nvidia driver is also quite out of date. See:

https://www.nvidia.com/download/find.aspx

Hope this gives you some ideas.

3

It is indeed an old card, hopefully my employer will update our workstations soon.

That said, this behaviour (i.e. maximised viewports are severely bogged down, even with an empty file!) has only recently been a problem. I don’t recall exactly when it started, but I believe within the last couple of Rhino updates. So I assume this is not necessarily (just) related to using an old card.

I did actually try update drivers, though through the Device Manager. Will try to download the latest one directly from NVIDIA instead and see how that plays out. Cheers.

Update: Updating the driver appears to have fixed this issue. The aliasing look at bit wonky now, but I assume this is something I can fiddle with from the NVIDIA Control Panel.

1 Like