|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Seems the link vanished. Hope it can be seen now:
http://news.povray.org/povray.beta-test/thread/%3Cweb.5033e17517f31266b62e53d00@news.povray.org%3E/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"MichaelJF" <mi-### [at] t-onlinede> wrote:
> Seems the link vanished. Hope it can be seen now:
>
"http://news.povray.org/povray.beta-test/thread/%3Cweb.5033e17517f31266b62e53d00@news.povray.org%3E/"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"MichaelJF" <mi-### [at] t-onlinede> wrote:
> "MichaelJF" <mi-### [at] t-onlinede> wrote:
> > Seems the link vanished. Hope it can be seen now:
> >
>
>
"http://news.povray.org/povray.beta-test/thread/%3Cweb.5033e17517f31266b62e53d00@news.povray.org%3E/"
Very mysterious, first time a link to the POV-newsgroups doesn't work. It was at
povray.beta-test, "Resuming renders in 3.7 RC6 is confusing at best, broken at
worst" by Chaanakya at 21 Aug 2012 19:30:00.
Best regards,
Michael
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 29.01.2013 21:53, schrieb MichaelJF:
> "MichaelJF" <mi-### [at] t-onlinede> wrote:
>> "MichaelJF" <mi-### [at] t-onlinede> wrote:
>>> Seems the link vanished. Hope it can be seen now:
>>>
>>
>>
"http://news.povray.org/povray.beta-test/thread/%3Cweb.5033e17517f31266b62e53d00@news.povray.org%3E/"
>
> Very mysterious, first time a link to the POV-newsgroups doesn't work. It was at
> povray.beta-test, "Resuming renders in 3.7 RC6 is confusing at best, broken at
> worst" by Chaanakya at 21 Aug 2012 19:30:00.
The very first link worked perfectly fine for me (I haven't tested the
others).
Did anyone ever file a bug report on this issue?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 30/01/2013 20:59, clipka wrote:
>> Very mysterious, first time a link to the POV-newsgroups doesn't work. It was at
>> povray.beta-test, "Resuming renders in 3.7 RC6 is confusing at best, broken at
>> worst" by Chaanakya at 21 Aug 2012 19:30:00.
>
> The very first link worked perfectly fine for me (I haven't tested the
> others).
>
> Did anyone ever file a bug report on this issue?
I don't recall seeing one. It's definitely something we need to look
at as I can't see us releasing 3.7 if it's faulty.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> clipka <ano### [at] anonymousorg> wrote:
>> Am 29.01.2013 01:40, schrieb Chris Cason:
>>> On 28/09/2011 04:58, Cousin Ricky wrote:
>>>> I start an overnight render. I wake up the next morning, expecting a beautiful,
>>>> polished image.
>>>>
>>>> Instead, the damn machine has gone into sleep mode!
>>>
>>> I've added a new 'Prevent sleep while rendering' option to avoid this
>>> issue. It defaults to on, which is probably what most folks would want.
>>
>> Sounds plausible indeed.
>
> That is reasonable. Another thing I do immediatelly after having purchased a new
> windows machine is to let it ask before downloading updates. Updates can cause a
> reboot which is annoying just as well.
>
> Best regards,
> Michael
>
>
When a Windows update need to reboot, it ask you and will wait untill
you sellect "Restart now" or "Ask again in...".
There have been a few times when I had that dialog open for a few days.
Any way, I prefer the setting that download the updated, then ask to
install them.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> On 30/01/2013 20:59, clipka wrote:
>>> Very mysterious, first time a link to the POV-newsgroups doesn't work. It was at
>>> povray.beta-test, "Resuming renders in 3.7 RC6 is confusing at best, broken at
>>> worst" by Chaanakya at 21 Aug 2012 19:30:00.
>>
>> The very first link worked perfectly fine for me (I haven't tested the
>> others).
>>
>> Did anyone ever file a bug report on this issue?
>
> I don't recall seeing one. It's definitely something we need to look
> at as I can't see us releasing 3.7 if it's faulty.
>
> -- Chris
>
One possibility would be to check at some point if some area are still
blank, or have only radiosity pretrace data. It could be done on a
resume or after the trace is otherwise finished.
Another way, would be to keep a per-tread last rendered block and not
just a last rendered block.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot <tenDOTlnDOTretniATtoorgedDOTt> wrote:
> On 3-10-2011 20:14, Darren New wrote:
> > Actually, it looks like XP and 2000 work the way I remember.
>
> I think XP did not go to sleep with a render under way. It maybe slowed
> down though... I am not sure.
>
I've definitely had it go to sleep on me, with a render in progress. Had to turn
the sleep mode off completely, to prevent this (which is probably not good for
the ol' hard drive.) I always thought it was just an odd Windows bug. (But if I
recall correctly, POV-Ray was the only application this happened with...although
it's also the only app I use that churns through work for hours on end.) So
adding a fix to POV-Ray is a great idea!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 30/01/2013 20:51, Alain nous fit lire :
> When a Windows update need to reboot, it ask you and will wait untill
> you sellect "Restart now" or "Ask again in...".
> There have been a few times when I had that dialog open for a few days.
> Any way, I prefer the setting that download the updated, then ask to
> install them.
YMMV, but I happened more than once to get an XP rebooted without
consent because it was updated and unattended long enough (coffee
break... oh, login again!)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |