Should DR/BB nodes reload the max file for every frame?

[atelieryork]

Hi folks,

When rendering an animation sequence, is it correct/expected that the other machines on the network have to close and reopen max for every frame? I get this when rendering a sequence either with DR or just plain old backburner frames. For every frame the server seems to dump max and reload the scene from scratch. This isn't the case with my main workstation where the job is running from, where it only loads the scene once.

This is the case even when the HDcache is saved out and being read, so just pure frame rendering happening.

My network nodes are super slow as a result of this. They need maybe 1 min or so to load the file and get going each frame.

Any ideas?

[Juraj]

Always wondered the same. Esp. noticeably overhead with short render times per frame.

Though as far as I remember (but I could remember wrongly...since I have shit memory) I wondered the same with Vray.

[atelieryork]

Always wondered the same. Esp. noticeably overhead with short render times per frame.

Though as far as I remember (but I could remember wrongly...since I have shit memory) I wondered the same with Vray.

Yes I seem to remember this being the same with vray too. I really don't understand why it happens. If the main machine can keep it loaded in memory and simply flip to the next frame and get moving why can't the other nodes?

Maybe I'm doing something stupid. It's been a while since I've done any animation.

[maru]

I think that this was due to some Autodesk licensing policies. Not sure, though.

[atelieryork]

I think that this was due to some Autodesk licensing policies. Not sure, though.

So is this expected behaviour for any animations?

I'm wondering if it's possible to actually manually specify for each node to render a chunk of frames, such as:

node 1 - render 0-100
node 2 - render 101-200
node 3 - render 201-300
etc.

And maybe it will avoid restarts between each frame... Not sure...

[Ondra]

I think that this was due to some Autodesk licensing policies. Not sure, though.

So is this expected behaviour for any animations?

I'm wondering if it's possible to actually manually specify for each node to render a chunk of frames, such as:

node 1 - render 0-100
node 2 - render 101-200
node 3 - render 201-300
etc.

And maybe it will avoid restarts between each frame... Not sure...

this is again going in the "corona should re-implement backburner/deadline" territory ;)

[johan belmans]

I think that this was due to some Autodesk licensing policies. Not sure, though.

So is this expected behaviour for any animations?

I'm wondering if it's possible to actually manually specify for each node to render a chunk of frames, such as:

node 1 - render 0-100
node 2 - render 101-200
node 3 - render 201-300
etc.

And maybe it will avoid restarts between each frame... Not sure...

this is again going in the "corona should re-implement backburner/deadline" territory ;)

and what about "Corona will develop its own render management software?" :-)