Well.. The topic says it..
My pov goes down when resuming a rendering...
It is my final render, 1024x768x48bpp, radiosity on(rather high) antialisaing mode 2,
recursive 4 ....
So, it takes a while...
But, I had to abort it(chaos, needed the printer....) and since I always have
continued
trace on, I did that..
But when resuming, it went Kapoof...
It reads the prev. image, does the radiosity check (prel. looking very blurred) and
then
goes down on me... Why ??? Is it a bug, does anyone else have this ??

I really want to resume it... (it renders at around 2pps) ..... I have a 166MMX...

Help, please..

//Spider

Post a reply to this message

In article <366EB2B2.C54D8872@bahnhof.se> , Spider <spi### [at] bahnhofse>  wrote:
>I really want to resume it... (it renders at around 2pps) ..... I have a 166MMX...

Also I don't know why it crashes, you can use partial rendering to render the missing
lines and them combine the two images with another program.


    Thorsten

Post a reply to this message

Yes... I could do that, but I'm more irritated by the fact that it crashes...
Thanx for the tip....

//Spider

Thorsten Froehlich wrote:
> 
> In article <366EB2B2.C54D8872@bahnhof.se> , Spider <spi### [at] bahnhofse>  wrote:
> >I really want to resume it... (it renders at around 2pps) ..... I have a 166MMX...
> 
> Also I don't know why it crashes, you can use partial rendering to render the
missing
> lines and them combine the two images with another program.
> 
>     Thorsten

Post a reply to this message

Thorsten Froehlich <fro### [at] charliecnsiitedu> wrote:
: Also I don't know why it crashes, you can use partial rendering to render the
missing
: lines and them combine the two images with another program.

  Partial rendering and radiosity is not a good combination. You will probably
get the two parts with differenct coloration. I discovered this when I
made a radiosity image by calculating the upper half of the image on one
computer and the lower half on another (400MHz Alphas if I remember right).
  When I joined the images, the dividing line was _very_ visible.

-- 
main(i){char*_="BdsyFBThhHFBThhHFRz]NFTITQF|DJIFHQhhF";while(i=
*_++)for(;i>1;printf("%s",i-70?i&1?"[]":" ":(i=0,"\n")),i/=2);} /*- Warp. -*/

Post a reply to this message

In article <366fb140.0@news.povray.org> , Nieminen Mika <war### [at] assaricctutfi> 
wrote:
>  Partial rendering and radiosity is not a good combination. You will probably
>get the two parts with differenct coloration. I discovered this when I
>made a radiosity image by calculating the upper half of the image on one
>computer and the lower half on another (400MHz Alphas if I remember right).
>  When I joined the images, the dividing line was _very_ visible.

Oh, interesting! Then the radiosity buffer is not generated for the whole image.
This effect is a bug! I will forward it to the team.


    Thorsten

Post a reply to this message

Thorsten Froehlich wrote:
> 
> In article <366fb140.0@news.povray.org> , Nieminen Mika <war### [at] assaricctutfi>
> wrote:
> >  Partial rendering and radiosity is not a good combination. You will probably
> >get the two parts with differenct coloration. I discovered this when I
> >made a radiosity image by calculating the upper half of the image on one
> >computer and the lower half on another (400MHz Alphas if I remember right).
> >  When I joined the images, the dividing line was _very_ visible.
> 
> Oh, interesting! Then the radiosity buffer is not generated for the whole image.
> This effect is a bug! I will forward it to the team.
> 
>     Thorsten

Although it could probably be considered a 'bug', it's not worth bothering the
POV-Ray team with.  I'm pretty sure that they know about it, and there's not
much they can easily do about it because of the way POV's radiosity works,
since the 'radiosity buffer' is generated on-the-fly as the image is rendered.
Probably providing some overlap of pixels when rendering partial images could
make the dividing line less visible.

-Nathan

Post a reply to this message