After looking at my Java books, tutorials and JBuilder for half a year 
and doing nothing with it, I got inspired by the erosion thread in p.a-u. 
Got myself Python and made a very simple, but deadslow, df3 erosion 
script.

Rendertime for 20 images ~50 minutes.
The script, running via Pre_Frame_Command took ~9 hours to do its job.

I noticed a memory use getting higher and higher per frame, strange. 
Looking in winNT's taskmanager, there are two processes MegaPov.exe. One 
using 4664k and steady, one using 90848k (frame 20) and rising. Is this a 
result of Pre_Frame_command?


Ingo

-- 
Photography: http://members.home.nl/ingoogni/
Pov-Ray    : http://members.home.nl/seed7/

Post a reply to this message

Attachments:
Download 'Erode50.png' (38 KB)

Preview of image 'Erode50.png'