I sincerely hope you're wrong Scott and it is a bug! As I'll keep saying until people listen... ;-) Poser 5 is a 32 bit application. That means it has a maximum address space of 4GB. Two GB are reserved for the application, Windows services file buffers etc. The other 2GB are available for general memory allocation, ie. resources, meshes, textures etc. Now if people are (in trivial examples) having problems with memory configurations of about 1GB, at the outset, then they should bear in mind that they are probably already half way to P5's maximum resource capacity. It won't matter how much real memory or processing power, or what (32/64 bit OS) you throw at it. Five years from now, 32 bit P5 is still going to be limited to its 2/4GB memory capacity, even on a system with 100GHz+ processor, a 64 bit OS, and hundreds of gigs of real memory. And you're not going to be able to do any more on it than you can today. This is as good as its going to get, kids! So if one millenium dragon needs (for example) a gigabyte of memory to run, then 3 or 4 (uniquely textured) may be the maximum P5 can EVER support. Of course if someone can load 3 or 4 Millenium dragons in P5 without it crashing, then this problem IS a bug after all. P4 was (needlessly) dreadful in resource management. There is no reason why P5 should have been any worse (no dynamic hair or cloth in this example), and it would have been nice if it had been improved - the adoption of a Reyes type renderer should have reduced the resource requirements (at least for non-raytracing renders). But somehow, it just seemed to get worse :-( As I've said before - Built in Obselence. Bill Ps . lalverson - although Poser doesn't use hardware acceleration, its still a good idea to make sure that you have the latest video drivers, which are still needed even for non-accelerated display.