Quote - I think rather than manually deleting them, you dial them to zero and then export out again ... yes?

In other words, let's say you are creating some face morphs. Export the head out to ZBrush with GoZ ... make a "Nose Puffy" morph ... export that back into Poser. Dial that morph to test it in Poser. OK, so far so good.  Set the dial back to Zero.

Go back into ZBrush. Zero out the morph you previously made so that all traces of "Nose Puffy" is gone.  Now make a "Cheeks Puffy" morph in ZBrush.  GoZ that one back into Poser.  Dial it in to test it, then dial it back to Zero in Poser.

Now you have two morphs, each working independently of each other in Poser. The Nose Puffy morph, and the Cheeks Puffy morph.

Would this be a solution for what you're doing?  I can see that the only gocha that it might have is if you have more than 64 undo's to undo in Zbrush (heh, I don't even know if that setting is adjustable).  But when working on one piece at a time and sending them back into Poser ... to combine them in Poser ... then it works quite well.

 

Tha'ts how it SHOULD work, but that's not how it actually works, as far as I can tell. 

So going with your example, the first 'nose puffy' morph in poser is still required to be set at 1, for any additional morphing you make to it. 

If you set it to 0, and goZ back to ZB, your model will be zero'd out in zb, so you have to start all over. Not intuitive at all.

This is because zb updates your model with the most recent changes, so it's going to see the zero-morph pose as the most recent version. Clearing the GoZ cache destroys the link between your poser model and your zb model, so trying to go back to Poser, poser doesn't recognize that it's a morph of the same model anymore and instead only gives you the option to import as a prop. Very frustrating. 

I will have to experiment with it more to see where the actual problem is or if its just an issue with my workflow.

 

*Edit - Sorry, correction. I was mis-reading what you said. 

That scenario does work. 

The issue comes when you're doing things like expression morphs, or JCMs.

 

~Shane