Quote - Thing is: I have. It's for a large part the Morps++-morphs. That's why it need to be encoded somehow :)

Can you not just make ++ morphs a verbally stated prerequisite... same as many marketplace products etc?

The pose file would just set the values on the ++ morph channels, that the end-user already has installed to M4?

Your custom sculpt would just be added as a new morph, on top of that, then, on a separate channel?

What was your workflow to get the custom sculpt / what did you use for it? Is the problem that ++ morphs are frozen into your custom morph... like a mixdown into one channel?