Render Queue producing double renders
Posted: Mon Sep 23, 2019 3:53 pm
A. Win 10
B. 2x GTX Titan Pascal
C.32gb
D. Nvidia driver version 419.67
E. OctaneRender Standalone 4.05
F. OctaneRender plugin 4.05
G.C4D R21.023
When I add scene via Render Queue it still renders out to project folder even if I untick the standard save... creating an additional render sequence and leaving things very messy...
If I do this to picture viewer it doesn't do it, so seems to be a render queue problem? Is this something that can be fixed octane side?
I''ve attached a C4D file which renders out to to a folder in the same directory...If you try rendering via picture viewer and also with render queue then look in the folder where the C4D file is and you can see a residual render that's produced even though the standard save function is turned off
It's not a HUGE issue but it's very annoying when your compositing and working and you have a folder filling up with images you don't need, plus the time it adds onto have to write an additional image file.
B. 2x GTX Titan Pascal
C.32gb
D. Nvidia driver version 419.67
E. OctaneRender Standalone 4.05
F. OctaneRender plugin 4.05
G.C4D R21.023
When I add scene via Render Queue it still renders out to project folder even if I untick the standard save... creating an additional render sequence and leaving things very messy...
If I do this to picture viewer it doesn't do it, so seems to be a render queue problem? Is this something that can be fixed octane side?
I''ve attached a C4D file which renders out to to a folder in the same directory...If you try rendering via picture viewer and also with render queue then look in the folder where the C4D file is and you can see a residual render that's produced even though the standard save function is turned off

It's not a HUGE issue but it's very annoying when your compositing and working and you have a folder filling up with images you don't need, plus the time it adds onto have to write an additional image file.