re: Hitpoint

First off, just to review and clarify, the Hitpoint generated by the original Closest Surface method was basically the intersection of the ray cast along the Normal of a vertex with the polygon/surface of the other mesh.

I went back to the other thread to refresh my memory and... we had decided to convert this into a 'delta' value when saving it to the .vwt file (this preserves the relationship of the vertex->hitpoint location, regardless of the current world-space position of the mesh).

Also note that the hitpoint itself - while used to determine the 3 correlating vertices and the weights to use for those - is NOT needed or used for Morph Transfers (the correlating vertices and weight info is all that's needed for Morph Transfer)... the hitpoint location IS used for things like Shape Transfer and/or No-Poke routines, etc.

In fact, you could describe the hitpoint as "the position to move the vertex to, in order to shape-match the other mesh".

So, given the above, does the new Closest Vertex method have a "hitpoint" - yes... it's the position to move the vertex to, in order to shape-match the other mesh.  In this case, it's (AFAIK) the average/center of the correlated vertices - that's being computed, but not (converted to a delta and) saved to the file - but there's no reason that it couldn't be... and if it was, then it would be "transparent" data as far as any shape-match or no-poke code was concerned.

...speaking of reasons not to... you have some concern about possible copyright issues, but for a lot of reasons, I have zero concern (relative to this) about that.  I just don't see that as a problem at all - there's nothing copyrightable about that info.

So, just to wrap up...

• the hitpoint info is not needed for morph-transfers, only for things like shape-transfer or no-poke type code.
• the Closest Vertex method has this same info, it's just not called a hitpoint
• the hitpoint info generated by the Closest Surface method is a more accurate location (for shape-transfers, etc) than the 'average vert position' one generated by the Closest Vert method.
• the Hybrid method discussed earlier could generate better hitpoint info for the majority of the mesh, using the 'average vert position' type for the rest of the mesh (where the ray-casting failed for whatever reason).
• In order to use this info (for shape-transfer or no-poke code and maybe other applications), it should be saved to the file (as a delta).

re: Restore Detail

Yeah, restore code is working great - and is much more appropriate than any of the other type of smoothing routines for this application.  Again, nice job on that.

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.