- Mon Jul 04, 2005 10:32 pm
#42857
I'm running mxcl from command line.
At the beginning, each frame of this particular animation takes 3'55" per frame. 12 hours later, each frame takes more than 3 hours to render. If I stop and restart the batch at the last "3-hour frame", it's back to 3'55".
I just setup a new batch and watched the Mem Usage in the Task Manager. The first frame loaded up 133,900K to render. Upon completion, the Mem Usage dropped to 105,000K, and then during the next frame voxelization, shot up to 177, 908K. The thrid frame went up to 233,512K. It doesn't appear to be flushing the memory between frames.
The content of those first 3 frames is nearly identical: A slow camera pan over static objects. With the memory not flushing, I can see how soon the RAM usage will be up to 2GB again, and the render will crawl.
Is this a leak, or a failure to flush, or what?
_Mike
At the beginning, each frame of this particular animation takes 3'55" per frame. 12 hours later, each frame takes more than 3 hours to render. If I stop and restart the batch at the last "3-hour frame", it's back to 3'55".
I just setup a new batch and watched the Mem Usage in the Task Manager. The first frame loaded up 133,900K to render. Upon completion, the Mem Usage dropped to 105,000K, and then during the next frame voxelization, shot up to 177, 908K. The thrid frame went up to 233,512K. It doesn't appear to be flushing the memory between frames.
The content of those first 3 frames is nearly identical: A slow camera pan over static objects. With the memory not flushing, I can see how soon the RAM usage will be up to 2GB again, and the render will crawl.
Is this a leak, or a failure to flush, or what?
_Mike
Last edited by mverta on Tue Jul 05, 2005 8:14 pm, edited 1 time in total.
very nice... and i like it without textures also.... ::
- By hwolfejr
- By choo-chee