Option settings are reset to default

All option settings, including Appearance, Aliases and View settings were reset to default in the middle of working. Following by a crash of my working file where I was actively editing V-ray materials.

Not sure if my hardware spec is too outdated, but random crashes have happened so frequently in Rhino 7. At first I thought the stability would improve through updates, but unfortunately major crashes keep happening ever after the release. All I can rely on is the autosave files in Recycle Bin that may or may not actually be successfully saved there.

This time is really the worst because the save file for custom settings is not easy to recover. Looking into the forum I don’t think there is any way to retrieve those custom settings. Being optimistic I still want to post this to see if anyone runs into a similar situation and is able to get those settings back.

Thank you

If you are getting random crashes it’s most likely either your computer specs are not up to running Rhino (especially the graphics card/driver) or a plug-in is doing it - or both.

Thank you so much for helping with the issue. I am surprised that I haven’t figured out that for such a long time. I guess what is even more surprising is that considering the number of people who are using the same model of workstation around the world, obviously, not everyone experiences this sudden drop in performance by switching from Rhino 6 to Rhino7. I am amazed how this can be so easily diagnosed to be an outside issue of hardware and/or plugins so quickly.

Hi -
We’re not seeing a lot of frequent but random crashes on Rhino 7 these days - which, as Mitch says, makes it likely that this is caused by a plug-in or hardware, or a combination.
Please run the Rhino SystemInfo command and copy-paste the result here.
From the crash reports that you sent in, I see that you V-Ray and Enscape. Are you crashing equally frequently when those plug-ins are disabled?
-wim

I am not 100% sure if I should consciously disable those plugins every time I open Rhino to make the software work properly. What I know is that most of the time I don’t have Vray or Enscape running actively when I am working in the model space. When I crash out with plugins open I understand that the issue is likely on the capacity of the graphic card or the issue of the plugin. However, it has nothing to do with the issues I run into when I focus exclusively on modeling.
Just an example, because of my modeling tendencies, I am used to editing a polysurface by selectively moving control points to adjust the size of an enclosed geometry, or doing similar things on curves and hatches for drafting. This is a habit I built since the very early days of using Rhino and now it has become a trigger to crash ever since the shift to Rhino7. I had reported this multiple times and the simple answer I get is to update my Rhino. It is obviously not the correct solution since the problem persists even to the most recent release today.

That being said, the true problem reported here is not only the file crashed, which can be partly recovered by digging into the autosave versions, but this time my custom settings have all gone disappeared for some reason. It is hard to believe this is likely caused by ‘plug-in or hardware, or a combination’ without further elaboration.
Below is the Systeminfo result when I open Rhino as a baseline:

