Quote - I think it might be faster because there are more cases in which it might escape before doing any serious calculations?  When I looked at your version, it calculated several things up front, before it checked to see if we could escape.  Or am I wrong in thinking that?

Yes, that's basically what I said above :).

Quote - What you've done there is kind of what I've been working with in shrinkwrapping.  How would you try to accomodate the split between the legs?

I wouldn't. (as a user/operator of the plugin, I'd fix my input mesh to also have it split at that spot, if that's what I wanted).

Quote - Part of my trouble has been moving verts without hits into line with the others.

Options:

1. fix the code so there are no missed hits.
2. move them to the average of thier neighbor verts.
3. before moving any verts, determine the missed vert positions relative to thier neighbors, then move the hit verts, then move the misses into thier neighbor-relative positions (relative-position-weighted).
4. do nothing with them.

...both 2 & 3 have additional issues when neighbors are also 'misses'.

Quote - Another problem has been dealing with shrink cases in which the normals of the shrinking object don't handle so well for the purpose of the shrink.

Not much you can do programatically about that.  That requires the code to divine intention on the part of the user - something typically difficult to do :).

Quote - Mind you, this is veering OT for TDMT discussion, isn't it?

That hasn't stopped us before :).

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.