Hi there!
May be a real stupid Question... but since i work with Poser about 3 Years i never had that Problem.

I`ve collected a LOT of Content.... Now my Runtime is about 10 GB fat.
And even if the Pathes are all correct.... more and more Poser takes really to long, until it adds a Clothes, Hair or a Prop. The Harddrive makes sounds when Poser is looking for an item.... and i can go to the toilet.... till its loaded. :-(

Is that because everything is in ONE Runtime?

And... ive read about Users having more than ONE Runtime.... but i dont know how to create more than ONE Runtime!!!

Any Tips to get that Beast a little faster?

Thanx in advance.....

Factor

Yes, the bigger the runtime, the slower Poser runs. 

This tutorial tells you how to set up multiple runtimes, offers advice on organization, and explains what the advantages are:

http://forum.daz3d.com/viewtopic.php?t=9060

It was written for Poser 5, and but  applies to Poser 6 as well.  (And probably Poser 7, too.)

I have Poser 5 & 6 installed (waiting for my Poser 7 physical shipment) so I use nothing but external runtimes.  My Props runtime, right now, is over 40 gigs so externals are definitely the way to go.  If you're using Poser 6 the instructions for adding external runtimes is on pg 69 of the manual or someone will post them again here.

Since mine is 48.9 gigs, the flip answer is 'no'. Which version of Poser are you running? IF P4, then you will need a 3rd party app like P-Booost to do the multiple runtimes. P5 and above, you need to click on the file folder at the top of the library panel until you get to the top of the stack. It should have one folder with a red 'led' dot to indicate the runtime of the actual app is selected. All you need do then is click on the + sign at the bottom, which brings up the add runtime dialog, and find the folder (or folders, but you may want to start with one to begin with) you want to add. Select it and hit the ok button, and you should see a new folder with that runtimes name. Double click on that one, and the active dot should move to it. One little speed up trick if you are just starting out is to create and empty folder for the runtime you want, select it, then shut down and restart Poser. It should recreate the directory structure of a runtime for you (the geometry, libraries and those nested folders, texture folder, ect), so you should be able to unzip content straight to the initial folder, and things will go where they belong (always have a temp folder handy, though; there are still a lot of folks who zip a freebie from the Poser directory, not the runtime directory, so things get installed in the path Poser/runtime/ etc) Another speedup for starting Poser is to create a folder called null runtime and get into the habit of switching to that one whenever you shut down. Poser reads the entire selected runtime tree upon start up, and if there is nothing in the runtime to read, it goes on its merry way. -How- you break things up is going to be up to you. A few ideas to ponder; Remember you have to have the DAZ INJ-REM files in the actual runtime of the Poser app....but nothing says you can't keep them in your extra runtimes, as well. Get in the habit of keeping multiple copies, and you don't have to worry about reinstalling those: just copy them out of a remote runtime. It takes some surgery with notepad, or something like CR2 Edit or one of the other programs like it, but keeping the textures in =one= location will be more than worth the trouble, particularly if you render in other apps. My personal opinion is that you should separate out categories; make one runtime nothing but architecture. One for DAZ figures. One for the other figures. One for dynamic clothes and hair. If you have a lot of one style of clothing, create a runtime for them. But this is your runtime, so you need to arrange the resources to fit your workflow.

Quote - A few ideas to ponder; Remember you have to have the DAZ INJ-REM files in the actual runtime of the Poser app....but nothing says you can't keep them in your extra runtimes, as well.

Dale, in Poser 6 you dont have to have the DAZ deltas in the main Poser runtime.  The only thing is my main Poser runtimes is the native poser content.  All of my deltas are now in the appropriate external runtimes and it hasn't affected my load times at all when injecting them.

I will say, for those still using P5, put the deltas in the main Poser runtime.  It will decrease loading time greatly but this problem was corrected with P6.

BIG Thanx to ya ALL!
I thought i should do what you now are saying......

Anyway.... i am a little wiser now!
Cool to have such people here @ Renderosity who have experiences ... i feel not alone.

Thanx again.
Factor

*Dale, in Poser 6 you dont have to have the DAZ deltas in the main Poser runtime.

• That is not true for me and many others.  I've found P6 to be exactly like P5 with regard to the DAZ deltas. 

OTOH, some people never had to move the !DAZ folder even with P5.  It's really a very perplexing issue.

With correct pathes loading will take the same time no matter how big the runtime is (I have over 60 GB in a single one and it loads as fast as from an empty one). I'd suggest you do a checkdisk and defrag on the drive...

i'm at 9.8gb's...and i thought i was a pig!?
10, huh?
bad factor, bad factor, go lie down.

Well, I'm at 46 gigs (PPP version) and it takes about a minute for Poser to start up. Guess it's time to start clearing out the Runtime.

Quote - Well, I'm at 46 gigs (PPP version) and it takes about a minute for Poser to start up. Guess it's time to start clearing out the Runtime.

or just never close Poser - the easier solution ;-)

57GB and multiple runtimes is a BLESSING.....

60GB and one runtime just works as fine for me ;-)

My Poser content is at 154GB, and I'm currently re-organizing from a one-runtime to a multi-runtime setup.   `Three weeks at it so far and  at least that much to go.sigh
:b_overwhelmed:

