my communication with smith micro so far:-

 
 

 
Dear Riesa,
The reason we chose to make all paths relative was to facilitate moving the main Runtime out of the Poser folder. Poser Pro can locate files regardless of their location (although it may take a bit longer in some cases) but this does admittedly create issues with applications like Vue that use an older version of the Poser SDK which can't properly locate all required source files without absolute paths. This is unfortunate but we're working with e-on to provide an updated SDK wich should allow them to create a Vue update which better handles files created in Pro.

Just to be absolutely clear, there's no way to force Poser Pro to write absolute paths in PZ3s, nor do we intend to allow this; for the moment Vue users will need to continue creating PZ3 files in Poser 7 to ensure compatibility. I very much apologize for the inconvenience but this should be a temporary situation. 

Regards, Colin Gerbode
Technical Support

The thing is though that in the previous versions of poser the path was relative for the main runtime which can easily be merged with the new poser.  All one has to do is first merge the new runtime into the old runtime so no old things will overwrite the new things, then copy that runtime back into the new version of poser.

Not only do the relative paths slow everything for people with multiple runtimes, but when object files or texture files have the same name, poser is going to make mistakes.  I am very sad that you are not allowing the absolute paths.   

MY ONLINE COMIC IS NOW LIVE

I aim to update it about once a month.  Oh, and it's free!