Quote - It worked in P6 because P6 had a whole bunch of extra lines of code to try different combinations with and without "runtime" as the first folder in the tree.

This was discarded as of Poser 7. Had you upgraded earlier, you would have run into this already. It's not going to come back.

I think the issue was that if you don't have that single portable root, it's more trouble to install things. Given some product package, you'd have top level folders for Geometries, Textures, components under Libraries, and potentially a Python folder. With the anchored way, all packages begin with Runtime and can be merged with other packages easily.

Hiya BB... here we are cross-posting.

I understand what you're saying about installation of addons and products.  I've often objected to the directory structures imposed by merchants (adding tildes to raise their products to the top of my libraries and such, or adding subdirectories I don't want in my runtime tree).  So I've tended to manually install then move textures and geometries and such where I want them in MY structure so I can keep track of them, including purging them if I decide I don't like something.  This has always required manual relinking or use of CRPro.  I've also tended to use absolute referencing so it made no difference whether my runtime was named "P6 Runtime" or whatever.  But I imagine my situation and approach are different from most others, so I'm certainly willing to recognize the need to adapt my approach to conform to P8.  It just would have been nice to avoid the hassle, but so be it.

And as a side note, thanks for all you do to help people out and work to improve the Poser product line.

Regards...