The objects not coming in or not is unrelated to the pz3 being compressed.

Poser is truncating(cutting off the front) the path that is written in the Pz3 to find the .obj file.

For example:
Some items will be written
C:3druntimeswhateverruntimegeometrieswhateverwhatever.obj.

Vue can find those objects and imports them.

Some items will be written
runtimegeometrieswhateverwhatever.obj

Vue can't find those objects and does not import them.
Poser does not have a problem with either way it is written(not really a Poser problem).

You need to go into your offending pz3 and add the C:3druntimeswhatever...to the beginning of the line of code which calls your .obj.

What is weird is that Poser is only doing this with the .obj file code.  Not textures, for example.  It writes the whole path for those, without exception that I have seen.

I suppose that if the runtime directories were all stored under the Poser directory that there would be no problem.  That is probably why the problem is only being recognized by a few users, that is to say, those who have their runtimes OUTSIDE of their Poser directory.