Quote - The final "hit points" would end up being closest vertices averaged positions, but those could be generated with only the tri weights.  If all hits are generated this way, they should be compatible with one another.  The results won't match those of the pure raycasting, but look at the pure raycasting's limitations, in this test.

Actually, the hit points wouldn't be the same as those given by closest vertices.  The ray direction would be set using those points, but the hitpoints would be wherever the ray intersects a triangle.  Since we'd be using normals, the potential problems with mismatches or missed matches might still exist.  And the possibility of the "lumpy" or pseudo-lumpy problem noted above.  The approach should remove the oversampling error seen on the right in the image I posted, where the lips have been pulled apart and the tops of the ears are shrunken, because of too many influences being used.  It would also generate mostly tri-weights.

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