 |
|
|
|
|
|
| |
| |
|
|
From: Bob Hughes
Subject: Re: beta 8: interupt animation causes runtime error
Date: 17 Aug 2005 20:12:23
Message: <4303d267$1@news.povray.org>
|
|
|
| |
| |
|
|
Encountered a different error while rendering scenes\animations\bounce.pov,
this one popped up during frame 439 of 500.
"This application has requested the Runtime to terminate in an unusual
way." No error code this time. I was leaving the computer alone during this
time.
Windows XP HE SP2
POV 3.7.0.beta.8.icl8.win32
Post a reply to this message
|
|
| |
| |
|
|
From: Chris Cason
Subject: Re: beta 8: interupt animation causes runtime error
Date: 13 Sep 2005 12:50:41
Message: <43270361@news.povray.org>
|
|
|
| |
| |
|
|
Bob Hughes wrote:
> Encountered a different error while rendering scenes\animations\bounce.pov,
> this one popped up during frame 439 of 500.
>
> "This application has requested the Runtime to terminate in an unusual
> way." No error code this time. I was leaving the computer alone during this
> time.
>
> Windows XP HE SP2
> POV 3.7.0.beta.8.icl8.win32
Can you reproduce either of these errors reliably ? I haven't had it happen
so far.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
From: Bob Hughes
Subject: Re: beta 8: interupt animation causes runtime error
Date: 13 Sep 2005 14:47:51
Message: <43271ed7$1@news.povray.org>
|
|
|
| |
| |
|
|
"Chris Cason" <nos### [at] deletethis povrayorg> wrote in message
news:43270361@news.povray.org...
> Bob Hughes wrote:
>> Encountered a different error while rendering
>> scenes\animations\bounce.pov,
>> this one popped up during frame 439 of 500.
>>
>> "This application has requested the Runtime to terminate in an unusual
>> way." No error code this time. I was leaving the computer alone during
>> this
>> time.
>>
>> Windows XP HE SP2
>> POV 3.7.0.beta.8.icl8.win32
>
> Can you reproduce either of these errors reliably ? I haven't had it
> happen
> so far.
Tried that animation again just now and it did happen again, this time at
frame number 448. Isn't due to screen saver, apparently, which was my first
thought.
I'm going to run it on my other computer and I'll be back soon to report
anything about that.
Haven't been using the beta much at all lately and especially not
animations, so I can't say anything more about the original problem I told
of. Now is my chance so I'll be stopping animation renderings to check on
that some more.
Post a reply to this message
|
|
| |
| |
|
|
From: Hughes, B
Subject: Re: beta 8: interupt animation causes runtime error
Date: 13 Sep 2005 15:31:05
Message: <432728f9$1@news.povray.org>
|
|
|
| |
| |
|
|
Happens on this other machine, too, except error popped up at frame 442
instead of 448.
Both are DELL's, first was notebook, this one a desktop and both are XP Home
Edition Service Pack 2.
Notebook has two half gig memory modules and the desktop has 768 MB memory.
Plenty free disk space on them.
Post a reply to this message
|
|
| |
| |
|
|
From: Chris Cason
Subject: Re: beta 8: interupt animation causes runtime error
Date: 13 Sep 2005 17:41:26
Message: <43274786$1@news.povray.org>
|
|
|
| |
| |
|
|
Hughes, B. wrote:
> Happens on this other machine, too, except error popped up at frame 442
> instead of 448.
Thanks for the report; this has been fixed. Still haven't seen the 'pure
virtual function call' one happen though.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
From: Bob Hughes
Subject: Re: beta 8: interrupt animation causes runtime error
Date: 13 Sep 2005 20:41:50
Message: <432771ce$1@news.povray.org>
|
|
|
| |
| |
|
|
"Chris Cason" <nos### [at] deletethispovrayorg> wrote in message
news:43274786$1@news.povray.org...
> Hughes, B. wrote:
>> Happens on this other machine, too, except error popped up at frame 442
>> instead of 448.
>
> this has been fixed.
Great!
> Still haven't seen the 'pure virtual function call'
After trying to interrupt some sample animation files (by clicking Stop
button or pressing Alt+G keys) I couldn't duplicate the error on the desktop
computer.
However, it continues to cause that same error (called R6025) on my notebook
computer. Sometimes I must hit Run/Stop twice in rapid succession at the
beginning to make the error show itself but other times it simply happens
during any part of the rendered frames, or parsing of them, by a single
click on the Stop button.
Hopefully something can be figured out about it. Any other info I can
possibly provide? Just name it.
Post a reply to this message
|
|
| |
| |
|
|
From: Chris Cason
Subject: Re: beta 8: interrupt animation causes runtime error
Date: 14 Sep 2005 22:53:10
Message: <4328e216$1@news.povray.org>
|
|
|
| |
| |
|
|
Bob Hughes wrote:
> Hopefully something can be figured out about it. Any other info I can
> possibly provide? Just name it.
unless it has the function name or an address, probably not.
if you can still make it happen with beta 9, let me know and I'll see if I
can build a version that hooks the pure virtual function default handler with
something that gives more information.
thanks,
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
From: Bob Hughes
Subject: Re: beta 8: interrupt animation causes runtime error
Date: 15 Sep 2005 04:53:20
Message: <43293680$1@news.povray.org>
|
|
|
| |
| |
|
|
Thanks for the effort Chris (and all), good to see bounce.pov animation get
through all 500 frames okay. Looks like this other problem is not gone from
beta 9-- for me anyhow.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hmmm...
getting a pure virtual call error consistantly whilst about 31% through a single
800x600 frame render. Except, I'm using 3.6 for Windows. I searched and it
brought me to this thread. Any suggestions? - Graham
"Bob Hughes" <omniverse@charter%net> wrote:
> Thanks for the effort Chris (and all), good to see bounce.pov animation get
> through all 500 frames okay. Looks like this other problem is not gone from
> beta 9-- for me anyhow.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Graham schrieb:
>
> getting a pure virtual call error consistantly whilst about 31% through a single
> 800x600 frame render. Except, I'm using 3.6 for Windows. I searched and it
> brought me to this thread. Any suggestions? - Graham
Is there anything special in that region of the image?
Could you try simplifying the scene to the simplest that still exhibits
the error?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
