Any fixes to P5 are appreciated and I certainly don't want to diminish what's been done. It could be that CL has discovered that there were just too many issues to try and deal with them all. Fix some now and do the rest later. They are probably right about that. I guess if I had my druthers, I would have prefered to see them focus on some of the most basic and troublesome issues first....things that affect the basic operation of the program (like the memory issues and "cannot find texture x" issues). The memory thing is huge. It's very difficult to create high resolution images involving multiple characters. Even on a fairly competant computer I still get the "virtual memory" message when trying to render images with multiple characters, large textures, etc., even though I can render these types of images effortlessly in Vue. The only thing that saves me is that I use XP and it will make adjustments for the memory problem. The "file not found" is also huge. I echo what someone else said that you have to save constantly and before making any changes in the event Poser can't find some file that's referenced, ignores your command to "ignore" or "cancel", freaks out and locks up. The speed issue is helpful, especially the character loading....but only if it applies to all characters, textures, etc, regardless of room. The biggest speed problem is encountered when you have very large runtimes or are working across multiple runtimes. Hopefully some of the python fixes will resolve the lockup when using non-poser light sets? At present, I use the clear lights python utility and "start-over" each time I add a new light set, to avoid the "lock-up" problem I was experiencing. It would be nice if this were "built in" so that old lights were cleared automatically when a new set of lights was added. The adjustment for moved .obj files is a good fix, as is the background image fix in the material room. That one not only caused crashes, but wiped out an entire .pzz of mine once! I don't use the face room much at all, or the walk designer or any other animation features, so these will not affect much of what I do. But I suspect those who have been frustrated with these areas will be grateful. I share the concern about "caching system files". Sounds like "an accident waiting to happen", especially on the Win 9x OS's. Won't this make the memory issues worse? I'm not a computer whiz, but it would seem that if files are cached in anticipation of a subsequent loading of the program, you are retaining it in memory. I could be wrong. I plan to wait for those braver than me to install this fix and give some feedback on any "dominoe effects" that might occur.