Hi, I have this problem that you may see in the screenshots.
I created a custom display mode based on the VisualARQ Realistic mode (changing the background, global illumination, and a few other settings). I’m attaching it here. It’s very handy because it allows me to place some fast renderings in my layouts.
But… every time I open my file, the layout details where I’ve used that display mode reset to Wireframe. In the screenshot I’m attaching, you can see an example: my custom display mode resets to Wireframe, while the original Realistic mode does not.
So I’m not sure whether this is a problem with VisualARQ or with Rhino itself.
Indeed.. this problem doesn’t happen with a custom display mode that is based on a native Rhino display mode.. Any guess why this happens with the ones bases on the Realistic one by VisualArq?
I imported your custom VisualArq display mode, used that in a detail, saved the file and then restarted Rhino. When I opened the file, the detail was still in that custom display mode. I don’t have VisualArq running here, so perhaps that’s a requirement to be able to reproduce the issue?
-wim
Hi @mutarq I can’t reproduce this problem with your custom display. And I have VisualARQ loaded.
I suspect that since that display mode comes from a VisualARQ one (the “Realistic”), when you open the file, VisualARQ does not load properly for some reason, and that display mode is not found, so the viewports using it switch to Wireframe.
What version of VisualARQ are you using? In the recent 3.11 update we added a change that forces Rhino to load VisualARQ as soon as it detects VisualARQ data in the file. This would solve this problem of the restored display modes, if the reason is that VisualARQ doesn’t load properly in advance.
Let me know if this problem occurs with the 3.11. If it does, please share a file we can test it with to keep investigating.
