So... it sounds like maybe it might make sense for me to call the function with each step, rather than having another Very Large Array hanging around pointlessly in memory the whole time...?  I'll try it.  :D

I'm excited about the new changes and additions, but before I can test anything, I need to grasp when I should deal with the mesh.VertPositionsChanged() call.  In my case, I'm carrying around settable lists for vertex positions and vertex normals, and I've been passing those into the collision handling.  Do I need to use mesh.VertPositionsChanged() in addition to this, or can the new call somehow replace the need for my doing some of that (normals, perhaps)?  Or what?  Is it something I can ignore in this case?  There weren't any hints in the example scripts, so I'm just puzzled....

This is becoming a regular Swiss Army Knife!  Whoo!  A great deal of broad utility!  Fantastic!

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