problemchild
05-27-2004, 11:43 AM
Hey, anyone seen this happen and have a workaround.
I use a couple nodes for rendering independantly. I don't like to network render off my workstation because if I run into problems I shuts down all the backround work...
so anyway, when I transfer the files to the node to run using LWSN controller, it works perfectly, everytime...
until I give it a scene with a LARGE number of frames and tell it to start rendering in the middle.
e.g.
A scene with 5000 or more frames will render fine if I tell it to start at frame 0. But if I need a particular node to start with frame 3000, it sits on the "rendering polygons" report for the first frame in the job and then a good while later, tells me it's done, without having rendered anything.
any workarounds.
maybe I should try a different controller.
recommendations for someone wanting to run LWSN indenpendantly on different nodes.
cheers
I use a couple nodes for rendering independantly. I don't like to network render off my workstation because if I run into problems I shuts down all the backround work...
so anyway, when I transfer the files to the node to run using LWSN controller, it works perfectly, everytime...
until I give it a scene with a LARGE number of frames and tell it to start rendering in the middle.
e.g.
A scene with 5000 or more frames will render fine if I tell it to start at frame 0. But if I need a particular node to start with frame 3000, it sits on the "rendering polygons" report for the first frame in the job and then a good while later, tells me it's done, without having rendered anything.
any workarounds.
maybe I should try a different controller.
recommendations for someone wanting to run LWSN indenpendantly on different nodes.
cheers