I have numerous runtimes and, thanks to Hogsoft's CR Pro, all my characters, MAT poses, Props and so on use path, as opposed to relative, references. This is great because it means Poser doesn't have to do any searching: it's always directed exactly to the .obj file, texture or Injection pose required, so things load very quickly.

However.

Poser Pro screws this up bigtime. Here's part of a PZ3 made in Poser 7:

prop Plant03_1:1
    {
    storageOffset 0 0.3487 0
    objFileGeom 0 0 x:poser currentruntimegeometriesDAZPropsEnvironmentPlant03.OBJ
    }
prop plants09_1:1
    {
    storageOffset 0 0.3487 0
    objFileGeom 0 0 x:poser currentruntimegeometriesDAZPropsEnvironmentplants09.OBJ

The same PZ3 was then opened in Poser Pro and resaved; the result:

prop Plant03_1:1
    {
    storageOffset 0 0.3487 0
    objFileGeom 0 0 :runtime:geometries:DAZProps:Environment:Plant03.OBJ
    }
prop plants09_1:1
    {
    storageOffset 0 0.3487 0
    objFileGeom 0 0 :runtime:geometries:DAZProps:Environment:plants09.OBJ

PoserPro writes a relative reference. When the file is subsequently opened by PoserPro (or indeed Poser 7), it can't find any of the OBJ or texture files (I have runtimes dedicated to storing textures and geometries only which are not added to Poser). This makes PoserPro completely unworkable for me, so I'm going to ask for my money back.

I know I can fix this by shoving all my runtimes into PoserPro and turning on deep searching, but this will slow everything down considerably.

If anyone is aware of q quick fix for this, please let me know!

---

Windows 10 x64 Pro - Intel Xeon E5450 @ 3.00GHz (x2)

PoserPro 11 - Units: Metres

Adobe CC 2017