*"You know, come to think of it, I saw translation at some point too.. but I don;t recall what I did at the time to cause that (I think the flipping of the increase to -increase was happening at the wrong time when that happened)."

*Just as long as it isn't translating anything now.

Those are much better results with the head.  :woot:

If edges are now the problem, do you need that point line distance code?  I think we'll need something like that for edges once we get into the weighting. 

I'm going to see how much benefit can be had from extending the use of Numeric.  What else can I work in without confusing anything?  You seem to have the Master Plan.  :)

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