.vrscene can't be rendered if interactive was enabled

[seltzdesign]

Is there a way to not have this happen? Usually when you work in Rhino you have the interactive renderer enabled for working. Now if you export a .vrscene it actually exports the current settings. When it comes to batch rendering it will tell you that it can't render the .vrscenes since they are set to Interactive.

Just like you have a "GPU override" button in V-Ray Cloud, shouldn't there be a clever way to switch it back to progressive when batch rendering. Otherwise, you have to always remember to have the settings right when you export, since otherwise your .vrscene files suddenly become useless and can't be rendered any longer.

In fact, the root cause of this is that it is weird that V-Ray has one set of settings for both interactive and production. They should be 2 separate sections in the asset editor so you can set them both up how you like and can then hit either render interactive or just render. Always having to switch settings is just not very user friendly.

Is something like that planned?

[konstantin_chaos]

Hi seltzdesign ,

This is something we are aware of.

In fact, the root cause of this is that it is weird that V-Ray has one set of settings for both interactive and production. They should be 2 separate sections in the asset editor so you can set them both up how you like and can then hit either render interactive or just render. Always having to switch settings is just not very user friendly.

This is more or less what I also think.
The best solution is to just remove the Interactive toggle always export production scenes.
We should initiate the interactive rendering mode only when you click on the interactive rendering icon (toolbar, asset editor, VFB, etc.).

The only issue with this solution is that you'll not be able to see UI guides for the features that work in interactive mode or not.
They are not too many though.

Konstantin