I'm running WinXP on an AMD Athlon 1 gHz, with 512mb pc2100, Aopen ti4600 geforce 4. I created a scene (file is 7,466 kb) and imported a poser 4 figure. I rendered the scene twice with no problems. Immediately after rendering, I closed the file and the program. Later, I tried to reopen the file and it took about 10 minutes to load. I wasn't happy with any changes I made, so I closed the program again. Now, I can't get the file to load at all - I keep getting out of memory messages and XP informs me that it's increasing the size of the page file. The program also stops responding (during rendering) after I added the light cones to the "planet" animation tutorial on the Eovia website. (http://www.eovia.com/community/tutorials_car.jsp) I'm wondering if my computer needs to be upgraded or if there's some other cure for these problems. My motherboard will only accomodate 1gig of memory. Do I need to upgrade memory or is there something else that's going on? Any guesses or suggestions are certainly welcome - I feel like I'm learning quite a bit, but this is really frustrating. Maybe I should try a different software???

I run C on a laptop with 256M RAM P3 1.6Ghz with no problems. I ran 1.1 before, and now run C2 with the patch without ahitch. Try trashing the Carrara.ini file. Carrara will rebuild the file, (it's the preference file,) and then you'll be at a fresh starting position. Actually, if you save it to aanother folder, with a new name (e.g. carraraOLD.ini,) if this doesn't fix the problem, then send the .ini file to eovia support. They can check into it to see if it's a bug that way. Good luck!

Thanks for taking the time bluetone. I renamed and moved the ini, but am seeing the same thing. The file loads to about 44% almost immediately, but then slows to a crawl. Then, after about 6 minutes the "open" dialog box appears so I can direct it to the texture files for the poser figure. As soon as this dialog pops up, Carrara posts the "critically low memory" warning. I've tried clicking ok on the open dialog but it just pops up again along with the memory warning. I emailed Eovia regarding the problem last week, but haven't heard back from them yet. At any rate, from what you've told me, my hardware should run this ok. Thanks again.

This is just a wild guess, not having had this problem myself with any 3D program, but perhaps there is a corrupted model in your scene? You could try removing the Poser figure and save the scene under a different name and close the program. Then try firing up Carrara and see if the Poser-less scene opens fast. If not, then it might be another model that's being mean. Otherwise, it sounds like some kind of big memory leak. Memory leaks were rampant under Windows 3.1 and Windows 95. Windows 98 was much better. I wouldn't have thought Windows XP would suffer from that. Lammoth

That1guy, you are not alone. It sounds like you have plenty of machine but being an XP user myself, and experiencing some of the same woes, I wonder if Carrara1.1 was really designed to run on that platform. Sorry I can't offer any advice since I couldn't find a fix to my problems but if you ever come across a fix or workaround PLEASE let me know so that I can use my program again. It is useless on my machine. Best of luck! SET

TB, not the kind of news I was hoping for, but at least I'm not alone in this. :o) I'm going to try and recreate the scene once again, this time rendering at each new additional element in the scene. Maybe I can at least pinpoint which element is causing the problems and work from there. I'll definitely keep ya posted if I manage any concrete results. BTW thanks to Lammoth and Blutone for their time to respond - they've generated ideas I probably wouldn't have tried on my own. If any of you would like to try and check out the file, I'd be glad to submit it here or email. :o) Being pretty busy myself, I certainly understand if there are no takers on this so don't feel compelled by me to do so. :o)

You can send the file to my Yahoo email account at: alduin@yahoo.com I have Carrara 2.0.21b and am running on Windows 98SE, so the problem may or may not manifest on my system. I'm willing to give it a shot though. Lammoth