My biggest gripe lately with Rhino8 is that for some reason when something has been selected, I can’t use the mouse to move or rotate the display until I’ve deselected the thing. Kind of maddening. Don’t know if there is already a report about this. It doesn’t matter what project. Here’s my sysinfo
Rhino 8 SR6 2024-3-26 (Rhino 8, 8.6.24086.11001, Git hash:master @ 8e3b686f596bb6443e56e6dbecf0f54f4888713a)
License type: Commercial, build 2024-03-26
License details: Cloud Zoo
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 8GB)
.NET 7.0.12
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 1-20-2022 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA Quadro P600 (NVidia) Memory: 4GB, Driver date: 11-1-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 537.77
> Integrated accelerated graphics device with 4 adapter port(s)
- Video pass-through to primary display device
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: 11-1-2023
Driver Version: 31.0.15.3777
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
I went to NVIDIA and updated to the latest, then went to Intel and update to what they said was the latest. I don’t seem to be able to make Rhino happy. I still got notification as follows.
Here’s sysinfo
Rhino 8 SR6 2024-4-2 (Rhino 8, 8.6.24093.11001, Git hash:master @ de3127ef7b7fd6e4c2fef07a9a1bc10c8e1942a3)
License type: Commercial, build 2024-04-02
License details: Cloud Zoo
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 8GB)
.NET 7.0.12
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 11-13-2023 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA Quadro P600 (NVidia) Memory: 4GB, Driver date: 3-14-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 538.49
> Integrated accelerated graphics device with 4 adapter port(s)
- Video pass-through to primary display device
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: 3-14-2024
Driver Version: 31.0.15.3849
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
Hi Pascal,
What you describe is correct. But it is an intermittent problem. It may happen only once or twice per drawing session. So I’ll have to try using the command line next time and try to observe if there is anything that led up to it.
I had not reported this before because it was so intermittent. It’s maddening when it does. When I saw the thread in the summary with the litany of other problems, mine sounded a little like the one where the command line loses focus which I have also experienced. So I threw my 2 cents in. We can probably close this thread now and let me try to reproduce it and gather more information.
Thanks,
Joe
I presume you’re describing an old issue that got worse in version 5, and has never been corrected ever since.
I don’t believe it’s directly related to ‘objects having been selected’. I do believe it mostly has to do with various command function activations, completions, dialogues etc.
My usual ‘hurdle over the problem’ is to quickly click with the regular mouse into an empty spot in the workspace, in order to correct the glitch.
Sometimes you might even have to invoke a regular rotation with the regular mouse to correct the glitch.
This used to be very frustrating to perform every time to mitigate the issue, but things like this can become subconscious after you do it a million times
It would be great if the world we live in would finally accept the 3D mouses, but they’re still waiting for something …
Not sure my issue is the same. I haven’t run into it until Rhino8 as far as I can remember, and I’m just using a regular Logitech mouse. I think I’ve only seen it when something is selected which makes it especially maddening after spending some time selecting just the right thing, or things. But I am going to take care to log future occurrences and try to define the conditions.
Thanks…