We’ve been getting reports from our users that their custom Display Modes have been resetting. I was hoping to get some more insight on where these Display Modes live and what might be causing them to reset? We are on version 7.29.23
Is there a reason you’re on 7.29 and not 7.37?
Our infrastructure team manages the applications we push out. Everyone has 7.29 on their PC. I suppose it will be a matter of time before we update.
For what it is worth: 7.29 came out April 17th 2023, 7.37 on May 14th 2024 - you’re missing out on quite a bit of fixes.
Hi -
We’ve gotten a few reports that that behavior in the past but it’s not something that we have been able to reproduce. As long as that is the case, this is not something that we can fix.
Can you please run the Rhino SystemInfo command on machines that have had this happen and post the output here?
-wim
I suspect you’re right.
Can you repeat this without the 3rd Party plugins installed? Enscape being the common denominator.
Please to do File>Properties>Plugins and disable 3rd party plugins (Rhino restart req’d)
Hi Japhy, repeat the screenshot or repeat the issue?
The issue, seeing that Enscape is on both it’s good place to start.
Updating to 7.37 did not resolve this. To the benefit of searching for a quick answer our user had his display modes disappear a couple days after updated. Trying enscape next however this is not a realistic work around since we have users who use enscape pretty often.
When the display modes are created, do they live in a file somewhere in appdata?
Hi -
Disabling 3rd party plug-ins is not offered as a work-around but as a means of troubleshooting the issue. As was said, we have not been able to reliable reproduce this issue, and, without that, this is not something that we can fix. If disabling an external plug-in makes this disappear, we at least have a lead to work from.
Yes, they are written to the settings-*.xml file in the %AppData%\McNeel\Rhinoceros\7.0\settings\ directory, where * is the name of the scheme in use.
-wim