That said, SM did fix the symmetry stuff I complained about, so a thumbs up to them for that.

Symmetry issues should not be so difficult to tackle and when of type 1a, 1b, 2a above easy to fix as long as the drift is of a lesser order of magnitude as the mesh size. Move vertices to the average mirrored position and done. This could be done even in Poser as a script tool. Issues of type 2b above could be signalled and added to a vertex group 'unpaired', and left for the use to fix.  A first step would be to make the search tolerance in Poser a quantity the user can define. Not sure if it is in not already in the settings files somewhere.

If it was that easy, don't you think that every 3D program out there would do that? Applying a correction morph does nothing to the original geometry, that is not how it works.

Meshes are stored in a KDTree, the original obj info in memory is never modified no matter how many morphs you apply to it. It is a look up chart for everything that follows.

Have you ever noticed that meshes like Antonia, Dawn, Star, V3, V4, Genesis, etc are symmetrical? I could list hundreds more that are.

Do you think that is a coincidence?

Or is it because they know that every step past that requires it in just about every application?

Trying to justify modifying a program to use non symmetrical meshes is nothing more than an excuse for not making it symmetrical in the first place.

---

Some things are easy to explain, other things are not........ <- Store ->   <-Freebies->