Hi,

I'm rendering a 30 second animation (640*480) and i've some problems with
the render time (30 minute per frame). My anim uses a detailed model of a
car (the files describing the geometry weigh more than 150 Mo). Is POV Ray
keeping the geometry in memory between frames or (as i think it) the whole
files are parsed again for every frame. Is there a solution for this
problem?? I already use my own application to distribute rendering over a
network... Seems like the only solution i have is to increase the number of
render devices

Regards,

ben

Post a reply to this message

Wasn't it benahpets who wrote:
>Hi,
>
>I'm rendering a 30 second animation (640*480) and i've some problems with
>the render time (30 minute per frame). My anim uses a detailed model of a
>car (the files describing the geometry weigh more than 150 Mo). Is POV Ray
>keeping the geometry in memory between frames or (as i think it) the whole
>files are parsed again for every frame. Is there a solution for this
>problem?? I already use my own application to distribute rendering over a
>network... Seems like the only solution i have is to increase the number of
>render devices

POV is re-parsing the whole thing for each frame.

There seems to be some confusion in your post about whether the problem
is with the parse time or the render time. Look at the stats to see if
parsing or rendering is taking too long, and change your code to improve
the efficiency in that area.

Also check to see if you are running short of memory. 150Mb of geometry
data is going to expand into a huge amount of parsed geometry. Once POV
requires so much memory that the system starts shuffling virtual memory,
the render times go through the roof.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

First of all, i wanted to appologies since i realize i already ask this
question once and you nicely answer me :

http://news.povray.org/povray.animations/thread/%3Cweb.4280796cbc627e41a14d5b880%40news.povray.org%3E/

Then i will specify my question. Saying render time, i mean the whole time
it takes to produce the image. But you're true, i should have said parse
time. Parsing my scene takes at least 2 minutes for each frame (i.e. 27,5
hours for the complete animation afte a rapid calculation). That's why i
wan't to minimize the parsing time (even if it's nothing comparatively to
the render time). But it seems like it is impossible to gain time between
frame.


>Also check to see if you are running short of memory. 150Mb of geometry
>data is going to expand into a huge amount of parsed geometry. Once POV
>requires so much memory that the system starts shuffling virtual memory,
>the render times go through the roof.

No problem with memory since all the render devices have 1Go RAM.

In my scene there is two instance of my car model (itself a CSG union of
multiple mesh2 that independently moving: wheels, body, interior,...). But
the two car aren't of the same color. So POV load the model twice? Or is it
possible to create a instance of the model in memory?


Another question concerning the render time : i've increased the parameters
of antialias to solve a flickering problem
(Sampling_Method=2,Antialias_Depth=3), which explains the render time (that
used to take 5 minutes a frame before that). I think i could gain time here
too, but i know no alternatives to solve that problem...Any suggestion?

Thanks a lot for your answer.

Regards.

ben

Post a reply to this message

Parsing time is the time that takes the program before starting to show the 
preview screen?

Regards,
Oleguer


news:RqnHlAANQ9LDFw$z@econym.demon.co.uk...
> Wasn't it benahpets who wrote:
>>Hi,
>>
>>I'm rendering a 30 second animation (640*480) and i've some problems with
>>the render time (30 minute per frame). My anim uses a detailed model of a
>>car (the files describing the geometry weigh more than 150 Mo). Is POV Ray
>>keeping the geometry in memory between frames or (as i think it) the whole
>>files are parsed again for every frame. Is there a solution for this
>>problem?? I already use my own application to distribute rendering over a
>>network... Seems like the only solution i have is to increase the number 
>>of
>>render devices
>
> POV is re-parsing the whole thing for each frame.
>
> There seems to be some confusion in your post about whether the problem
> is with the parse time or the render time. Look at the stats to see if
> parsing or rendering is taking too long, and change your code to improve
> the efficiency in that area.
>
> Also check to see if you are running short of memory. 150Mb of geometry
> data is going to expand into a huge amount of parsed geometry. Once POV
> requires so much memory that the system starts shuffling virtual memory,
> the render times go through the roof.
>
> -- 
> Mike Williams
> Gentleman of Leisure

Post a reply to this message

"Oleguer Vilella" <ole### [at] infonegociocom> wrote:
> Parsing time is the time that takes the program before starting to show the
> preview screen?


yes

Post a reply to this message