Rhino 8 Computer hanging needs resetting

Just keep in mind, that when using Remote Desktop, the graphics stack in-use in Windows is totally different from when you are running locally on the actual hardware. So if McNeel is using more OpenGL or DirectX features in their own graphics code in v8 vs v7, you can potentially run into new issues with RDP.

In something graphically intensive like Rhino, if I were McNeel folks, I’d want to verify that using Rhino with a mouse, keyboard, and monitor hooked up to the actual machine shows the same issue.

Pete

Hello,
Below is the SystemInfo.
I appreciate your help, but I had the fourth such crash earlier today, two while using Remote Desktop and two working directly on the computer with cabled keyboard, a cabled mouse and and cabled monitor privileges to make Ctrl+Alt+Delete, so I would take the Remote Desktop out of the equation.

Rhino 8 it’s proving unreliable to work on, with the type of files we are handling. It is slow and every now and again goes away.
Please have a look at the info below, in the hope you spot the thing that is reducing the performance.
Thanks, N

Rhino 8 SR5 2024-2-27 (Rhino 8, 8.5.24058.13001, Git hash:master @ eaa901528453bac5a3cfc23321bdf4d767238d34)
License type: Commercial, build 2024-02-27
License details: Cloud Zoo

Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.16

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3060 (NVidia) Memory: 12GB, Driver date: 2-2-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 528.49
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0

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: 2-2-2023
Driver Version: 31.0.15.2849
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 12 GB

Rhino plugins that do not ship with Rhino
C:\Users\ \AppData\Roaming\McNeel\Rhinoceros\packages\7.0\AMDDenoiser\0.5.3\AMDDenoiser.Windows.rhp “AMDDenoiser.Windows” 0.5.3.0
C:\Users\ \AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.5.24058.13001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.5.24058.13001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.5.24058.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.5.24058.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.5.24058.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCode\RhinoCodePlugin.rhp “RhinoCodePlugin” 8.5.24058.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.5.24058.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

1 Like

Please update your GPU driver, currently the most recent one for your model is: NVIDIA Studio Driver | 551.61 | Windows 10 64-bit, Windows 11 | NVIDIA When you do make sure to go through the custom/advanced installation and check clean install.

I understand your frustration, but I don’t understand why you haven’t done this while I asked you to do so.

Is there a reason to have both the AMD Denoiser and the NVIDIA Denoiser installed on a PC with an NVIDIA GPU?

Does that cause problems?

Pete

having them installed does not in and of itself cause problems.

1 Like

The only times I’ve seen a completely frozen screen, without a proper bugcheck is when something goes really wrong with the graphics driver.

Applications will not typically cause anything like that, and kernel problems will typically give you a bugcheck/blue screen.

Out of curiosity, when the screen completely locks, from the local PC, try Windows+Ctrl+Shift+B. Hold each one down in turn and release all of them after the B.

That key combination resets the graphics subsystem, driver, etc. on the PC. If you have speakers, you should hear a beep when it does it, and the screen may flash a time or two. If the computer is truly locked up (which is exceedingly rare), it may do nothing. Worth a try either way. But it needs to be done from the local PC with the actual attached keyboard.

Pete

2 Likes

That is a little gem there. I haven’t had freezes in ages, but I’ll try to remember this. I probably should program it into my keyboard…

1 Like

Sorry about that. I can drive the car but I have no idea what is under the hood. I asked for help on that, I’ll keep you posted.

I’ll try it if it happens again.

1 Like

Given that it was happening multiple times per day, I take it this is now fixed with the driver update?

Pete

Hi Pete,
They were not happening multiple times per day, it happened —4 times— [edit: rereading my own first message, the first time it happened it happen 3 times in a single day indeed. - I grouped those into one event in my memory, sorry - it then happened 3 other times] over a week or two, and always with the same file.
I stopped using R8 for a while for that and a couple of other reasons (some of them resolved with the latest release), until I finished my previous deadline. And I haven’t returned to the previous heavy file until now, and have been only lightly testing other issues, while focusing on other parts of my work (I have periods of almost 100% Rhino use, and periods that I barely touch it).
Unfortunately, I also did not yet have the opportunity to update the drivers, I expect I’ll be able to get help on that beginning of next week.
Thanks, N

Hello @nathanletwory and @Pete_Brown
I came back yesterday to Rhino 8 to test a few things. Today I noticed there was an update and after updating a few minutes into navigating around the model, the computer hanged remaining unresponsive for the last hour.

This had no result. Both the keyboard and the mouse are completely unresponsive.

I have updated the drivers a couple of weeks ago, but I had not touch Rhino 8 since then.

Although I haven’t touched Rhino 8, I have been working quite intensely in Rhino 7 and not once I had a hanging computer (some crashes but not this one). The file that provoved the hanging is a file that I have worked for the last week or so in Rhino7 without any problem.

Just to be clear, I haven’t used the remote desktop since this issue appeared and the keyboard, monitor, and mouse are connected directly to the machine.

@nathanletwory
Any further suggestions to try to understand what is going on?

Thanks, N

So nothing Raytraced / material related in this case?

I’m not sure if we already tried this, but please give turning off GPU tessellation a go (Tools > Options > Views > OpenGL).

Hello Nathan,
I don’t recall it ever been related to raytraced issues.
In this particular instance, it occurred just after opening the file.

What does turning off GPU tessellation do?
N

It essentially demands less of the GPU. It could help in this case - we won’t know until we’ve tried.

Hi @nathanletwory ,
I haven’t been using R8, and I now I brought a file from R7 and I am trying to print. A few seconds after I press Ctrl+P the Rhino shut down. The computer does not hang but Rhino simple goes out.
I think it is a different problem.
Can I send you the file and see if you have the same problem?
N

I believe some printing fixes were made recently - can you share the Rhino _SystemInfo of your current Rhino version?

Below the system info
I can’t post the file publicly.
N

Rhino 8 SR7 2024-4-22 (Rhino 8, 8.7.24113.23001, Git hash:master @ 6d95a2bfe831b9dd0ef81b6e220b294af59416ca)
License type: Commercial, build 2024-04-22
License details: Cloud Zoo

Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.17

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3060 (NVidia) Memory: 12GB, Driver date: 2-15-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 551.61
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0

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: 2-15-2024
Driver Version: 31.0.15.5161
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 12 GB

Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Lands.rhp “Lands Design”
C:\Users\User Name\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
C:\Users\User Name\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\AMDDenoiser\0.5.3\AMDDenoiser.Windows.rhp “AMDDenoiser.Windows” 0.5.3.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.7.24113.23001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.7.24113.23001
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.7.24113.23001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.7.24113.23001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.7.24113.23001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.7.24113.23001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.7.24113.23001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\BlockEdit.rhp “BlockEdit” 8.7.24113.23001
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

Feel free to send the file using Rhino - Upload to Support

1 Like

@nsgma
Thank you for this.
Please disable these 3rd party plugins and test.
Let us know your results with no 3rd party plugins loaded.

Finally, make sure you are submitting the crash dmp from Rhino.
You can also manually save off the RhinoCrash.dmp from the desktop while Rhino crash dmp dialog is still open. You can email it to tech@mcneel.com and reference this thread.
This is very important because this might tell us what is crashing your Rhino.

Sincerely,
Mary Ann Fugier

Hello Mary Ann,
the Print crash problem went away with the recent Rhino 8 update. With and without plug-ins.
Thanks, N