The source C++ code is extremely ambiguous on certain points, one of them being exactly what oneOverM represents.  I'm not exactly certain.  I only know that he receives the value from the GUI, where it seems to be preferred to have it clamped between 1.0 and 0.0.  Whether that represents mass or some pre-altered value related to mass, or something else altogether, I don't know.  I've retained his variable name with oneOverM, however, so presumably the name itself is some sort of indicator of what it is....

I was thinking about embedding your Mesh type in my container.  I'll try that, then!  :D  This seems like a bit of a serious paradigm shift, regarding the general approach we've had since the start, but I think I can see how it will be beneficial.  Among other things, I expect it to make calling up multiple actors easier.

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