here we go
most PC today have more then one CPU - if I define a buckt size of 64 sometimes one bucket need more time to finish and all other CPU stay idle until the last bucket is done
to avoid it why not having a dynamic bucket size?
image a "buckte render-way" (how to say it better) spiral from out to in
as closer the image center comes as small are the buckets until reaching a bucketsize limit
next idea
when I need to pre-render a GI map I can use DR or do all with one PC
also possible is doing it via backburner and assign each mashine a couple of frames and save it all to an unique file
if done merge all into one final GI map
but thats a lot of admin
I whould like to see a button to save the GI map frame by frame separatly
you ask me why?
if you need to do 100 frames with one PC incremental it takes 5min for the first frame and 1 min for all others = in total 104 min to do all
if I have 100 PC and do all frames as single mode I need 5 min (+the time to merge all into one)
the best way whould be sending that job to backburner with single frame+dont render final image+save GI frame0000 up to frame0100
at the end I merge down *.vrmap into one final map
we all know the feeling when rendering over night a GI solution and the next morning the mashine have a blue screen by writeing to file (or one of the DR nodes is dead)
GImap isnt readable and we start all over again
Backburner could easily buffer all that
ps
please edit the vrmap viewer
why typing all map name in the command line insteat of
vrmapviewer.exe -laod *.vrmap -save X.vramp -nodisplay
most PC today have more then one CPU - if I define a buckt size of 64 sometimes one bucket need more time to finish and all other CPU stay idle until the last bucket is done
to avoid it why not having a dynamic bucket size?
image a "buckte render-way" (how to say it better) spiral from out to in
as closer the image center comes as small are the buckets until reaching a bucketsize limit
next idea
when I need to pre-render a GI map I can use DR or do all with one PC
also possible is doing it via backburner and assign each mashine a couple of frames and save it all to an unique file
if done merge all into one final GI map
but thats a lot of admin
I whould like to see a button to save the GI map frame by frame separatly
you ask me why?
if you need to do 100 frames with one PC incremental it takes 5min for the first frame and 1 min for all others = in total 104 min to do all
if I have 100 PC and do all frames as single mode I need 5 min (+the time to merge all into one)
the best way whould be sending that job to backburner with single frame+dont render final image+save GI frame0000 up to frame0100
at the end I merge down *.vrmap into one final map
we all know the feeling when rendering over night a GI solution and the next morning the mashine have a blue screen by writeing to file (or one of the DR nodes is dead)
GImap isnt readable and we start all over again
Backburner could easily buffer all that
ps
please edit the vrmap viewer
why typing all map name in the command line insteat of
vrmapviewer.exe -laod *.vrmap -save X.vramp -nodisplay