QUOTE LaurieA:

Asymmetry is a problem with Poser. I doubt the model was built asymmetrical, however I know from personal experience and other top vendors I've spoken to in the past, that Poser will randomly knock a model out of symmetry depending on how the model is saved into the library. It happens in very small increments and in various ways, and not all the time. It's been an on-going issue for many versions that makes content creation all the more frustrating, that S-M has yet to fix or even acknowledge.

I've seen this firsthand. Seen things that I KNOW where symmetrical were not once they were run thru Poser. AFAIK, its been a problem since at least Poser9/PP12.
END QUOTE

Laurie, Poser sometimes saves out a mesh obj. file when you save a figure to the library, even when there's no need to do so. But when you reload that figure, it will load the other .obj file instead of the original one, and I think that's how errors accumulate.
Poser has problems with saving very small numbers like 0.00001 and often "rounds" these: I think that's the source of the problem.

So check your .pz3 or .cr2 file for mesh reference, and change it back to the original mesh .obj file instead of what Poser created.

This is actually one annoying "feature" of Poser:
I could understand it if the grouping, or texture groups, were changed... But with an unchanged mesh I see no reason for such behaviour (except annoying us, creating errors like you described, and also eating up disk space for every new iteration of the same character, by saving a new mesh .obj file for every single iteration).

Peter