Do you have any thoughts on using a series of Vertex and Polygon class instances for Geom data organization, rather than comprehensive lists covering the entire actor geometry?  I plan to test this soon.  My thought is that it might make mapping verts and polys between actors (virtually merging geometries) easier, as well as mapping between normal polys and triangulated polys.  But what I don't know is whether it would actually be worse for memory usage or slower (or more involved) in terms of loop structure.  As far as I can tell, however, that would be moving toward ADP's idea of a more object-oriented structure.  (Or would it?)

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