Hi JoelI work in a large studio of modo artists, and often swap between using modo, Octane or Maxwell to render our visuals, however one key issue I keep coming up against is that whenever I load up modo to work on a scene, the plugin will automatically add octane parameters to my scenes even when I don't intend to work in Octane. when working on projects with other artists, this creates compatability issues between machines and causes problems when running renders on our farm.
It would be great to have the option not to auto update every scene that's opened with the plugin, or as with the maxwell plugin, there's an button that strips the scene and everything in it of all maxwell specific channels. Could the same be implemented on this plugin?
I have spent some time on this today trying to implement an "On/Off" button, however this is quite at odds with how Modo works - where all the Octane info is stored in channels - if the channels are not there Modo crashes. So the plugin goes to great lengths to ensure the Octane channels are there for all scenes. So having the plugin running, but not adding the channels is going to be virtually impossible to implement (since all the channels are in the plugin XML files - they cannot be turned "Off"). In particular, the camera, environment, imager, kernel and postproc nodes are attached as channels to the Modo renderer, camera and environment, so pulling those out is likely to cause substantial stability issues. Deleting the Octane Overrides on the other hand should be doable. Would that work for you? I could implement a simple Modo command to do this.
Also, are you able to tell me about the compatibility issues you are getting pls? I would expect if you load a scene saved with Octane info into an install of Modo which does not have the plugin installed, Modo should just pop a warning. Are there other problems arising?
Thanks
Paul
