Rhino crashes with .vrscene loaded while saving named view

[seltzdesign]

If I load a .vrscene file into Rhino and then go to save a named view, Rhino crashes every time. If I have no .vrscene file loaded saving a named view works as expected.

I am on the latest Rhino Version 6.28.20199.17141 and V-Ray for Rhinoceros 6 4.20.03.

I have tried with several different .vrscene files and the same thing happens.

Is there a fix coming?

If you need any more info let me know, we need to be able to save views without first deleting the .vrscene file. Thanks.

[seltzdesign]

Update: If you save the named views first and THEN import a .vrscene file, Rhino crashes as well.

[nikoleta.garkova]

Hi seltzdesign

I've tested this with Rhino 6.28.20199.17141 and V-Ray Next 4.20.03, however, I could not reproduce the issue. Please correct me if I'm doing something wrong: http://ftp.chaosgroup.com/support/screenshots/2020-10-08_14-00-51.gif

Can you let us know a few additional things so we can try and identify the culprit:

1. When did this started happening - have you done any hardware/software changes?
2. Are you using any additional plugins not shipped with Rhino?
3. Is it possible that the .vrscenes were done in a previous version of V-Ray?
4. Does this happen if you open a completely new file and try to load the .vrscene there?/Can you try exporting a very simple .vrscene, loading it back and then try to save a named view?
5. Would it be possible to forward one of the .vrscene files you've tested with so we can investigate further?

Thanks!

[seltzdesign]

Hi nikoleta.garkova

Thanks for getting back. Yes, I have done exactly the same steps. The .vrscenes come from 3DSMax 2019 and are a scene from Evermotion Archinteriors 49.

I just disabled some plugins and found the culprit. Its EvoluteTools. Once I disable their plugins, I can save named views just as you show.

I will just leave them disabled for now, as I don't need them at the moment. They are pretty popular plugins though.

[nikoleta.garkova]

Thanks seltzdesign and good job for narrowing it down. We've logged this in our internal bug-tracking system (ID number: VRW-2873) for developer investigation.

[nikoleta.garkova]

FYI, our devs had a look at this and it seems that our code is not directly involved with the issue. I'd advise you to get in touch with EvoluteTools developers and let them know about this.