Whoo.  So I was right to use the clone() function when filling the points list in the complex example. I'm rather nervous, myself, about setting up funny reference loops and things, with all the RAM leak trouble I've had due to reference handling.  Cough.

I'm a bit puzzled about how to interpret the hit distance.  It gives direction and the values are useful, relative to one another, to check good distances against bad.  It works that way for screening out the multi-actor collisions by distance.  But yesterday I tried to plug the abs() values for the distances into some code which needed the true distance from the collision point, and the values in the hit distances were nothing at all like the PointDistance values I ended up using.  How does one, ah, disassemble the hit distances to separate the direction vector component from the actual distance?  Or can that be done, given that we have a scalar here and not a vector?  I assume there's some modification by the direction of motion (our raycasting normal for the vertex) here....  Not that I need to get the values from the hit distances.  I can do point distance if need be.  It would be better, I assume, to use the existing values, though, if they can be used this way.

Boy, I have so many ideas about how to implement these .pyd functions.  And so little math skill.  LOL

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