Splendid!

In fact I had been thinking abut a solution to that problem too, but couldn't really figure something easy out.
I was playing around with a "Ghost Figure" as donor, but in the end it was too clumsy and it also wouldn't allow a user to add his own custom morphs.

Your suggestion has the advantage of being simple and easy to implement.
This will definitely included in the next Service Release!

Thank you!

Probably it will become the @ symbol, for several good reasons.
See the conversation here:
https://forum.smithmicro.com/post/25649

I'll start work to include it in SR1 now (and should they agree on a different symbol it's still easy to change that)

K

Agreed; I'll implement it for SASHA's own morphs, and the Morphs++ only (because these are the morphs I use most, so it makes sense in order to test it.

K

First, let me say I'm sorry I didn't pursue this further yet.
I somehow hoped that people here https://forum.smithmicro.com/post/25649 would pursue it further and come to an agreement upon a standard.
Unfortunately it was not the case, and the matter went out of focus.

If your idea works as you say in P9 and P10 too, this would of course be a much superiour solution: Just select a "Copy Relevant Morphs" dial and you're done.

Issues that need to be examinated:

• Does it work with a zero "Copy Relevant Morphs" master dial (to comply with some Python scripts that reset *ALL* values to zero)
• or must the master dial have a value /= 0
• compatibility with P9 to P11
• compatibility with D3D's "Morphing Clothes" standalone program (this is mandatory because it delivers far better results than the on-board Poser function!)

Yes, I already did a brief test with it, and it looks like it's working.

However I want to check out all other eventualities though - Poser sometimes does strange things , and I want to make sure it works 100% before I add that feature to SR1.

K