Hmm.  This doesn't seem to be a problem with the poses, but it is a puzzle.  In the above examples, I use "storageOffset 0 0.3487 0" for the swap pose and "storageOffset 0 0 0" for the restore pose.  But when I check a resored cr2 in cr2Builder, I find that the objFileGeom reference is still using "storageOffset 0 0.3487 0".  This makes the restored parts inconsistent with the normal actor listings.  I haven't detected any errors as a result, but I, personally, would prefer to retain consistency.  So it looks like it may be best to use "storageOffset 0 0 0" for both the swap poses and the restore poses, just to be on the safe side.

Poser is a puzzle.  Does no one understand the difference represented by the variances in storageOffset values?  Kuroyume's cr2 file specs note that the reason for the difference is unknown.  Does anyone from eFrontier read these forums?  Stewer?  Anyone?

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.