Quote - Possibly silly question: is anything forcing you to use the same threshold in all areas of the mesh, or is it conceivable to make it depend on the mesh density in the neighborhood of the current point?

Not silly at all... it's what I had started playing around with, actually.  The current script will 'lock down' verts (stop moving them) as they get closer to where the script thinks they need to be (based on the threshold value).  It does this by filling in a matchlist[] array with a 1 for verts that should no longer be moved.

The large polygons don't really need tight threshold/tolerance values as the smaller ones... My current thinking is to determine an approximate "mesh density" value for each vertex, based on the shortest distance to a neighboring vertex. The script would then use this density value to 'lock down' the sparse areas earlier (higher threshold) in the process.  I had some success with some crude hard-coded values earlier, but hadn't yet come up with the best way to compute the right values to use, for any given mesh (in other words, values I was using for V1 or Antonia didn't work well on V4 and values I used for V4 didn't work well on V3).

The early testing code is in there (along with my related comments), it's just commented out right now.

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.