Hi, I have another question. Again, I'm almost a Poser novice. I have a question regarding "texture" folder. I'd like to know if there are any ways to keep the texture files outside of Poser in a systematic way. OK, my situation is that I set up Runtime folder outside of Poser and now I know that I don't need to keep all the texture files inside of Poser. Actually I keep some of my texture files in my external HD. But the problem is that whenever I try to open a file with the texture kept in my external HD, Poser keeps on asking me, "Where is this texture? Where is that texture?" It bloody bothers me a lot. Of course, if I keep the texture files in the texture folder inside of Poser, Poser doesn't ask me anything. But now my texture folder inside of Poser takes over 1GB of my main HD and I really need to clean it up. Are there any ways to solve this problem systematically? GUSTAV

If the texture locartions are hard-coded into the cr2s and/or props, then Poser will look in the indicated location (and ask you to locate them if it doesn't find them there). Otherwise it will look in the same runtime as the file you're trying to load (and ask you to locate it manually if it doesn't find the textures), so if you put all your textures on your external drive including ones for items not on that drive, it will require you to locate them. AFAIK, there is no option to set a "default" location to look for all textures.

First, what version of Poser do you use? Poser 4, ProPack, Poser 5, Poser 6? If you're using Poser 4/Poser Artist, or ProPack, there's not much you can do, everything should remain under the Poser Runtime folder. But if you use Poser 5 or 6, you can set up external runtimes. Search for "geep" in the Poser forum, he's got loads of tutorials, at least one of them addresses setting up external runtimes. The main advantage of external runtimes is that they can reside on another drive, they even can reside on the network (but that'll make things slow). Usually textures reside in :runtime:textures:[subfolder]. You can rename and move those subfolders, but it's advisable to keep them within the :runtime:textures folder structure. Poser will scan those folders for the texture you need, only if it can't find it (for instance, if it's outside the folder structure) it'll ask you where it is. Figure, pose and prop files contain pointers to the texture(s) they need. .cr2, .pp2, .pz2 files are all text files, you can open and edit them with a text editor. Usually a texture reference looks like this: "textureMap :runtime:textures:[folder name]:[texture name]" This is a so-called relative reference, it starts with :runtime, and Poser will look in every registered runtime to find it. Sometimes the texture reference is hardcoded: "textureMap C:Program FilesPoser 6RuntimeTextures[folder name][texture name]" A hardcoded reference requires the texture map to be in exactly that place. Not very handy. Only some freebies and very old commercial items have their texture references coded like this. One of the tools I often use to fix up references is CR2Builder by kim99 (free). Search for CorrectReference in freestuff here. A valuable tool (not as good as CorrectReferencePro by hogsoft, but very useful nonetheless) to fix up texture references. By the way, 1 GB is still quite small. My main runtime is 30 GB now, and I've got several smaller additional runtimes. There are users here that have runtimes over 100 GB. You might want to get an additional internal drive of at least 80 GB....

My Poser 6 Runtime is 1.97GB. I moved all of the Poser 6 Characters to their own individual Runtime. This make P6 open relatively fast. I have a total of 42 External P6 Runtimes, which includes my old P5 and P4 Runtimes. I expandunzip all new purchases into a Empty Folder, link to it with P6 and check it, if all is fine, then i move to the appropriate Runtime. If I run across a case where P6 is asking for a location, then I edit the Cr2, etc. Cheers DR

Hi, thanks everyone. I got it. BTW, I'm using Poser5. So this means, create "texture" folder inside my customized "Runtime" folder, right. OK, I'll try and see. Thanks! GUSTAV