Rendering Animation Bug

[spartan00j]

Are you able to send me your config.xml file pls?

Thanks

Paul

[Petec]

I am experiencing this bug as well (with the last Octane 2021 build). Sometimes the partially baked frames are 2 frames apart, other times they're 20 frames apart. Increasing samples per pixel to around 900 doesn't help.

I have both a 2080 and 3080 to render with (the 2080 also drives my display). After some testing it seems checking the "image" box in render devices for the 3080 will cause this bug to occur.

If I have the image box checked ONLY for the 2080 the bug does not seem to occur. So, there is that. While this is a work-around (for me, at least), it's not ideal, as I prefer to render only with the 3080, leaving the 2080 for display purposes.

Update: After updating to Octane 2022 the problem is worse and happens on every 2nd frame now no matter how I set up my render devices, so my work-around no longer works-around.

So, that's a kick in the pants...

[face_off]

Hi

I still cannot replicate this issue. Can you please send a screenshot of your device preferences (by clicking on the Open Device Settings button on the Render Devices tab of the plugin.

Thanks

Paul

[spartan00j]

Hi

I still cannot replicate this issue. Can you please send a screenshot of your device preferences (by clicking on the Open Device Settings button on the Render Devices tab of the plugin.

Thanks

Paul

I used RTX acceleration on and off.
Same results.

[Petec]

Hi

I still cannot replicate this issue. Can you please send a screenshot of your device preferences (by clicking on the Open Device Settings button on the Render Devices tab of the plugin.

Thanks

Paul

When I turn off RTX Acceleration the bad frames go from every second frame to about 3 bad frames out of 30.

[face_off]

Hi

I can now reproduce this error, and am trying to fix it for the next release. In the meantime, you can set the Fresh Time in the plugin Settings to something like 2000 to minimise the chances of a blank frame being saved.

Thanks

Paul

[Petec]

Hi

I can now reproduce this error, and am trying to fix it for the next release. In the meantime, you can set the Fresh Time in the plugin Settings to something like 2000 to minimise the chances of a blank frame being saved.

Thanks

Paul

Thanks I'll give it a shot and I appreciate your efforts.

[Petec]

Question: Where exactly do I find the right setting (refresh rate) to minimize bad frames?

Also, estimate on when the update will drop? I use Octane primarily for animation, and use the plugin (not standalone). So, at the moment I am not getting the benefit of something I am paying for.

Hi

I can now reproduce this error, and am trying to fix it for the next release. In the meantime, you can set the Fresh Time in the plugin Settings to something like 2000 to minimise the chances of a blank frame being saved.

Thanks

Paul

Thanks I'll give it a shot and I appreciate your efforts.

[face_off]

Question: Where exactly do I find the right setting (refresh rate) to minimize bad frames?

I was using 2000 (ie. 2 secs) and couldn't reproduce the error.

Also, estimate on when the update will drop? I use Octane primarily for animation, and use the plugin (not standalone). So, at the moment I am not getting the benefit of something I am paying for.

OTOY are looking at the issue at the moment. I hope to have a fix in the next week.

Thanks

Paul

[face_off]

Hi

I believe that the following version of the plugin will resolve this issue. It has been compiled with Octane 2022.1 XB4, however the compositor layers (ie. Output AOV's) are not working correctly (and will change with XB5) - so I am not doing a formal release of this version. Other than that - all 2022.1 XB4 features should be in this release.

https://render.otoy.com/customerdownloa ... RPRISE.exe
https://render.otoy.com/customerdownloa ... STUDIO.exe

Thanks

Paul