Quote - I read your first reply above a while ago and have/had been trying to think of a 'tactful' way of telling you that you were wrong :) (..and most likely fixating on some bad test-cases). ... So I'm pleased (and relieved) to hear that you went back and looked again and discovered the problem!

Anyway, don't focus too much on finding the trouble with the .pyd version of the script... when I was reviewin the previous thread earlier, right near the end you reported a problem where apparently the weighting is messed up in the .pyd.  It also looks like I never got around to looking into that, so I suspect that's where the problem is (you could take a look at your .vwt files - you might see all 0/1/0, 1/0/0, 0/0/1 weights, for example).

Ah, I'm used to being wrong, most of the time.  :lol:  That's part of what makes me hesitant making major changes to something that's working.  Part of the thrill of being me.  :meh:

I'm afraid it's looking like the correlate by index lists functions may be broken, too.  Hopefully not.  I'm testing it.  I wasn't using the .pyd for weighting.  I was using a pyd-converted version or your weighting code from the earliest TDMT.  I disused hitpoint.Weight when I discovered that bad data was being returned.  The straight CorrelateTo functions work.

I know there's a divide-by-zero crash bug in mesh.GetWorldNormals(), too, but that one can be faked out if you add dummy entries into any empty slots in the vpolys list before calling the function.

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