New timing tests.  It was a little slower this time.  (Why?  Transient conditions on my computer?  A matter of what else happens to be distracting the processor at the time?)

numverts:  4062
 numhits:  4062
8.50500011444 - .pyd CorrelateMeshVerts()
199.137999773 - Python whaddayacall Trumbore method (what's the name again?)

That's the raw result for time.time() - sTime.  So, let's see... divide by 60....

About 14 seconds for the CorrelateMeshVerts and 3.3 minutes for the Python method.  Is that right?  I always get mized up when I try to do base 6 conversions.  Hmm.

Now, the original old method, without even using the .pyd at all... took much longer.  I don't have code to test this.  I've added the octree handling into all my pre-.pyd code for shrinkwrapping....  It was slow.  Even with octree at 4 divisions, this test would take perhaps... four minutes?

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