Quote - > Quote - Ok, I found the dropped verts problem...

What's the functional difference in these 2 cases (aside from one being for shape transfer and one being for morph transfer):

        if (abs(delta[0]) > FLT_EPSILON) and (abs(delta[1]) > FLT_EPSILON) and (abs(delta[2]) > FLT_EPSILON):
            parm.SetMorphTargetDelta(vi, delta[0], delta[1], delta[2])

...and...

        if abs(tmorph[0]) > FLT_EPSILON or abs(tmorph[1]) > FLT_EPSILON or abs(tmorph[2]) > FLT_EPSILON:
            parm.SetMorphTargetDelta(i, tmorph[0], tmorph[1], tmorph[2])

...hint: the first one drops verts from being included in the shape-transfer when they should be included .

Good eye!  Would I even have looked there?  Maybe after a few days.  :lol:

I really need more sleep.  :lol:  My tendency toward bumble-headed mistakes is worsened when I don't get enough.    Coffee alone does not solve this problem.

I had been using a simple "if delta" check, until the recent update, for the shape transfer.  I began to wonder if that might create problems without the .pyd.  The standards applied by Numeric for that test don't seem to be as rigorous as those used by the .pyd.

I'll fix it.  Many thanks!  :woot:

Hey.. just to be clear, the problem is using "and" instead of "or" in the above.

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.