I've been dividing my 23GB runtime into smaller pieces to prepare for P6. My question is how small should your original runtime be before you notice a change in loading time. I've moved about 4GB into 3 new runtimes which leaves about 19GB left in the main runtime. So far I haven't noticed the program loading any faster...

I really don't know, because I never put any additional content into my main runtime, which has only the stuff that came with P5, except for the deltas for the milennium figure morphs. Poser still loads kind of slow for me.

I have not sub-divided my runtime at all...my runtime = 44.6G of data & it loads in 5 min. Just make sure you have all your folders up to the top level, before you exit Poser....another words...before I exit Poser ALL my libraries are to the top...in the display it only shows 2 folders.

I am going to keep my P6 runtime to the bare minimum when its installed and then remove the redundancies from the main P5 runtime and further subdivide. Until then I'm still sorting through stuff figuring out where I'm going to put everything. So far I made a runtime for Sixus1 figures, a runtime for some environments, and a runtime for Elle and other alternate figures. All of the unimesh clothing is going to be a pain to hunt up and differentiate. I think I'll let the DAZ human figures stay in the main runtime for now and concentrate on making a separate runtime for all the animals...

Yep, I'm also organising. Finally conceded that I need CR Pro, and what a great investment! Thanks Howard. What I don't understand is the comments (I've often read) like dlk30341's above (5 mins loading time). I'm using about 25 Gigs of runtime libraries here, and it only takes about 45 secs to load Poser 5 (including a default fully loaded V3 character). Sure enough, I can correlate my runtime size with a noticeable slowdown when Poser has to search for missing textures, but I've never experienced slow starting like some others seem to have. I've been wondering why I'm able to avoid such sluggish starting and two possibilities spring to mind. Firstly I keep just about nothing in Poser's own runtime library (deltas only) and I have all my runtimes in a completely separate partition. A related point is that Poser 5 has its own partition too, and very rarely if ever do I find it necessary to defrag this partition. Maybe the slow start can be alleviated by keeping the minimum in Poser's own runtime? Or maybe its attributable to fragmented files?

My guess..I'm hardware ignorant..is that it I have too many programs running in the background. IE...PC-CIllian/Stop-Zilla/printer/scanner/Yahoo etc That said, phases me none, I have time to get coffee/go to the restroom/empty dishwasher/smoke cig...so no biggy to me :)

Message edited on: 03/14/2005 20:05

caulbox, I completely agree and I've promised myself I would be better organized and more tiddy when it comes to the default runtime of P6. What happened was I just copied my runtime over from P4 when I upgraded last year and I never bothered to really sort through it because I thought the slow start-up was poser just being poser. Now, I'm still looking through stuff and trashing some free stuff I don't want and things that I bought but no longer want on my computer. I think it will move quicker when I'm able to compare the runtimes of P5 to P6 and know how to keep it to a bare minimum in the default runtime :)

Incidentally, before anything is concluded here, I now notice that martian manhunter also keeps the minimun in Poser's own library and still gets hampered with this slow starting problem. The possibility remains that the problem has roots elsewhere. What I omitted to add earlier is that I also keep nothing in Poser 5's 'Downloads' runtime library.

Neither do I. Is it safe to delete that folder?

Ok, I'm on a Mac so maybe its different. Used to have long load problems, crash problems etc. For the past three months I've had my main DAZ injection and cr2 stuff loaded in the main p5 runtime and "everything" else, over 20gigs, loaded in downloads in the same file structure as in the main runtime. P5 loads in 24 seconds. Opening up the other runtime takes about one minute. As long as I exit through the main runtime, in other words move out of the "downloads" content runtime, the app will not crash. Fast loads and stable...what more can I ask. Figures that once I get everything finally working right they come out with a new one...and yeah I bought it. -jay

It isn't possible to delete the "Downloads" runtime. Poser just creates another one if you try editing the LibraryPrefs.xml file.

Attached Link: http://forum.daz3d.com/viewtopic.php?t=9060&start=0

Caulbox, I didn't say I deleted the runtimes folder...I loaded everything inside. Open it up and look at the structure inside...look familiiar. -jay

I had a notable speed increase when I moved my runtimes out of the Poser folder. I had multiple runtimes, but they were all in the same place as the Downloads folder. Bad idea. Not only does that make the path names painfully long when you have to scroll to find or install something, it really slows Poser down. I moved them to another drive, and noticed an immediate jump in speed.

Well folks I may seem like an idiot howling in the wind here. I mean no disrespect to the others who have said this is a bad idea but the loading of all content, outside of main DAZ3 version stuff that has to be on the main drive, in the "downloads" folder was the best thing I've ever done with Poser 5 configuration. I DO NOT have mulitple runtimes loaded in Downloads. I have all the rest, 20+ gigs worth, of content loaded there in the configuration which already inhabits that folder. Things load faster than I've ever had in Poser, (24seconds for application and another minute for "downloads" folder,) and it has been rock solid for three months. The only quirk being exiting the program while in the main runtime. I've tried the mulitple runtime route and it was slower than can be tolerated. This configuration is simple and it works! At least on a MAC. -jay

Hmmm... I've moved just under 5GB out of the main runtime and then moved all my extra runtimes out of the Poser 5 folder. The start up time dropped from about 3-4 minutes to about 35 seconds :)