Warp <war### [at] tagpovrayorg> wrote:
> MichaelJF <mi-### [at] t-onlinede> wrote:
> > I'm certainly no expert at this. But POV leaves a state file when interrupted
> > otherwise an image. So it should not be impossible. But with a multicore machine
> > the continue option works only if all threads have left no "whole" in the
> > picture. That means if a block is not finished but an other which is later in
> > the sequence the blocks are worked through from another thread is (may be the
> > first contains some glass the second not, so the later thread is ready before
> > the first) than "continue" continues behind the later thread overlooking the
> > "whole" from the first unfinished thread. So if you have to interrupt a
> > rendering since you need your machine for other purposes, you have to be lucky
> > to can use the +c. IMO this issue is more important then the occasional updates
> > or the sleeps, which can be avoided easily with the update options or the energy
> > options Stephen pointed out.
>
> Are you saying that +C doesn't currently work, or are you just guessing?
>
> I wasn't talking about the +C option per se. I was just talking about a
> possible convenience feature in winpov that would suggest the user to
> continue the render if povray was closed the last time while it was
> rendering.
>
> --
>                                                           - Warp

No, I'm not guessing, this is an observation. We had a discussion about this
issue some months ago and Thomas de Groot observed the same. Look at

http://news.povray.org/povray.beta-test/thread/%3Cweb.5033e17517f31266b62e53d00@news.povray.org%3E/

Best regards,
Michael

Post a reply to this message