It looks like the angle limits are no longer in the TDMT code I've been using.  I was calling more than once, but to accomodate multiple octree passes.  The slowdown was at the end, when it was checking the outstanding 52 vertices against the entire mesh, using only one octree zone (in the shrinkwrap, not TDMT itself).

As usual, I haven't read the code carefully.  I'll study it and see how it needs to be implemented.

Edit:

Okay.  I see what you did.  The alternate code I've been using also does the back-facing test for the polys.  It does seem more straightforward.  But I don't understand the idea of running the function only once.  There were two reasons for doing multiple runs.  One was varying the angle, as noted.  The other was enlarging the bounding boxes, to catch possible cases in which no match was found due to the octree divisions cutting the correct match tri out of the point's octree zone.  My tested multiple runs were for that purpose, and each run did find something.  The final "catch-all" phase was very slow about it, however.

So how do you suggest the new code be implemented in TDMT, given the octree handling?

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