Rhino8 Windows,
experiencing a bug while oribiting in viewports with a 3d connexion mouse. While orbiting is ongoing all is good, but when it stops, the display jumps to a previous frame that was displayed in the orbiting process and stops there. Basically the viewpoint changes again after there is no 3d connexion input, back to a random frame that was displayed previously.
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 64Gb)
.NET 7.0.0
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2080 SUPER (NVidia) Memory: 8GB, Driver date: 6-8-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 536.23
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port 0
- Secondary monitor attached to adapter port 1
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPUâs maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 6-8-2023
Driver Version: 31.0.15.3623
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\RhinoCAM 2021 for R7\RhinoArt1FileExporter For Rhino7.0.rhp âRhinoArt1FileExporterâ
C:\Users\isvoranu\AppData\Local\Apps\Evolute\EvoluteTools PRO Panelisation for Rhino 6\EvoluteCoutHook.rhp âEvoluteCoutHookâ
Two things that are usually suggested for issues like this:
Nvidia driver is 6 months old: update it and test.
Disable all plugins that donât ship with Rhino and test again.
If disabling plugins fixes it, install one at a time and test to determine which one causes the problem.
From other discussions on 3dconnexion in R8: if you have the properties panel open, try with it closed. Let us know whether that helps (that would provide a clue to what the root cause is).
Jeremy,
I donât know what you mean by the âproperties panel openâ. There is no panel, open on my desktop, but there is a bunch of software that I see running in task manager. Without those processes running, the 3d mouse wonât work. I will update the nvidia driver and report back, but wonât have the time to remove/install plugins.
Hihihi, this is funny, I thought you meant the 3d connexion panel
I updated the nvidia driver, and it seems the cuprit is the object properties panel. Having it open, docked or undocked, causes the frame jump. Keeping another panel open, like layers, seems to eliminate the problem. Although it doesnât happen immediately so maybe other panels are also making the 3d mouse orbiting display misbehaving ?
Just a guess but it may be influenced by whether the properties panel is displaying object properties or viewport properties. As you move about the view its positional data is constantly changing and that has to be updated in viewport properties.
There are few 3d connexion devices in house.
Hopefully with your description, someone will be able to reproduce it.
Just curious, wondering if you tested this issue with your Plugins disabled.
If you have a chance and can disable these plugin and see if the issue still happens?
you can do that from Options â Plugins and filter on âPlugins that do not ship with Rhinoâ.
Uncheck these, close and reopen Rhino.
C:\Program Files\Rhino 7\Plug-ins\RhinoCAM 2021 for R7\RhinoArt1FileExporter For Rhino7.0.rhp âRhinoArt1FileExporterâ
C:\Users\isvoranu\AppData\Local\Apps\Evolute\EvoluteTools PRO Panelisation for Rhino 6\EvoluteCoutHook.rhp âEvoluteCoutHookâ
@lander - Keep in mind that support for 3Dconnexion devices in Rhino is developed by 3Dconnexion, not McNeel. The 3dxRhino plug-in, which controls 3Dconnexion devices, is distributed with Rhino on their behalf.
That said, we are looking into reported issues to make sure weâve not broken something.
Yeah mm k but, the legacy Rhino support characteristics still have residue and redundancies.
Sure if Rhino wantâs to make it logitecâs problem then thatâs one thing⌠But thereâs still conflict from the pre R6 days of Rhino drivers for said matter.
Although, it would probably be better if there were more collaboration between logitec and Rhino on the matter.
And the future should be more 3D mouse compatible. Unless we all want to continue living in the stoneages.
Thereâs no reason why the world couldnât have more 3D mouse brands by now and more plug nâ play compatibility.
But the human race is still relying on what like 2 or 3 brands for 6 axes navigation devices â there should be 10 or more. itâs sad really. Maybe in 20 more yrsâŚ
I am having the same problem with 3D connexion. There seem to occur when the object properties panel is open as mentioned before, not all the time but often enough.
Windows 11 (10.0.22000 SR0.0) or greater (Physical RAM: 64Gb)
.NET 7.0.14
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA RTX A4500 Laptop GPU (NVidia) Memory: 16GB, Driver date: 12-1-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 537.99
> Integrated accelerated graphics device with 4 adapter port(s)
- Secondary monitor is laptopâs integrated screen or built-in port
- Windows Main Display attached to adapter port #1
- Secondary monitor attached to adapter port #2
Primary OpenGL: NVIDIA RTX A4500 Laptop GPU (NVidia) Memory: 16GB, Driver date: 12-1-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 537.99
> Integrated accelerated graphics device with 4 adapter port(s)
- Secondary monitor is laptopâs integrated screen or built-in port
- Windows Main Display attached to adapter port #1
- Secondary monitor attached to adapter port #2
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPUâs maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 12-1-2023
Driver Version: 31.0.15.3799
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â
maybe⌠
â there should be 10 or more. 
itâs sad really. Maybe in 20 more yrsâŚ