|
 |
Hi!
(running the Windows version under Windows XP home edition, Athlon XP 2800+,
1GB RAM)
Under beta5a and beta6, clicking the "Stop" button/hitting Alt+G twice in a
row while rendering brings up the message "Warning: had to force state to
stopped". This message didn't seem to exist in 3.6.1a. I'd like to know its
meaning... does POV resort to a more drastic way of stopping when i ask it
to stop for the second time?
When developping a scene, i constantly start a test render, see what's
wrong, hit Esc, edit the SDL with POV still rendering, and then click
"Stop"/hit Alt+G twice to stop/relaunch at once. I still need to adjust to
JYR
Post a reply to this message
|
|
|
|
"JYR" <jyr### [at] hotmail com> wrote:
> Under beta5a and beta6, clicking the "Stop" button/hitting Alt+G twice in a
> row while rendering brings up the message "Warning: had to force state to
> stopped". This message didn't seem to exist in 3.6.1a. I'd like to know its
> meaning... does POV resort to a more drastic way of stopping when i ask it
> to stop for the second time?
> When developping a scene, i constantly start a test render, see what's
> wrong, hit Esc, edit the SDL with POV still rendering, and then click
> "Stop"/hit Alt+G twice to stop/relaunch at once. I still need to adjust to
This is just my guess, but this is how I read the situation:
I think this means that the render thread(s) had to be manually terminated
instead of it/them terminating on its/their own. Normally, POV-Ray would
send a "stop" message to the thread(s), which would then finish up their
business (i.e., clean up temp files, deallocate memory, etc.) and terminate
of their own accord. When you hit the "Stop" button twice in a row, the
following happens:
* The first time you click/type it, POV-Ray sends the "stop" message to the
thread, which then responds to POV-Ray that it is stopping, and begins the
finishing-up process.
* The second time you click/type it, POV-Ray again sends the "stop" message
to the thread, which does not respond, because it is in the middle of
finishing up. POV-Ray takes this to mean that the thread has stopped
responding altogether (i.e., has crashed) and manually terminates the
thread, producing the error message you then see.
As far as the reason for the difference in behavior, I have no idea.
I'm no authority on this as I have not looked through the POV-Ray code
myself; however, from what I know of programming/coding, this is why this
happens. (Feel free to let me know if I'm wrong, though.)
Bent
Post a reply to this message
|
|
