I'm wondering about support for animatable origins, in the script.  If the script is intended for use in creating weight map injection poses, I can see the utility of including animatable origin support for the transform dials: translate, scale, and (primarily) rotate.  It seems to me that animatable origin support for valueParm or targetGeom is really a separate matter, deserving of a separate script.  In that case, the morph or set of FBM morphs is really the point, with the origin adjustments dependent on those deformations.  The more I think about it, the less sense it makes to me to try to put that into the main weight map script.  I think that's more of a morph packaging concern and, as I say, it would make sense to me to treat it separately.

That is, unless someone knows of a really good reason to combine the two?  :unsure:  I suppose the effectiveness of a morph set could be reliant on weight mapping and animated origins.  But... it still seems to me that such a case would be more about the morphs and less about the primary concern of making weight map distribution accessible to a wide user base.  Hurm.

Any thoughts? 

===========================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.