Poser 7 changes the known solutions with the introductions of selectable deep searches. Up till now I did have all textures in one place, with P7 this might not be a great idea anymore.
We will all have to reconsider how to construct our different runtimes, of course the new collections add new possibilities.

I do hope CRPro will be modified soon to handle the new facilities of P7. Over the next couple of months I will have to rebuild all my runtimes to take advantage of the P7 capabilities.

May be you are on  an XP System and you are above 100.000 files on a drive. In this case, XP has to rebuild the MFT often as the Standard MFT is designed for app. 100.000 files. If you have more, you have to increase the space reserved for the MFT.

For this you have to add in the Regitry under
HKEY_LOCAL_MACHINE
System
CurrentControlSet
Control
FileSystem

the entry (as DWORD)

NtfsMftZoneReservation
 with a figure of :
2

This makes a reservation of 25% of the drive's space for the MFT and is good for about 200.000 files.

**All changes in your registry are don eon your own risk! So save before you make the changes!
**
I have no in my Posers 45.4 GB in 16.297 folders with 179,573 files means 44 Runtimes.

I started in August to build up Poser 6 from the scratch, I ended end of November. I looked into each freebie, is it worth to be installed or not and less then 50 % are now installed. I converted, where necessary the rsr's and deleted all rsr's, all ReadMe's and Promo pics. Checked the installed Files for correct pathes, believe me, it is a horror what in some files.

Now I have P7 and all I had to do was to direct P7 to my old Runtimes, done in less then 5 Minutes.

Quote - Poser 7 changes the known solutions with the introductions of selectable deep searches. Up till now I did have all textures in one place, with P7 this might not be a great idea anymore.

I don't see where that changes anything... > Quote - We will all have to reconsider how to construct our different runtimes, of course the new collections add new possibilities.

The only real change is content collections and those only slow down Poser's startup if used heavily. For example if you added all your runtimes into the content collections startup time would be at least as slow as if you had a single runtime with all those files ;-) > Quote - I do hope CRPro will be modified soon to handle the new facilities of P7. Over the next couple of months I will have to rebuild all my runtimes to take advantage of the P7 capabilities.

There are no new capabilities CR Pro needs to handle as it shouldn't need to handle anything. Content Collections just use regular file shortcuts to point to the library files you added to the collection. So Poser loads the original files from the correct runtime and if those are correct(ed) then all is fine...

You don't need any other content management utilties if you just use the solutions EF has given us properly.. multiple runtimes and the new content collections.

I swear, some people spend 3/4 of their poser use time managing thier content, and I use no management time or utilities at all without problems.

Micromanagement in businesses (or poser) is a bad thing, IMHO. ;)

Wait -- I was under the impression that a large runtime will take more time for Poser to start up, but once you're up there is no noticeable difference in anything you do except maybe locating and loading content. Is that not true? It's not clear from the replies in this thread. SS

I thought that the main problem with runtimes is that if they reside within the Poser application folder itself it will slow Poser significantly, at least in the preceding versions it did.  I have multiple large runtimes in an external folder and haven't noticed an application slow down, it just may take a little longer to navigate the folder tree.

