Solo Node is currently taking into account frame buffer exposure and tonemapping - shouldn't these be ignored?
working on an image where exposure is +11 which means that if i solo a node it's way too bright
Moderator: face_off
If that is the only change you need, I can do that in the next release.Dingbat wrote:so exposure can't be temporarily switched to 1 while Solo Node is on?
Hi - does this "test" version of the next release of the plugin do what you are looking for?Dingbat wrote:thanks Paul
so exposure can't be temporarily switched to 1 while Solo Node is on?
face_off wrote:If that is the only change you need, I can do that in the next release.
Paul
face_off wrote:does this "test" version of the next release of the plugin do what you are looking for?
Paul
face_off wrote:Regarding Modo14...the Octane plugins are released for the current 3 versions of the host app (so Modo16, 15 and 14 at the moment). However Modo17 will be released soon (if not already), and at that point Modo14 will no longer be support by the Octane plugin. So I would highly recommend upgrading your Modo version.
Thanks
Paul
It will, although I am not doing test builds for Modo14. I will do the final Octane 2022.1.2 build in a week or two, and there will be a Modo14 then.Dingbat wrote:i understand that Octane 4 MODO will continue to work in MODO 14 until 17 is out
Users browsing this forum: No registered users and 3 guests