Mark Wagner <mar### [at] gtenet> wrote:
:>  Does it work with interrupted renders?

: Yes.

  How?

:>  How much will it take memory?

: Hopefully, not much more than current rendering methods.

  How can this be possible if you have to keep the whole image in memory
(for example for the antialiasing pass)?

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

On 15 Nov 2000 05:19:40 -0500, Warp <war### [at] tagpovrayorg> wrote:

>:>  How much will it take memory?
>
>: Hopefully, not much more than current rendering methods.
>
>  How can this be possible if you have to keep the whole image in memory
>(for example for the antialiasing pass)?

POV-Ray for Windows already does that when display is turned on.


Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] usanet
TAG      e-mail : pet### [at] tagpovrayorg

Post a reply to this message

Warp wrote in message <3a12633c@news.povray.org>...
>Mark Wagner <mar### [at] gtenet> wrote:
>:>  Does it work with interrupted renders?
>
>: Yes.
>
>  How?


It stores the number of the last pixel computed in the comments section of
the image file, and uses the number of each pixel to figure out which pixel
to compute next.  This isn't true random order, it will just look random.

>:>  How much will it take memory?
>
>: Hopefully, not much more than current rendering methods.
>
>  How can this be possible if you have to keep the whole image in memory
>(for example for the antialiasing pass)?


It won't need to.  It will store the image on disk, probably as a temporary
uncompressed TGA file.

Mark

Post a reply to this message