I have been thinking of rearranging my Poser 5 libraries where I have one Runtime folder with all of my Geometry files and one Runtime folder with all of my Texture files. Then, I can create all the other Runtime folders where I can move the characters, props, etc. around and, as long as I delete the .rsr files first, they should still find the geometry and texture files they need to open. With all the Runtime folder installations and DAZ installations, I can't always figure out what geometry file I need to move with the character or prop unless I open the .CR2 in a text viewer. Does anyone think this would work? If not, why? THANK YOU!!!

SSSTTTOOOOPPP! DO NOT MOVE THE GEOMETRIES!!!! No, no, no, you don't want to do that! You would have to edit each and every CR2 and PP2 file to point to the new locations, or you would have files overwriting files with the same name. It is easy to open the CR2, copy the address of the geometry, and search runtime until windows finds it, and open the containing folder. Not to mention, if you need to know who created the mesh, for permissions or such, the folder name usually serves as a signature. The textures, I have always organised to my liking. Warning though, if P5 can't find it, it will lock up. Thus you are forced to have one giant geometry folder, and one giant texture folder if you want to avoid editing the CR2. But yes it may or may not work, but I would recomend against it.

Thanks for the advice. What about having one texture folder. I hate it when P5 locks up when it can't find the texture :(

Echo - don't mess with the geometry files. The Cr2's will find it where it's supposed to be and you rarely, if ever, need to know where it actually is. Textures are another beast. P5 gets really sick if it can't find the textures rapidly. About a third of the texture files you download do not have the optimum file location in the library file (CR2, PP2, Hr2, PZ2 (for mat files)). You need to run CorrectReference, a free utility found here, on your library and on each successive addition to your library ... or whenever you change the location of a text file. CorrectReference will quickly find the texture and rewrite the path to it for optimum performance of Poser3,4 or 5. Reorganizing your texture files is a choice between grouping by type object, by author, and/or by model. Or all of the above. Have fun. Just run CorrectReference. Reorganizing the library itself is much easier. You are restricted to keeping each library (character, expression, hair, etc) together. Some characters and a few props, however have placed the geometry file in the same library folder. There you either tinker with the cR2 or you leave that library and it's item alone.

OBTW: You will go seriously nuts if you have one giant text directory not broken up into useful easy to find again sub directories. Whatever you do, use CorrectReference to optimize the connection between the library and the text files. My P5 runs like a rabbit now that this has been done.

Bad advice is worst than none. I do not want anyone to just go putting all of the textures into one folder based upon anything I wrote. I have implemented my own system to organize the textures, but I do it as I need to. If I seem to be using Vicky often(which I do) I go through the folders and move vicky textures, BUT If any are used by another file, I edit the file right away. I see no need to hunt all over to find the transmap I need, so when I finally find it, I organize. I always leave prop textures alone, it's not worth the hassle for how often I use them. Just remember, by putting in one big folder, files may get overwritten.

pigfish I tinkered around with the thought of doing something similar to what you proposed but abandoned it with the idea that I'd be spending more time editing ?r2 files to repoint them to the proper places than rendering.

I'm in the process of rearranging my P5 folders. I have one Runtime specifically for Victoria 3, then use the Downloads folder to install all new items that I purchase or get for reviews/beta testing, and a Reorg folder where everything but the V3 stuff will end up. Before moving stuff, I ran CorrectReference to get rid of absolute pathnames. Under Figures, I have different sections, like Animals, Females, Males, Kids, Architecture, Jewelry, Hair, etc. Females is then broken up into Nadya, Natalia, Victoria, Posette, Eve, Judy, Millie, and Stephanie. Each of those folders is broken up into Characters, Accessories, Jewelry, and Clothing, etc. And then each of these are broken up depending on what character (Aiko or Stephanie? Bella or Poeme? Tops 'n Bottoms, Dresses, Bottoms, Fantasy, Historical, Shoes, etc.) Poses are broken out the same way, with each character having a folder for characters, poses, and textures, with more subfolders under each. Same with Props, Lights, Expressions, and Cameras. Okay, so maybe I went a bit overboard, but it works for me. So far, I haven't moved any of the geometries or textures and since I'm using relative pathnames, Poser 5 hasn't hollered. It finds them all.

Thanks everyone. Right now my files look about like jelisa's. I have a DAZ runtime, a Poser5 runtime, a V3 runtime, etc. I really wanted to reorganize by topic rather than vendor. I'm on way way to find CorrectReference.

I rearranged my libraries by topic and it worked all right for me. The only thing I regret is that Poser still cannot recognize a cr2 from a pp2 if it's not in the proper library. So I have to separate pieces of clothnig or armor between character and props files. This is soooooo annoying. If anyone has got a workaround this one, I'd be most grateful... Compiler

Gotta put library items in the right library ... no way around it. I have organized the major parts of my libraries and the texture file structure along similiar lines: I have Characters, props, and textures each with an Architecture group, a Michael Group, a Victoria group, War group, etc. That way when I am working with a Michael Character, all clothes, props, and textures can be readily found in each of the respective directories by a common name or logic. Architecture character? Many of Sams3d's building are characters ... so I group them along with 3dz world's stuff. I used to move texture files around a lot, but when I do so, it is essential to rerun CorrectReference against all the library items linked to those texture files. It's easier to do that when the same logic is used to group library items as texture files.