Adam Dershowitz wrote:
>I just downloaded and installed POV-Ray.  I am using OS 10.2 (I saw the
>warning about opening files, so I am working around that).
>I have tried several of the animation examples that are included and
>each time POV-Ray just locks up.  My pointer goes to the spinning "busy"
>circle, and POV-Ray stops responding to anything.  I can then just kill
>the application, but can't do anything else.
>I have tried doing animations in two different ways.  First I loaded one
>of the examples, by dragging the file into the Render queue, then
>started the Render queue to open the file (and render a frame).  Next I
>then changed the render settings for the examples to use the INI file.
>I then selected render, and I get the busy spinning icon, with no
>indication of any progress.
>I also tried loading a different example animation the same way as
>above.  Then I manually changed the setting for the object to animation
>and put in some numbers (the same as what was in the INI).  This time
>the progress window opened, but I got no indication of any progress, and
>POV-Ray again locked up.  Although this time I got 6 images in the same
>directory (named bounce1 -bouce 6) then no additional frames, or
>indication of any progress.
>Again, I had to force quit.
>I am running on a dual G4 1GHz machine, if that matters.  Does this
>relate to the OS 10.2 bug that you mentioned?
>I was about to send this email, but decided to try one other thing.  I
>changed it to only render 4 frames, and then it seemed to work fine.  I
>then tried 10 frames, and it did a few then locked up again.  Seems very
>strange to me.
>
>Please let me know if there is anything that I can do, or what bugs
>might exist to cause this.
>
>I also tried getting info on the POV-Ray executable and set the flag to
>have it open in Classic.  But when I then double clicked on it, it still
>open in OS X, so I was not able to try it that way.  Any idea why that
>is?
>
>
>Thanks much,
>and I am very excited about this program.  Very nice work!
>
>
>der### [at] alummitedu
>

  I was about to post the identical message.  I can confirm the same problem
on OSX 10.1.5.  I also note that the bug always happens after generating
about 5 or 6 frames, regardless of which frame is the 6th.  In other words,
if I start at frame 3, it will choke 6 frames later on frame 9, so it's not
something special about the image in frame 6.  I've tried many conbinations
of output type, internal/external looping, image size, image quality, etc.
Always the same behavior of choking on the 6th frame of the sequence.

  Russ

Post a reply to this message