I occasionally experience an unknown crash caused by Rhino that forces my computer to restart. After restarting I will see that all settings are reset to defaults, nothing appears in recent files and licensed plugins (RhinoCAM) have to be reactivated. The biggest headache is all of my keyboard macros (not aliases), display mode options and other settings reverting to default which forces me to have to manually reconfigure each customization from scratch when this occurs.
Is there anyway to save a backup of my options configurations to avoid having to reconfigure everything when this occurs?
yes, with modern OS design, such crashes cannot be caused by user-level programs like rhino, only by the OS itself and drivers, or by failing hardware, so the thing to do is update drivers and check hardware health (memory, etc)
they can appear to be “caused” by a program, because the program makes a normal request that triggers a driver or OS bug, or brings failing hardware into play
you should open rhino and post the results of the SystemInfo command so we can see more of what is going on
Only reason I suspected that the OS crash was caused by Rhino was because I had poked around in the Event Viewer with my IT guy and observed logs that suggested it was caused by Rhino. What you’re saying about the program request triggering a driver/OS bug makes sense and probably explains that. I would be surprised if it was any kind of hardware failure as this particular machine is a fairly fresh build. Does it make sense though that a bug like this would reset Rhino in particular back to default settings while not affecting other software on the OS?
No it doesn’t. That’s super wierd. The only scenario I can think of where this happens is…too convoluted to explain and still wouldn’t reset everything.
Your Nvidia driver is way out of date, as may also be your Windows 10. Also your Rhino 7. Everything needs to be kept up-to-date, this is not an “if it doesn’t look broke don’t fix it” system. If you’ve got corporate IT people who have to update stuff for you, well get friendly with them.
As Jim mentions, this is super weird. It means that directory or files in it are deleted and there shouldn’t be anything that does that. When you launch Rhino and the necessary files aren’t in place, Rhino creates them on the fly.
if not, then the first files to check/monitor would be the .xml files under appdata/mcneel/rhinoceros/7.0/settings, to see what they look like after one of these crashes, but before starting up rhino, to see if they are actually missing or corrupt in some way
secondly, it would seem interesting to know how/where rhinocam stores its license info
Windows 10.0.19042 SR0.0 or greater (Physical RAM: 32Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2060 (NVidia) Memory: 6GB, Driver date: 9-13-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 472.12
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
Secondary graphics devices.
Intel(R) Iris(R) Xe Graphics (Intel) Memory: 1GB, Driver date: 3-18-2022 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- There are no monitors attached to this device!
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: 9-13-2021
Driver Version: 188.8.131.5212
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 6 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\RhinoCAM 2021 for R7\RhinoCAM 2021 For Rhino7.0.rhp “RhinoCAM 2021 - The cutting edge CAM plug-in for Rhino 7.0 from MecSoft Corporation”
C:\Program Files\Rhino 7\Plug-ins\RhinoCAM 2021 for R7\RhinoArt1FileExporter For Rhino7.0.rhp “RhinoArt1FileExporter”
I suspect you may be right, will be sure to stay updated and continue monitoring down the line. Fortunately this issue has only occurred a few times sporadically in the last 2-3 months, happened more frequently when I switched to this new machine about 6 months back.
I read something awhile back that referred more to UI layout about saving a backup of the “settings-Scheme_Default” and “windows_positions-Scheme_Default” files for recovering/migrating viewport preferences. Am I correct to interpret what you’ve said as saving a backup of the AppData directory (after setting up my custom options) and replacing in the event of a critical crash like this to be the quick and dirty way of restoring the changes I’ve made to my options from defaults?