Batch render Tweet

[tschwenke]

Hi,
When I render with "Render to disk," the plugin loads in the whole scene every time. Every frame, it loads the whole mesh and sends it to my render slaves; that takes a lot of time, even if it's only camera movement (of 100kB), it sends the whole scene (like 100MB). I tried these "octane update" buttons, but without any effect. Is there any mystical button I can use (like those D,M,I buttons)?
Best wishes,
Thomas

[juanjgon]

What update options do you have enabled? If you are rendering a sequence with an animated camera only, you should disable all the "update" options that are not needed in your case.

Thanks,
-Juanjo

[tschwenke]

Hi,
I tried those checkboxes, but they have no effect. It doesn't matter if I check or uncheck them, it's the same...
Is there any other button I have to activate?
Rendering mode is set to "Update scene" and Multithread extraction is "Disabled."
Best wishes,
Thomas

[juanjgon]

Hmm, but are you talking about the scene extraction time/local GPU update, or the scene updating in network render nodes? At least in the local machine, the scene updating in "update scene" mode with all the update options disabled should be really fast, like the IPR ...

Thanks,
-Juanjo

[tschwenke]

Hi,

No, neither the local update nor the network render is faster. Is it working on your machine?

As I suppose you didn't touch the network render, both should go hand in hand: if you reload the whole scene locally, the slaves will update the whole scene (automatically). If only the camera is updated on the local computer, the slaves will only update the camera. That's at least my assumption...

Best wishes,
Thomas

[juanjgon]

I'm investigating an issue updating the scene while rendering to disk that can be related to your reported rendering slowdown. I hope to know more details soon ...

Thanks,
-Juanjo

[tschwenke]

Hi,

Great to hear that. Thanks alot!

Best wishes,
Thomas

[juanjgon]

The slowdown problems updating the scene while rendering sequences in update scene mode should be fixed in the next 2018.1 build.

Thanks for reporting this issue!
-Juanjo

[tschwenke]

Great. Thanks!