A year or two of installing content in its default file structure has left my runtime rather complicated--not to mention the files I installed under Downloads before I realized how annoying it would be to move back and forth--so I'm planning to move everything into a more logical file structure. Is there anything I should beware of (like files that should not be moved, or things like that)? I want my content to be easier to use, not broken, so I thought I'd ask before I started mixing stuff around.

The advice has always been several external runtimes categorized and organized in a logical method.  Most content files should be kept together so that internal actual/relative path references be established without searching the entire folder.  The latest generation 4 DAZ models require installation into the actual Poser runtime, although many users have successfully managed to install and maintain these files in separate externals.  It is adviceable not to separate content from within their own established category folders, eg removing texture files from the Textures folder into a differently named folder.  That will break the internal pathway convention, which will force you to search for content when loading a model.

Okay, I see what you mean about texture folders. I would prefer to draw from one runtime only, but have that runtime organized in at least a semi-logical manner. I was thinking about keeping the texture and Geometries folders all the same, but moving the files in the library folders (pose, figure, prop, etc.). Will that cause problems?

I'm also thinking that I better not delete the default-position content until I try to load the moved content and see how it works. Hmm... guess I just have to move carefully. I'm very scared of breaking something.

Quote - The advice has always been several external runtimes categorized and organized in a logical method.  Most content files should be kept together so that internal actual/relative path references be established without searching the entire folder.  The latest generation 4 DAZ models require installation into the actual Poser runtime, although many users have successfully managed to install and maintain these files in separate externals.  It is adviceable not to separate content from within their own established category folders, eg removing texture files from the Textures folder into a differently named folder.  That will break the internal pathway convention, which will force you to search for content when loading a model.

Not so.  I - and several other users - advocate one Runtime, split with subfolders into logical categories.  This avoids many of the possible pitfalls of multiple Runtimes.

The long loading time is a bit of a red herring, too.  Any net gain from loading a smaller Runtime will be lost when you switch to another.

Sorry, Sam, I just reread my post and I shouldn't have said "...has always been..." .  Should have said "...in many instances...".  That's what I get for not proofreading my responses.

If you can, cohesively, organize one runtime for easier access of all content, then it might be to your benefit.  As Sam indicated, if the folder becomes too large, loading time could increase substantially and slow down your application.  However, I have seen a substantial improvement with the most recent Poser iterations.  And the new library format in P8 and PP 2010 is a big improvement whether you like it or not.  My philosophy has been to install your content, use it for whatever projects are on your list, then uninstall it.  The rule that has floated around for ages, if you haven't used it in 6 months, the likelihood that you are going to use it again anytime soon, is very low.  Maybe Cyberwoman should do is take a content inventory, determine the degree of importance for each, and delete the unnecessary.  Not only would the runtime folder weight lighten, there would be less content to organize, and a better opportunity to properly separate new content.

Heh.  I'm not going to fall out with you over it, buddy. :) 

Of course not!  Let's have some civility here.

Quote - Of course not!  Let's have some civility here.

In this forum?  :lol:

Glad to see you two worked everything out Most of my content is used on a pretty regular basis, so I don't think I would gain much from installing and deleting it per project. So you're saying that it is possible to move files around in my default runtime so that they're still in the same runtime, but grouped into logical folders? I think that's what would be best for me.

 I think no matter if you use one runtime or many external runtimes, unless you are very organized and have a good memory, that sometimes trying to find a certain file is like looking for a needle in a haystack!

Okay, so I did some experimenting tonight. My download folder is now empty, and everything is in a single runtime. At that point, it works.

However, I'm running into problems when I try to regroup library files. For instance, I have a figure folder named "JamesG2" under a folder named "G2". Instead, I want "JamesG2" to be under "Smith Micro Humans". If I just copy and paste "JamesG2" into "Smith Micro Humans", then James G2 will load just fine. However, if I delete the original "JamesG2" folder (the one under "G2"), then James's body parts and morphs come up in the parameters, but nothing shows up in my scene. What do I need to do to get my runtime files grouped like I want them to be?

If I may?  Leave the Geometries and texture folders be.  Most items in the libraries folders can be moved about BUT some of the newer e-frontier/Smith Micro content has the OBJECT file(s) located IN the library folders.  That is to say, the obj file may be in the same folder as the CR2 - actual character folder.  These items shouldn't be moved unless you want to edit the CR2 to point to the new destination folder.  I keep Poser 1-4 folders, Poser 5 folders, Poser 6 folders and DAZ folders with all of the various content in sub-folders below those folders.  The DAZ sub-folder is further  broken down into sub-folders containing clothes, etc for each of the figures.  Poser 6 also has Ben, James, etc. folders.

I keep a pretty structured Runtime and don't have ANY trouble finding anything.  Well, let's face it, we all have brain farts once in a while.  I do maintain a couple of runtimes containing stuff I don't normally use and even a couple of "project' Runtimes.  Whatever works for you.  It is handy to have everything you need and nothing else in certain runtimes.

Start looking into your cr2s and pp2s and you learn that not all providers are all that careful about path statements, especially freestuff providers (bless them all).  That DOES add to load times.  If path statements to textures are correct (or corrected) items will load faster from the Library palettte.

I think I could (and have) spent hours and days just organizing runtime content.  Maybe I'd spend LESS time just hunting and pecking for what I'm looking for.  Now where did I put that Row of 10 Books prop ...

PS: I never installed the G2s but DO notice that the original Poser 6 people have their object files located in the same folder as the CR2s.  JamesCasual.cr2 is pointing to the .obz file located in the same folder.

How are you moving content around?

Are you using Windows?  If so, are you moving the files using Explorer?

In the JamesCasual CR2 file I read "Runtimes:Libraries:Character:James:JamesCasual.obj" so that file DOES contain path statements that go counter to the original idea that object 'figure' files go in the Geometries folders.  The odd thing is that there is no Casual.obj file on my computer, but the compressed obz version.  And the figure loads fine anyway ... go figure.

Rance01, that's exactly what I wanted to know. Thanks a bunch!

It's looking like I'm going to be hacking some CR2 files... oh well. Wouldn't be the first time I've had to correct a messed-up file path.

It never made much sense to me that Poser can search through a runtime for a texture that has been moved, but is clueless about OBJ files if they are not in the exact location specified in the .CR2 or .PP2.  Even move it to a subfolder within the same original folder  and Poser has no idea where it is.

Perhaps one of those archaic practices that just never changed with the times... like vendors who continue to label_everything_like_this, as if they're working on an old DOS-based 286 that can't recognize blank spaces.

 I love my multiple external runtimes and wouldn't do it any other way.  A few of my runtimes are large, and those ones are slow to load. I find it is very much quicker to switch from one external runtime to another than have larger runtimes.  I'm poser pro 2010.  Scrolling down my list of runtimes with the BB built in library is blindingly fast ie no delay.
Having multiple runtimes is also quicker to install.  Just put the runtime into a folder such as V4BillyTaircrew and then drop it into your folder where you keep all your runtimes.  then when you load the figure, you click on pose and there are all your mats for those figures.
Love esther

Each to his her/his own.  I like one big runtime but do find it useful to have multiples too.  It's a great feature of Poser that the user has a choice.

Okay, so I opened up the CR2 file and changed the file path to the new folder, and it worked! Thanks again Rance01.

And imax24, I'm guilty of naming FoldersLike_This :blushing: I saw it so often in the names of content files that I assumed that Poser couldn't handle it.