HI, all,

I've been playing with Apo 2.05b2 for a week or so. I started a render to disk a few days ago that said it was going to take 80+ hours, but I let it go because I liked the image. This morning the remaining time was finally down to 0 after about 82 hours, but the elapsed time just keeps going up, and the file has not been saved to disk. Elapsed Time is over 94 hours now and still going. Task Manager says it's not using any CPU cycles, but it still has over 140 MB of memory allocated.

I'd really rather not have to kill it and start over, since it took almost 4 days, but I don't see any alternative. Anybody got any ideas for salvaging my render, or what went wrong?

Thanks,
Dennis

Attached Link: http://www.apophysis.org/list.html

You should probably ask this in the APO mailing list.  I remember a problem with rendering from waaaaaaaay back, but I thought it had been resolved.  You can join the list at the link above.

~Viv

Thanks for the suggestion, Viv. I tried joining the Apo list several times yesterday and today. I figured they would be more likely to have an answer for me, but my emails to them always bounce.

"The following addresses had delivery problems:

apophysis-subscribe@lists.fractalus.com
    Permanent Failure: Other address status
    Delivery last attempted at Thu, 25 Jan 2007 05:49:21 -0000"

And I don't see any other way to contact the list and let them know there's a problem.

Dennis

This sounds normal ...on my P4 2.8ghz dual core it takes my PC 40+ hours to render an image 6000x4500...it renders the image in 5 slices & the final slice seems to take the longest... i nearly quit the program at this point thinking it had locked up, but it eventually renders the file to the h/d & all is well...just be patient :)

Andy