>> Now, this is all assuming that you are correct and that is what Poser is doing, since I haven't seen the source code I can't say for certain this is the case, however it seems like a logical guess as to why a large default runtime would so negatively impact Posers performance.

And here's proof.

Open Poser.

Hide it.

Add something to the runtime -- doesnt matter where: geometries, libraries, textures, I dont care. Just put it in.

Un-hide Poser.

Try using the drop-down menu to find the stuff you just put in.

You wont find it. And the reason you wont find it is because the stuff in the drop down is previously read runtime materials -- all of them. The only way you'll find the new stuff is by going up the library tree to the runtime listings, then work your way back down.

That's Poser re-reading the entire runtime, guys.

docandraider.com -- the collected cartoons of Doc and Raider