Hello,

is it possible to interrupt the render, switch the computer off and later,
continue the render where it has been stopped?

PS  I am French, I can't speack english fluently. I hope I was clear :)

thanks

Post a reply to this message

"Sylvax" <syl### [at] darthsylvaxcom> wrote in message
news:3b83941d@news.povray.org...
> Hello,
>
> is it possible to interrupt the render, switch the computer off and later,
> continue the render where it has been stopped?

    Yes. In Windows, if you stop a render, a new selection appears in Render
> Rerun that has the name of your file.

    So you would use 'Render > Rerun > Continue Yourfile.pov"

Post a reply to this message

Sylvax wrote:
> 
> Hello,
> 
> is it possible to interrupt the render, switch the computer off and later,
> continue the render where it has been stopped?

This can be done with the '+c' options (or like Bill explained in the
windows version) but be careful when using radiosity because the break can
be visible then.

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

If the "break" with Radiosity can become visible, does that mean that two
renders of the same scene would give different results?



"Christoph Hormann" <chr### [at] gmxde> wrote in message
news:3B8### [at] gmxde...
>
>
> Sylvax wrote:
> >
> > Hello,
> >
> > is it possible to interrupt the render, switch the computer off and
later,
> > continue the render where it has been stopped?
>
> This can be done with the '+c' options (or like Bill explained in the
> windows version) but be careful when using radiosity because the break can
> be visible then.
>
> Christoph
>
> --
> Christoph Hormann <chr### [at] gmxde>
> IsoWood include, radiosity tutorial, TransSkin and other
> things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

stefkeB wrote:
> 
> If the "break" with Radiosity can become visible, does that mean that two
> renders of the same scene would give different results?
> 

No, but if you render a subset of a scene starting in the middle it will
differ from the same section in the whole render.  

I know Gilles Tran for example has made good experience with 'stripe
rendering' of radiosity scenes but it is critical and you should know what
you are doing.

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

Christoph Hormann <chr### [at] gmxde> wrote:
: This can be done with the '+c' options (or like Bill explained in the
: windows version) but be careful when using radiosity because the break can
: be visible then.

  This is not so simple.

  POV-Ray saves the radiosity data to an .rca file. This allows it to
continue an interrupted render without problems, as it loads the data from
that file and continues as if nothing had happened.

  The problem can happen if you try to continue the render without the
.rca file (eg. you continue the render in another computer without copying
the .rca file there, only the scene file(s) and the partial image).

  The main problem with radiosity is not interrupted/continued renders,
but partial renders (which is a different thing). If you render one half
of the image (with +er.5) in one place and the other (with +sr.5) in another,
you'll get a visible line. This is because the radiosity data from the first
half is not taken into account in the second half and thus the illumination
is different.

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

Warp wrote:
> 
>   This is not so simple.
> 
>   POV-Ray saves the radiosity data to an .rca file. This allows it to
> continue an interrupted render without problems, as it loads the data from
> that file and continues as if nothing had happened.

If you use 'always_sample off'

>   The problem can happen if you try to continue the render without the
> .rca file (eg. you continue the render in another computer without copying
> the .rca file there, only the scene file(s) and the partial image).
> 
>   The main problem with radiosity is not interrupted/continued renders,
> but partial renders (which is a different thing). If you render one half
> of the image (with +er.5) in one place and the other (with +sr.5) in another,
> you'll get a visible line. This is because the radiosity data from the first
> half is not taken into account in the second half and thus the illumination
> is different.

Pressing the stop button in WinPov does not leave the .rca file BTW.

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

Christoph Hormann <chr### [at] gmxde> wrote:
: If you use 'always_sample off'

  I'm talking about POV-Ray 3.1 here. MegaPov is no different from that.

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

Warp wrote:
> 
> Christoph Hormann <chr### [at] gmxde> wrote:
> : If you use 'always_sample off'
> 
>   I'm talking about POV-Ray 3.1 here. MegaPov is no different from that.
> 

Then 'always_sample' does not work as i expect it.  And a quick test also
confirms that:  Renders with no pretrace (start=end=1) look very similar
no matter if 'always_sample' is on or off.

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

thanks a lot

Post a reply to this message