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.