|
![](/i/fill.gif) |
In most cases it would give a general time frame, but an experienced user can
probably guess it more accurately himself. Extreme cases are not rare in POV
renderings. A small part of the image may take up most of the time. Linear PPS
calculation (or even one based on previous data) can _not_ take this into
account. And POV can't predict the number of rays it has to trace for a
particular pixel or line.
Like I said, a progressive histogram approach might do the trick. It would hold
the added advantage of showing a progressively refined preview of the entire
scene before rendering is done. I would certainly consider this an useful
option.
Adding render time calculation based on time spent & PPS should be trivial. I
can only guess, but perhaps the very reason it hasn't been done already is the
inaccuracy of this method in raytraced scenes.
Margus
Remco de Korte wrote:
>
> I don't agree. It's quite meaningful to me to see whether a render will be
> finished the same day or two days later. That's something you can calculate for
> yourself, which is what I'm doing now, but POV has the data already at hand.
> This would be even more meaningful with animations.
> You could use a straightforward calculation (based on PPS) or a more advanced
> one (based on a series of PPS-data).
>
> So long,
>
> Remco
> http://www.xs4all.nl/~remcodek/vic.html
Post a reply to this message
|
![](/i/fill.gif) |