Rhino 7 SR24 2022-10-10 (Rhino 7, 7.24.22283.10361, Githash:master @ 8a36c0fc6c4c6b22ef2530cd9aa33ae6661fa64f)License type: Commercial, build 2022-10-10License details: Cloud Zoo Windows 10 (10.0.19043 SR0.0) or greater (Physical RAM:32Gb) Computer platform: DESKTOP Standard graphics configuration. Primary display andOpenGL: NVIDIA Quadro K1200 (NVidia) Memory: 4GB, Driver date: 12-29-2021(M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 511.09 > Acceleratedgraphics device with 4 adapter port(s) - Secondarymonitor attached to adapter port #0 - Windows MainDisplay attached to adapter port #1 OpenGL Settings Safe mode: Off Use acceleratedhardware modes: On Redraw scene whenviewports are exposed: On Graphics level beingused: OpenGL 4.6 (primary GPU’s maximum) Anti-alias mode: 4x Mip Map Filtering:Linear AnisotropicFiltering Mode: High Vendor Name: NVIDIACorporation Render version: 4.6 Shading Language:4.60 NVIDIA Driver Date:12-29-2021 Driver Version:30.0.15.1109 Maximum Texturesize: 16384 x 16384 Z-Buffer depth: 24bits Maximum Viewportsize: 16384 x 16384 Total Video Memory:4 GB Rhino plugins that do not ship with Rhino C:\Users\PLY_1\Downloads\elefront0410\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0 C:\Users\PLY_1\AppData\Local\Programs\Enscape\Bin64\Enscape.Rhino7.Plugin.dll “Enscape.Rhino7.Plugin” 0.0.22231.942 C:\ProgramFiles\Chaos Group\V-Ray\V-Ray for Rhinoceros\V7\VRayForRhino.rhp “V-Ray for Rhino” Rhino plugins that ship with Rhino C:\ProgramFiles\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.24.22283.10361 C:\ProgramFiles\Rhino 7\Plug-ins\rdk.rhp “RendererDevelopment Kit” C:\Users\PLY_1\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\RPC\0.0.15\RPC.rhp “RPC” C:\ProgramFiles\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “RhinoRender” 7.24.22283.10361 C:\ProgramFiles\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.24.22283.10361 C:\ProgramFiles\Rhino 7\Plug-ins\rdk_ui.rhp “RendererDevelopment Kit UI” C:\ProgramFiles\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots” C:\ProgramFiles\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.24.22283.10361 C:\ProgramFiles\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.24.22283.10361 C:\ProgramFiles\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion3D Mouse” C:\ProgramFiles\Rhino 7\Plug-ins\Displacement.rhp “Displacement”

Hi -

That advise is not offered as a permanent fix or work-around but as a tool to try to isolate the problem.
It’s 100% up to you to take that advise or to leave it.

Here on Discourse, you have a total of 3 posts, all in this thread. I can’t find any reports from you in our 1-to-1 support system.

As I said, we’re not seeing a lot of frequent but random crashes on Rhino 7 these days. Your issues are related to something very specific to your workflow and/or hardware.
-wim

‘take it or leave it’ — Perfect.

Thank you for trying to arguing over those details in the post instead of being helpful regarding the problem itself. I have total of 3 posts because I was talking about all the crash reports I sent in the past to the team, and threads on another account. I am sorry that those are not useful information for your ‘1to1 support system’.

I am so glad that this shows how McNeel might have taken off and gotten one step closer to what we expected from a tech monopoly — to have a typical customer service that plays dodge ball so well. Now you are going to argue that this is a community space, not for customer service. You got it right. Congratulations for the great work.

1 Like

Couple of thing to check: see if there is a newer graphics driver available (yours is relatively old) and check your file for bad geometry /bad meshes.
Your video card memory is on the small side also. But I doubt that’s the cause of trouble. It will depend on your scenes.

Well, as you may have gathered in the responses to your posts, even after various kinds of suggestions were offered, having a sarcastic attitude and not trying the things that were suggested isn’t going to inspire people to help you much more.

If you want to continue to believe that Rhino is 100% responsible for your ‘random’ crashes, that’s your right, nobody is going to argue. However, it’s not going to help solve the problem. It was stated a number of times that there aren’t many reports of those that are not in some way either connected to video drivers and/or plug-ins.

Both V-Ray and Enscape are well-known crash-producers, if you do a little search of the forum you will find lots of such reports. You yourself mentioned “Following by a crash of my working file where I was actively editing V-ray materials.”

Your video driver could be updated - it’s not quite a year old - but that’s not likely the problem.

If you disable Enscape and V-Ray for a day or so - not just not use them, but actually disable them - and still have crashes, then something can be investigated. And do send in any crash reports if the dialog comes up, if you don’t, it will be difficult to analyze what happened. If the crashes do stop happening after they are disabled, then it’s time to contact Chaos support.

As far as options being set to default, difficult to know what happened there. There aren’t a lot of reports of that either. All the settings are in an .xml file here:

C:\Users\<username>\AppData\Roaming\McNeel\Rhinoceros\7.0\settings

I surmise something might have crashed when trying to write to that file and it got corrupted, but that’s just a theory.

1 Like

Well said my friend, what has become so apparent is that all you care about is winning the argument instead of digging deep into what triggers the problem. Frankly, my ‘sarcastic’ attitude is a direct response to the arrogance you have shown in the thread that I feel is necessary and responsible to express. Though I am open to suggestions, the solution Wim provided has nothing to do with the issue I expanded on the cause of ‘random crashes’. It is a different topic from the issue I listed in the initial post — that the crash this time (even if it is likely caused by Rhino’s compatibility with Vray) makes all my settings reset to default. I spent enough time browsing the forum before I even consider posting this in the first place, and unfortunately after seeing all your replies from the team I feel unlikely there will be any suggestion I can possibly take. I am sorry if you feel upset because my attitude doesn’t inspire, that is not my objective anymore. I can close the post if you think this has a bad influence on the positive vibe of the forum, but otherwise I will save my energy from responding further on this topic.

A few more words about my attitude. The very mentality of yours for suggesting people to upgrade their hardware even before understanding the entire situation is a reflection of what the tech industry has been imposing on all users in this time of history. Instead of providing more accessible tools and democratizing technology to enable a larger base of users to fulfill their goals, updates have happened to become more and more demanding on the performance of the working device that become necessary to upgrade every few years. When you are making updates for the sake of legitimizing software purchasing, and you still expect that users should just internalize the frustration as individuals, I am not going to apologize for my attitude to express the disappointment of the project. Good luck to your development team and I am looking forward to the success of your future releases.

1 Like

I will do the same. Good luck on your quest.

Your video card is under powered for two monitors, (you need 4gb vram for each monitor) and your nvidia driver is also due for an update.

when you update your card driver, use the custom/ advanced option and check “clean install”

Also please make sure your windows OS is completely up to date, as well as updates for all your plugins, especially vray and enscape. Elefront is also worth making sure is fully updated.

Hi,

While working earlier, Rhino reset itself for the first time today. Thought I’d check in when I had a spare moment to see what caused it. I also have V-Ray installed but used it only briefly yesterday. Any thoughts? I had no crashes btw…

TIA
H

System Info below:
Rhino 7 SR29 2023-4-17 (Rhino 7, 7.29.23107.03001, Git hash:master @ 5f05ef3a2eea3d910c4c2fb79ccc75b413d33ca7)
License type: Educational, build 2023-04-17
License details: Cloud Zoo

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 64Gb)

Computer platform: LAPTOP - Plugged in [100% battery remaining]

Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 5-24-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 P3200 (NVidia) Memory: 6GB, Driver date: 2-15-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 518.01
> 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: 2-15-2023
Driver Version: 31.0.15.1801
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\Solemma\ClimateStudio\bin\ClimateStudioRhino.rhp “ClimateStudioRhino” 1.6.8014.23580
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros\V7\VRayForRhino.rhp “V-Ray for Rhino”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.29.23107.3001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.29.23107.3001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.29.23107.3001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.29.23107.3001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.29.23107.3001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”