I can't find any comment on this one, so I'm posting it, in case it
wasn't mentioned before.
I've just recently downloaded POV-Ray3.5 Beta 8 for Windows,
own a 800MHZ Athlon, 340 MB RAM with Windows98.

The source is rather difficult to recreate (since it requires a particle

system of mine), but perhaps the following is sufficient:

I've changed the quickres.ini, so that I have a selection
with 320x240, 175 Frames, cyclic animation.
In the command-line option, I added +AM2 +A0.3 +R2, so that
the 175 frames are rendered with Antialiasing.
In the scene, there is a mesh (made up of six triangles) and a blox,
which has the new reflection on it (reflection{.1, .9 falloff 2
metallic}).

The thing that happens after some irregular amount of frames
(mostly somewhat between 5 and 20), it just stays stuck in a frame,
tracing something seemingly forever, though the frames normally required

only about 40 seconds tracing.
The timer in the lower right corner moves on, the PPS count drops slowly

with time, but the rendering line doesn't go on (stays fixed somewhere
in
the blob, not when it first hits it).

The effect somehow doesn't reproduce itself exactly, but I'll spend some

more time figuring that out.

Hope someone has a clue what the reason is!

Tim

Post a reply to this message

I've also tried it using no command-line options, but found that this
error occurs in ANY animation. I've tried to rerender the insert-meu-images,

and it stuck there as well.
Several other animations I've tried also stop short of moving on at some
point
of time. May this be due to the read-write restrictions (though they are set

correctly, with output to folder as mentioned in doc).

Post a reply to this message

Again me!

I've restarted the computer, and since then, no crash occurred anymore.
Perhaps the problem was, that I didn't restart Windows98 right after
installing Beta 8, but used it right away instead.

Unless I post something new about this "bug", think of it as "not-a-bug". It's
probably just some windows-crap-thingy. If it reappears (against all
expectations now), I'll post it anew.

Thanks for your patience (anyone's who read this),

Tim

Post a reply to this message