lasco
09-29-2004, 10:11 AM
Hi,
Let me just share with you a very cool new exiting feature of LWSN :
MIXING SCENES while rendering !
I explain : as you know when you render an
animation the best way to save computing time is
to separate your scene in "parts", depending of the
camera position.
Then if you render for example :
- Scene 1 : frames 0 to 50
- Scene 2 : frames 50 to 150
etc.
you should delete items that are out of the camera angle of
view in each scene, and then save RAM as well as time
during the rendering process.
I did this few days ago, and setted 2 "parts" of a same scene :
- Scene A1 : frames 200 to 260
- Scene A2 : frames 261 to 340
Just look at the images below,
you see that there is a building on the very right of the
frame 311, and that this building is not seen by the camera
on frame 250. That's why I deleted the building (as well as other
items like lights and trees) in the FIRST scene (frames 200 to 260).
But of course I never deleted these items from the SECOND
scene (261 to 340).
Though as you can see on frame 312, these items are not rendered,
I'm sure I did not mistake because I just launched the 2 scenes
at the same time in the LWSN render queue, and discovered
this after the rendering was made.
But what makes me even more think that LWSN MIXES scenes
is that this error "only" happened on about 1 frame on 4
for all the second scene. Which means that around 25 frames
were like this but not the others.
I guess this is because only one of the 4 nodes of my network
mistaked and loaded the camera path of the second scene
(rendered the good frames)
but the objects of the FIRST scene !!
Now that's the third very serious bug I meet with LWSN, during the last
3 weeks I already wasted around a hundred hours of computing with bugs
and crashes.
Do you folks think that one day NT sells us a real network rendering
engine or what ?
ps : Please don't tell me to try some Spider or Amleto third part,
I do think these are ADDITIONAL featuring plugs and consider this
differently than buying a tool, Lightwave, that does not work itslef.
In other words I don't find regular at all to have to try / learn /
buy third parts ONLY because LWSN is nothing but toy.
Let me just share with you a very cool new exiting feature of LWSN :
MIXING SCENES while rendering !
I explain : as you know when you render an
animation the best way to save computing time is
to separate your scene in "parts", depending of the
camera position.
Then if you render for example :
- Scene 1 : frames 0 to 50
- Scene 2 : frames 50 to 150
etc.
you should delete items that are out of the camera angle of
view in each scene, and then save RAM as well as time
during the rendering process.
I did this few days ago, and setted 2 "parts" of a same scene :
- Scene A1 : frames 200 to 260
- Scene A2 : frames 261 to 340
Just look at the images below,
you see that there is a building on the very right of the
frame 311, and that this building is not seen by the camera
on frame 250. That's why I deleted the building (as well as other
items like lights and trees) in the FIRST scene (frames 200 to 260).
But of course I never deleted these items from the SECOND
scene (261 to 340).
Though as you can see on frame 312, these items are not rendered,
I'm sure I did not mistake because I just launched the 2 scenes
at the same time in the LWSN render queue, and discovered
this after the rendering was made.
But what makes me even more think that LWSN MIXES scenes
is that this error "only" happened on about 1 frame on 4
for all the second scene. Which means that around 25 frames
were like this but not the others.
I guess this is because only one of the 4 nodes of my network
mistaked and loaded the camera path of the second scene
(rendered the good frames)
but the objects of the FIRST scene !!
Now that's the third very serious bug I meet with LWSN, during the last
3 weeks I already wasted around a hundred hours of computing with bugs
and crashes.
Do you folks think that one day NT sells us a real network rendering
engine or what ?
ps : Please don't tell me to try some Spider or Amleto third part,
I do think these are ADDITIONAL featuring plugs and consider this
differently than buying a tool, Lightwave, that does not work itslef.
In other words I don't find regular at all to have to try / learn /
buy third parts ONLY because LWSN is nothing but toy.