Scott - That's not Poser's fault Oh yes it is, and its a big fault as well. The resource management in P4 was dreadful, all the textures get loaded into memory. For a 32 bit application there's an upper limit (in Win32 and probably linux and MacOS as well) of 2GB usable by the program - this is an upper limit to memory both RAM and virtual. For most programs this is not a problem, but by its nature Poser requires a lot of texture mapping and those textures, when uncompressed can add up to a lot of memory use. Bear in mind that people who felt they needed 512 MB to run P4 well were already pushing the 25% mark and those who felt they needed a gigabyte were sailing close to the 50% maximum. I don't yet have P5 (still waiting here in the UK), but all the indications are that the memory use is even higher. If this is the case, I expect that within a year or so people are going to be pushing the 2Gig mark and P5 will crash and burn, regardless of their installed RAM or OS. It's a built in obselesence and one that a few people are probably already close to hitting. In this respect, I initially had great expectations of Firefly, based as it is (allegedly) on the Reyes rendering algorithm. If this had been implemented properly, it would not require more than a single material (and associated textures) in memory at one time, and load each material only once - which is a fundemental part of it design philosphy and one of the feature that makes it very a very fast and resource friendly render solution. As it stands, going by some of the reports, Firefly is slow resource hog, and it looks like CL fumbled the ball on this one. Still Waiting... Bill