 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I installed POVRAY 3.7 Beta 34 on a Vista 64 Ultimate machine, and it was quite
happy to render an animation (started from an ini file) for almost 1600 frames,
or about 18 hours on an AMD quad core. At this point, POVRAY reported an error
regarding not being able to find the input file, despite trying an extension
blah, blah, blah. My question is: how could things go so well for 18 hours,
and then just tank?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>I installed POVRAY 3.7 Beta 34 on a Vista 64 Ultimate machine, and it was
>quite
> happy to render an animation (started from an ini file) for almost 1600
> frames,
> or about 18 hours on an AMD quad core. At this point, POVRAY reported an
> error
> regarding not being able to find the input file, despite trying an
> extension
> blah, blah, blah. My question is: how could things go so well for 18
> hours,
> and then just tank?
I'm just guessing, but it could be ...
(1) a small memory leak / out of memory.
(2) you overheated the CPU.
(3) the HD is getting older and flipped a bit.
(4) too many open files.
(5) somthing different (image map?) was loaded on the failed frame.
(5) something else =/
Just restart the animation on the frame where it failed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I suspect it's a memory leak because there was nothing different about the
failed frame, I had no other files open, the HD is only a year old, and an
overheated CPU should have cooled after the error, thereby giving me a bunch of
frames before overheating again. Instead, I only got a few frames after
restarting the animation. However, closing POVRAY, and then restarting the
animation seemed to produce much better results. I suspect, though, that once
I check it again, it'll have failed - again suggesting that it takes many hours
for the leak to take its toll.
"Tim Attwood" <tim### [at] anti-spam comcastnet> wrote:
> >I installed POVRAY 3.7 Beta 34 on a Vista 64 Ultimate machine, and it was
> >quite
> > happy to render an animation (started from an ini file) for almost 1600
> > frames,
> > or about 18 hours on an AMD quad core. At this point, POVRAY reported an
> > error
> > regarding not being able to find the input file, despite trying an
> > extension
> > blah, blah, blah. My question is: how could things go so well for 18
> > hours,
> > and then just tank?
>
> I'm just guessing, but it could be ...
> (1) a small memory leak / out of memory.
> (2) you overheated the CPU.
> (3) the HD is getting older and flipped a bit.
> (4) too many open files.
> (5) somthing different (image map?) was loaded on the failed frame.
> (5) something else =/
>
> Just restart the animation on the frame where it failed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 2 Sep 2009 15:05:31 EDT, "gnu_uzer" <nomail@nomail> wrote:
> I suspect, though, that once
>I check it again, it'll have failed - again suggesting that it takes many hours
>for the leak to take its toll.
Have a look at the performance tab in the task manager. If the memory usage
"sawtooths" upwards then it probably is a memory leak. This used to happen in
Pov 3.5 IIRC. As I workaround I used to split my animations into batches in ini
files and use the file queue to run them one after the other.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
