Forum: Vue


Subject: I think i found a reason for problematic Poser 7 empty imports into V6I

wabe opened this issue on Dec 29, 2006 · 74 posts


dburdick posted Sat, 30 December 2006 at 8:01 AM

After doing a little research on this issue, the fundamental problem is that when saving scene files (PZ3's) which use characters that have compressed obz (object files) and crz(chracter files), the runtime path in the scene file will only save the hardcoded runtime path inside of these files.  This is true of P6 and P7 characters when the geniuses at EF decided to distribute only compressed versions of their characters.  To make matters worse, they stuck the geometry files for these characters in the runtime:libraries:character path instead of the traditional runtime:Geometries path.

So if you installed Poser 7 onto the default standard path and have your runtime located on that standard path, you won't have any problems (except for some of the corrupted figures obz' such as James casual).  If you move your runtime to another location and change the runtime folder hierarchy, you must uncompress the crz and obz files using the uncompress Python utility program in Poser (you can find this from the Poser python menu) in order for the scene file to save the proper runtime paths.

The bug or problem that needs to be solved by EF is to save out the actual runtime path to the PZ3 when using compressed obz/crz files.  This bug is also there in P6 as well.  I'm surprised it hasn't come up until now.  Given the fact that so few Vue'ers render P6 and P7 characters versus DAZ characters, this may not be all that surprising.