I wish Poser were more like Daz Studio, it's library is alway very snappy no matter how big a runtime.

Quote - You don't need any other content management utilties if you just use the solutions EF has given us properly..

Sorry, I can't use those properly, because I lack the photographic memory needed for that. And I'm much happier and calm without Poser's library interface anyway ;-)

Quote - I thought that the main problem with runtimes is that if they reside within the Poser application folder itself it will slow Poser significantly, at least in the preceding versions it did.

Poser always (I wish that could just be disabled...) builds that right click dropdown for the library interface for the active runtime when it starts up or you switch to another runtime. Poser 7 also always builds the one for the Content Collections at startup. So the size of the runtime (and content collection) determins how long Poser will need to switch runtimes or to start up. If you switch or start up with an empty runtime it'll be fast, whereas it will be slow with a big one. (That's why using Poser with an empty runtime and loading content with PRPC and an external browser is my preferec method of accessing Poser content - fast startup times, no time wasted switching runtimes, ...). Poser 7 now seems to work worse with big runtimes, at least it's unable to build the righ click menu for my runtime - but wastes minutes on each startup to try it - same with the content collection I gave it for a try ;-)

Quote - > Quote - Poser 7 changes the known solutions with the introductions of selectable deep searches. Up till now I did have all textures in one place, with P7 this might not be a great idea anymore.

I don't see where that changes anything... > Quote - We will all have to reconsider how to construct our different runtimes, of course the new collections add new possibilities.

The only real change is content collections and those only slow down Poser's startup if used heavily. For example if you added all your runtimes into the content collections startup time would be at least as slow as if you had a single runtime with all those files ;-) > Quote - I do hope CRPro will be modified soon to handle the new facilities of P7. Over the next couple of months I will have to rebuild all my runtimes to take advantage of the P7 capabilities.

There are no new capabilities CR Pro needs to handle as it shouldn't need to handle anything. Content Collections just use regular file shortcuts to point to the library files you added to the collection. So Poser loads the original files from the correct runtime and if those are correct(ed) then all is fine...

With Poser 7 it is now possible to choose between a shallow search, standard search, or deep search. A shallow search is supposed to speed things up. As we all know Poser doesn't always include the path name in all file names, this means it expects the file to be in the logical place in the current runtime. With all previous versions of Poser the file was always searched in all logical places in all connected runtimes, with Poser 7 this is not always true anymore.
We will need to test the options for the best performance. Always put everything in the current runtime and use shallow searches, or always use full path names, or some other combination of the search option and file references. CRPro should give us these options in combination with the option chosen in Poser 7, it should also correct broken shortcuts if some content is moved to another folder.
While working on a scene textures (and other resources) tend to be in a single working folder, once complete the scene is archived (with all its resources) in a specific folder. This means that on my system things wander around as I see fit and I rely on CRPro to keep everything working properly.

Quote - With Poser 7 it is now possible to choose between a shallow search, standard search, or deep search.

Actually, it's none, shallow, deep. None tries to load the file from the first runtime folder it encounters when moving upward from the loaded file. Shallow checks all runtimes. Deep is really unneeded when using correct references. Do you really need to optimize loading times by the fraction of a second?

I'm not getting this shallow/deep search stuff?  What do you guys mean?  This is part of Poser's new library system?  What are you searching for?

I hesitate to use CR2Pro ever again.  I destroyed my entire runtime library with it last year without a backup.  It took me weeks to reinstall my content.  I let the software "automatically" fix my references--I didn't understand how to manually do this.  What I ended up with is having a ton of models missing their texture maps and could not find them.

Perhaps CR2Pro is a great is the hands of an expert, but for me it was just one big nightmare.

Under preferences you can now choose how Poser should look for stuff. None/shallow/deep. the last one ('deep') is what Poser did always in 4/5/6: If it didn't find a file in any of the locations it made up from the reference (and there are some quite funny ones it checks), it'll search all runtimes for a file with that name. If you switch to 'shallow', it won't do the search, if it doesn't find the file, but ask you to locate it. 'None' will only search within the first runtime folder above where your file has been.