POV-Ray : Newsgroups : povray.advanced-users : Continuing a render Server Time
26 Dec 2024 01:49:04 EST (-0500)
  Continuing a render (Message 1 to 3 of 3)  
From: Orchid XP v2
Subject: Continuing a render
Date: 22 Sep 2005 14:23:01
Message: <4332f685@news.povray.org>
Today I tried to continue a render using the +C flag. Much to be 
interest, it spent 3 minutes computing the photon maps for each and 
every frame - only to notice that the frame has already been rendered. 
(I wonder if a similar thing happens with frames that take an 
excessively long time to parse as well?)

I can see why this happens, but... would it be hard to fix?


Post a reply to this message

From: David El Tom
Subject: Re: Continuing a render
Date: 4 Oct 2005 06:34:53
Message: <43425acd$1@news.povray.org>
Orchid XP v2 wrote:
> Today I tried to continue a render using the +C flag. Much to be 
> interest, it spent 3 minutes computing the photon maps for each and 
> every frame - only to notice that the frame has already been rendered. 
> (I wonder if a similar thing happens with frames that take an 
> excessively long time to parse as well?)
> 
> I can see why this happens, but... would it be hard to fix?

The problem IMO is, that povray first parses the scene file before 
looking if the output file exists.
Maybe you could check for the frame file in first place and enable 
photons only if the file doesn't exist, something like
#if (MACRO_TO_CHECK_IF_FILE_EXIST("file_of_interest"))
   #declare PHOTONS = off;
#else
   #declare PHOTONS = on;
#end // if else
Problem would be that for the frame rendered half way befor interuption 
povray wouldn'd use photons for this particular frame.

Easier is to look which frames allready are rendered and start povray 
with +C and the subset frame parameters +SF and maybe +EF
(docs: 3.1.2.1.3 Subsets of Animation Frames)

... dave


Post a reply to this message

From: Orchid XP v2
Subject: Re: Continuing a render
Date: 15 Oct 2005 12:50:52
Message: <4351336c$1@news.povray.org>
>> Today I tried to continue a render using the +C flag. Much to be 
>> interest, it spent 3 minutes computing the photon maps for each and 
>> every frame - only to notice that the frame has already been rendered. 
>> (I wonder if a similar thing happens with frames that take an 
>> excessively long time to parse as well?)
>>
>> I can see why this happens, but... would it be hard to fix?
> 
> 
> The problem IMO is, that povray first parses the scene file before 

Indeed.

> Easier is to look which frames allready are rendered and start povray 
> with +C and the subset frame parameters +SF and maybe +EF

So I found...


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.