Kupa: Poser always likes lots of RAM, especially with a few hi-res figures and a couple of 3000x3000 pixel texture maps.... (btw, each 3000x3000 pixel map eats up about 100 meg of RAM!) Oops, I read that as possibly bad news. The implication here may be (not definite) that P5 will still load textures into its application memory space. At that level of memory use, it will only be able to support about 20 or so unique (and less with 4Kx4K) textures before it starts getting close to the logical limit (for a 32 bit app and OS) of 2-3GB (virtual + physical RAM). Considering that some P4 characters already use several maps of this size, that might well limit the number of uniqely textured characters in a scene to a small number. Given that many P4 users have, in the years since its release, pushed the app far beyond its original design specifications, sooner or later P5 users are going to start trying these sorts of renders (probably sooner). Only speculation of course (apologies Steve for jumping on this), but this possibility did occur to me a few days ago, as I recently hit the same problem myself. In my case, I dumped the images into temporary files (eating up disk space instead) and relied on the W32 file buffers to aleviate the extra disk thrashing, without eating into the application memory. It actually wasn't that bad for rendering type scenarios. The cost is of course extra processing (rendering) time, but without pushing things to the limit, it didn't seem to be too great an overhead (ie.a small percentage). I can imagine that the first thing I might be doing with P5 is running it under the system monitor. That makes me a really sad individual doesn't it? Sorry guys, you've just got to accept that there always will be a few of us with half empty glasses ;-o Bill