I recently ran into some issues with a new Laptop + eGPU setup where Rhino would crash on startup when the eGPU is not connected.
I think I narrowed this down to the Rhino Cycles plugin. Rhino starts normally when this is disabled and crashes as soon as I load the plugin when Rhino is already running.
I’m running a Win Laptop with an Intel Iris chip graphics chip and an external nVidia GPU.
I checked the CPU renderer then restarted rhino to confirm the setting is saved.
After unplugging the eGPU I tried starting rhino again and it crashes on startup like before, when loading the plugins
Edit: please try updating your GPU drivers first, they’re pretty old. And while you are at it make sure all Windows 11 updates have been installed.
If that doesn’t do it:
Please try creating an empty file called disable_gpus in the location %APPDATA%\Rhinoceros\7.0\Plug-ins\RhinoCycles (9bc28e9e-7a6c-4b8f-a0c6-3d05e02d1b97)\settings
An unplugged eGPU setup - does that mean the eGPU is not connected at all? As in you just have the laptop with nothing connected to it?
I don’t have access to eGPU configurations to test and debug what you’re seeing. I have currently no good understanding what it means to have an unplugged eGPU setup.
What I mean is that I usually run rhino with an external GPU plugged into the laptop.
When I try starting Rhino when I don’t have the eGPU connected to the laptop, Rhino will crash while starting when trying to load the Rhino Cycles plugin.
When you disconnect your eGPU does windows still show a display adapter in the device manager?
I don’t see how else Rhino Cycles (or rather Cycles) would crash.
I wonder if Blender 3.5 also would crash if you first have it started with the eGPU connected, then close Blender, disconnect the eGPU and restart Blender.
@blind when the crash happens do you ever get the Rhino Crash Reporter dialog presented? If you do please submit a crash report with in the comments a link to this topic.
Furthermore, after a crash can you check your desktop for a RhinoCrashDotNet.txt (or similarly named .txt file) with a timestamp that matches the time you crashed. Could you attach that to a reply here?
I have logged this as RH-79798 RhinoCycles crashes Rhino on startup with disconnected eGPU, so that if and when a fix is found this thread will also be notified.
With the eGPU unplugged, there is basically no discrete GPU in your system, only the CPU. Disabling GPU rendering in this case does not and will not make any difference in rendering speeds, but it does apparently prevent you from crashing…so to me, that sounds like a pretty good stop-gap solution until we can figure out what’s really crashing Rhino on your system.
Note: The Intel Iris is not used in the way you might think when it comes to Rendering… A non-discrete GPU is simply ignored and CPU rendering is used.
I’d like clarification here (I’ve read this entire thread, but I still want to make sure)…
With the eGPU plugged in, Rhino never crashes? Yes? No?
With the eGPU unplugged, Rhino always crashes? Yes? No?
I think that the usage of an eGPU here is just a red herring, and that these crashes have nothing to do with the eGPU or the GPU inside it… It has more to do with starting Rhino on a laptop that contains only a non-discrete GPU (i.e. Intel CPU).