F9 saves inappropriately with Render Passes node
Posted: Sat Aug 01, 2015 5:13 pm
Recently I've had problems when compositing in After Effects because suddenly a frame would look completely wrong. I would then realize that an F9 test render for a future version of a scene had been rendered into a folder with a completed render of a previous version of a similar scene, and a finished file had been written over. This is a file that may have taken 10-40 minutes to render, wasting a similar amount of time because I now had to re-render the same frame, but actually wasting much more than just the render time because I have to track down the right scene file and load it, which sometimes takes up to ten minutes, and then double-checking all the settings are correct.
This is unexpected behavior. Lightwave never saved F9 renders until after the render display had opened following completion of the render, and then it is done manually. Whenever possible Octane should follow LightWave behavior. In this case, so I don't have to constantly remind myself to disconnect the Render Passes node whenever I'm doing test renders.
I realize that it's possible that some people may want F9 renders to automatically save if the RP node is connected. If so, would it be possible to add a button to the node that would disable saving F9 renders?
Thanks!
This is unexpected behavior. Lightwave never saved F9 renders until after the render display had opened following completion of the render, and then it is done manually. Whenever possible Octane should follow LightWave behavior. In this case, so I don't have to constantly remind myself to disconnect the Render Passes node whenever I'm doing test renders.
I realize that it's possible that some people may want F9 renders to automatically save if the RP node is connected. If so, would it be possible to add a button to the node that would disable saving F9 renders?
Thanks!