Poser 5 already handles zipped files (e.g., pzz, crz, etc.) It helps keep the disk space from climbing too rapidly, but it doesn't help the organization problem. P.S. Maybe I'm a packrat, but I find that I can do some things more quickly (maybe better sometimes?) in P4 than in P5. Render differences, yes... but also P4 has a memory of which textures have already been used in a scene. P5 does not... so if the same texture image is used for several parts of a mesh, you have to manually enter the same information over and over and over.... Anyway... this means that I keep everything in its uncompressed form so that both P4 and P5 can read it. Which also means.... it's ALL under the "Runtime" directory where P4 resides. YECCCCHHHH 2) If/when I finally decide that P5 is really doing what it was supposed to do when released (stability being a critical element, and the most recent version -SR4 - is actually not bad)... I MAY give up P4. Then comes the real question of this topic string. Where to from here? a) Remember the textures already used and make it easier to remove an entry from the list. As I may have many textures called "wood" (in different directories)... how bout giving me a better way of id'ing which "wood" it is? Has anybody ever heard of image previewing? b) Allow me to group morphs dynamically rather than having to use a word processor to enter the grouping command. Then let me delete all the morph targets in any selected group. This alone, when applied to V3 and similar models with huge libraries of morph targets, will do wonders to minimize the disk space. Once I have defined the shape of a character's head and most of it's features, I will probably never change or modify those morphs again. (I can always re-inject them if I intend derivative characters, or even save them off-line somewhere before the morphs are removed). Yes, I know I can use morph manager and a Python script which lists all the morphs with zero values, but these are time consuming because they are done with general purpose programs. And just think about how much faster it will be to find the particular morph targets you want (i.e., expressions, phonemes, etc.) b) Poser should keep separate "most recently used" directories for render output, scene input, image textures, etc. Right now, it actually only keeps the information necessary to save the scene or the render. As I like to keep my textures in a type-catalogued structure separated from the run time programs, I end up clicking many mouse buttons to get from deep within a D drive to deep within the subdirectories of "Runtime" on the C drive. c) Make it easier to maintain the list of "Runtime" directory tree roots(e.g., to "remove" one) that exists only for archiveal reasons) d) This message is already too long.... sooo.... If anybody wants to continue on this subject, let me know at bmoritz@exis.net.

Forum: Poser - OFFICIAL

Subject: What I'd like to see in Poser 6