 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I posted this before in beta test but someone suggested I should post it
here.
The problem regards the continue function. I am rendering a large (10240 x
7680) image using the switches -D +c 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 those switches)
the render again assuming it will continue where it left off. Instead the
render window shows it starting at 1 again (out of 7679) depsite 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?
Is there some reason why it won't continue?
Anyone else have such a problem and is there a workaround?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hello,
the parameter +c makes povray to continue a *formerly* interrupted render.
therefore you do not need to give it at the first render.
i do not use windows-version, but here is a suggestion:
does povray delete the file after rendering is cancelled?
if not, i do not know more. in linux there is no problem - my render
continues without the +c parameter.
good luck
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The BMP file remains afterwards. The +c was used after the render had
completed a few lines then allowed to run overnight. Then the next morning
(after 600 lines were completed) povray started over. I have tried to
"restart" this render several times and it always wants to start over. This
doesn't happen with every scene only SOME scenes.
What would cause povray to decide that it had to start at the top of the
image? Is there a marker within the BMP file that povray looks for and for
some reason it can't see it and starts over? Hows does povray know where to
restart? This image takes a LONG time to render so continuing is a
necessity.
I am using Windows XP with 256 meg ram, 15 gig free HD space.
"marabou" <agu### [at] igimix net> wrote in message
news:3c2b8858@news.povray.org...
>
> hello,
> the parameter +c makes povray to continue a *formerly* interrupted render.
> therefore you do not need to give it at the first render.
> i do not use windows-version, but here is a suggestion:
> does povray delete the file after rendering is cancelled?
> if not, i do not know more. in linux there is no problem - my render
> continues without the +c parameter.
> good luck
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
what happens, if you use PNG as fileformat ?
--
Jan Walzer <jan### [at] lzernet>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I haven't tried that, but I'll certainly test it to see if it helps.
"Jan Walzer" <jan### [at] lzernet> wrote in message
news:3c2bac55$1@news.povray.org...
> what happens, if you use PNG as fileformat ?
>
> --
> Jan Walzer <jan### [at] lzernet>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Using PNG or TGA allows the continue to work, while the BMP format did not.
Not sure why that is happening, but I guess I'll stick to something other
than BMP for now...
"Jan Walzer" <jan### [at] lzernet> wrote in message
news:3c2bac55$1@news.povray.org...
> what happens, if you use PNG as fileformat ?
>
> --
> Jan Walzer <jan### [at] lzernet>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
try to stick with png ...
it uses a lossless compression and can also support alphachannel
but please try to post this problem to povray.beta-test
--
Jan Walzer <jan### [at] lzernet>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
