Really, what Poser itself needs is some kind of complete reorganization of their geometry data.  It's very hard to loop over vertex coordinates when you have to call them as X(), Y(), Z(), rather than being able to use indices.  And having to hand-calculate the vertex indices of each polygon, using the Start() and polygon length?  Feh.  I wish I had access to a compiler and had better programming skills.  I'd try to create something that would make all of this more accessible....

But I'm slightly OT....

Thank you for the information, ADP.  I was looking into Pyrex, with my initial idea of creating a .pyd.  Perhaps we've now come back full circle to the .pyd idea, with this thought of adding geometry built-in types?

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