Hi Mark,
i dont think RS network rendering is unreliable, but for long sequences and
tons of textures i had it quite often that some random crashes happened..
when this happens overnight and i´m not in the office there is no chance
that real will render on.. but with drqueue exactly this is what happens..
it rerenders missing frames and so if i return in the morning everything is
fine.. most of all full frame distributed rendering is in many cases much
faster then box rendering.. i already had speedups of 200% which is
dramatic..
setting it up for the first time takes of course quite some time, but for
all other boxes it takes me 15minutes here, thats much better then staying
in the office overnight to check if the rendering is still alive..
btw. drqueue rendering also works with boxrendering.. you just need to be
aware that then you have to tell drqueue all pc´s are single cpus and then
tell real to render dualthreaded... its a bit confusing but it works
best regards
Gunnar
----- Original Message -----
From: "Mark Heuymans" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, August 28, 2006 2:50 PM
Subject: Re: frame or sequence based network rendering - solved (tut)
At 13:13 28-8-2006, you wrote:
Hi folks .. especially Bernie ;°)
since a long time i wanted frame based network rendering in real and for
all who are working with real and have a renderfarm it would be such a
cool feature but lately i found there are free scriptable renderqueue
manager available which do just that and much much more.. so i choose
drqueue and made it work with real.. :°) here is the tut:
http://www.3d-cg.de/tut/drq-tut.htm
warning: its not easy as drag?n drop so just try it if you really think
you need such a tool ..
Hi Gunnar,
I'm afraid by the time I'd get it working, the deadlines would be over by
a long time ;)
But many thanks for sharing this!
Apparently, frame based network rendering really needs to be in the nest
SP or V6... it doesn't seem very complicated to implement as long as
there's no simulation involved (and DA could solve that problem since it
has caching).
for those in need of failsafe rendering and speedy network rendering its a
must have ;°) since i use it i found all my overnight renderings to be
absolutelly failsafe..
best regards
Gunnar
Are you implying that Real's native network rendering is unreliable? I
haven't found problems with it so far, love the extra render boxes
appearing seemingly out of nowhere ;)
If so, that would be bad news since I'll have to render thousands of hires
frames next month... and I'd like to use motion blur, another CPU hungry
feature. I use just a small farm (2 computers, 4 cores, more will follow),
I could split an animation manually and render the parts separately if
necessary...
Disabling box rendering would nearly halve the render capacity, so I'll
skip drQueue for now but will keep it in mind for the future!
tnx again,
Mark Heuymans
