I posted this before in beta test but now have more data

I'm using Windows XP and creating a large BMP file.

The problem regards the continue function.  I am rendering a large (10240 x
7680) image using the switches -D for the render.  I let the render run
all night and it creates about 600 lines.  I stop the render, reboot the
computer (the next morning) and then start (continue with -D +c)
the render again assuming it will continue where it left off.  Instead the
render window shows it starting at 1 again (out of 7679) despite the fact
that it had completed 600 lines previously.  I examined the BMP and the 600
lines are there but povray insists on starting over at the top.

Why would it do that when I have the +c switch specifed?

I have tested the same thing with a PNG and TGA formats and those continue
normally.  For the time being I am sticking with those other formats.

Is there something that is being misread in the large BMP that would cause
it to not start where it left off?  Not every scene causes this problem only
certain scenes I have made.  Once it gets "stuck" and unable to continue
(after several attempts) I tried using a different format for output ansd
that solved the issue.

Post a reply to this message

Also I am using the Povray 3.5 beta 9

"Patrick Dugan" <pat### [at] usnetcomcorpcom> wrote in message
news:3c34a396$1@news.povray.org...
> I posted this before in beta test but now have more data
>
> I'm using Windows XP and creating a large BMP file.
>
> The problem regards the continue function.  I am rendering a large (10240
x
> 7680) image using the switches -D for the render.  I let the render run
> all night and it creates about 600 lines.  I stop the render, reboot the
> computer (the next morning) and then start (continue with -D +c)
> the render again assuming it will continue where it left off.  Instead the
> render window shows it starting at 1 again (out of 7679) despite the fact
> that it had completed 600 lines previously.  I examined the BMP and the
600
> lines are there but povray insists on starting over at the top.
>
> Why would it do that when I have the +c switch specifed?
>
> I have tested the same thing with a PNG and TGA formats and those continue
> normally.  For the time being I am sticking with those other formats.
>
> Is there something that is being misread in the large BMP that would cause
> it to not start where it left off?  Not every scene causes this problem
only
> certain scenes I have made.  Once it gets "stuck" and unable to continue
> (after several attempts) I tried using a different format for output ansd
> that solved the issue.
>
>
>
>

Post a reply to this message

Gasp! That would make it a 10240x7680x3/2^20=225 MB pic! Why the hell are you using
BMP? :)

--
#local j=text{ttf"arial""JRG".2,0}#local J=0;#while(J<10)#local R=0;#while
(R<2)#local G=0;#while(G<1)#if(inside(j<R,G.1>))object{j scale.025translate
<R-1G-J/20J/-40+2>pigment{rgb<9J>}}#debug"O"#else#debug" "#end#local G=G+
.025;#end#local R=R+.05;#debug"\n"#end#local J=J+1;#end// JRG

Home: http://digilander.iol.it/jrgpov

Post a reply to this message

Yes the files are usually around 250 meg in size.  No big deal really, I
just copy them to a CD and ship them off to the publisher/printer.  Actually
I usually convert them to TIF format but I generally allow Povray to create
them in the "native" format and convert them afterwards.  The size has never
really been a problem.

"JRG" <jrg### [at] hotmailcom> wrote in message
news:3c34a76a@news.povray.org...
> Gasp! That would make it a 10240x7680x3/2^20=225 MB pic! Why the hell are
you using
> BMP? :)
>
> --
> #local j=text{ttf"arial""JRG".2,0}#local J=0;#while(J<10)#local R=0;#while
> (R<2)#local G=0;#while(G<1)#if(inside(j<R,G.1>))object{j
scale.025translate
> <R-1G-J/20J/-40+2>pigment{rgb<9J>}}#debug"O"#else#debug" "#end#local G=G+
> .025;#end#local R=R+.05;#debug"\n"#end#local J=J+1;#end// JRG
>
> Home: http://digilander.iol.it/jrgpov
>
>
>

Post a reply to this message

Patrick Dugan wrote in message <3c34a396$1@news.povray.org>...
>I posted this before in beta test but now have more data
>
>I'm using Windows XP and creating a large BMP file.
>
>The problem regards the continue function.  I am rendering a large (10240 x
>7680) image using the switches -D for the render.  I let the render run
>all night and it creates about 600 lines.  I stop the render, reboot the
>computer (the next morning) and then start (continue with -D +c)
>the render again assuming it will continue where it left off.  Instead the
>render window shows it starting at 1 again (out of 7679) despite the fact
>that it had completed 600 lines previously.  I examined the BMP and the 600
>lines are there but povray insists on starting over at the top.
>
>Why would it do that when I have the +c switch specifed?

Normally, to figure out where a trace was interrupted, POV-Ray reads the
image file, and on the line where the file ends, POV-Ray starts tracing.
Resuming from BMP images is more difficult, since the BMP format stores the
images upside down and the whole image file must exist on the disk in order
for the first pixel of the image to be written.  I'm having trouble making
sense of the source code for reading interrupted BMP images, but it looks
like POV-Ray decides a line hasn't been rendered if the first pixel of the
line is a particular dark shade of grey and the rest of the line is black.

I strongly suggest using a different format for rendering images where you
expect the render to need to be stopped and continued.  I recommend either
the compressed or uncompressed TGA formats.

--
Mark

Post a reply to this message