"You can stop and save an image partially through the render, and close Vue altogether. Open Vue back up again, open your scene file, go to Picture>Resume Render and it starts back up where you left it."

I'm quite aware of this VUE feature, however upon restarting Vue the memory load, within about 45 seconds, goes right back to the edge of the memory abyss! You can also quit C5Pro, shutdown the PC, and do the same. My point was that Vue loads back the entire render POINT, thereby not relieving memory restrictions when rendering a very large file.

You are comparing C5Pro to V5I it is appropriate to mention C5Pros very good (but certainly not comparable to 3DS Max 8 or 3DS Max 8 price!) modeling tools. I think it is nice that I can do some very good modeling in the same application that does excellent outside scenes. C5Pro has most of V5Is features, and does a better job in terrain modeling. If you havent delved into C5Pro to any real depthhow do you know?

Actually, the biggest problem I'm having with Carrara is not "memory leaks," but memory allocation errors, which is not the same thing. I reported this to Eovia's "Bug Line." It will be interesting to see what is done about it. I'll give them some slack for a while as the application is considerably more stable than V5I was/is.

Message edited on: 01/12/2006 20:43