I'm guessing that probably 80% (or so) of the problems people are having (after the patch) is lack of sufficient memory. Regardless of whatever the recommended specs are, the program is just danged memory intensive - and not always happy (robust) when it runs out. I'm still running Win98 on a 933mhz P3 system, so I'm stuck with a 512mb limit for the time-being... I can pretty much track my success or failures, depending on how many objects/textures are in the scene and what the rendering options are set to. The program seems pretty stable if I'm just rendering one character in a simple scene, but starts crashing badly (exceptions, etc.) when I get more ambitious. I don't think the program is particularly robust about memory usage at all. My latest render (firefly, production, with one character an apartment prop and a few others, including some reflection and refraction) created a 2 GIGABYTE swap file and took 4-5 hours to render my 800x800 image (it was the only app running at the time). So my suggestion? stuff as much memory in that new machine as you can - while we wait for future patches. Aside from that, the current patch seems to have fixed a majority of the problems I (and others) were having.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.