Hi Mark,
just a quick note.. if you´ll clearly need boxrendering for your project you
should not too soon test drqueue.. i´ll give it a more intense testing as
boxrendering seems to really cause some troubles. in fact if more then one
batchrender instance per pc does boxrendering on the same project the boxes
get mixed up between frames and you get a big mess.. this is dues to the
fact that RS does name the boxes via project name and box index but not via
frame index too..
best regards
Gunnar
----- Original Message -----
From: "Mark Heuymans" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, August 29, 2006 6:53 PM
Subject: Re: frame or sequence based network rendering - solved (tut)
Hi Gunnar,
I see your point, thanks for clarifying. I'll certainly have a go at it
soon, although it seems pretty intimidating at first glance!
good luck,
Mark H
At 15:40 28-8-2006, you wrote:
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
