So if I understand the issue - (and there's a good chance I do not) - a 3D model is essentially a collection of data coordinates for specific vertex points in three dimensional space. So when Poser sends my figure to Zbrush, it is sending it a long series of vertex positions/coordinates (sort of like connect-the-dots) from which Zbrush then maps out and reassembles my model. I can then morph it (move the vertexes around) and send a new series of coordinates back to Poser for Poser to reassemble in the exact same fashion. The new coordinate locations now represent a morph target or new set of locations for the existing vertexes in my model. If the vertex count is not identical, Poser cannot create a morph target and will import the wrong-vertex data as an object file only.

Straight out of the Poser manual, page 810, it says that the order of the vertex coordinates must match or the of course Poser can't replicate the model form properly and so when we import a FBM from an external source in Poser, we have an option called ATTEMPT VERTEX ORDER CORRECTION in case our external source didn't quite arrange the points in the right order.

So is it possible, that Poser is not realigning the vertex information correctly when receiving it from Zbrush? As Caisson pointed out, there is a tiny bit of misalignment with the incoming data and it can and certainly does get worse with subsequent iterations on the same misalignment. So this is why one morph doesn't explode as badly as a second or third additional morph does. The more we morph the HD figure, the further out of alignment the polys/vertexes get. Zbrush doesn't misalign or get the vertexes out of order on it's own. Poser 10 can go and come without the slightest issue. A zero-subD figure can go and come without problems in Poser 11. Only with the HD applied in Poser 11 are we getting a problem. So then Poser 11 is simply not reading or aligning the points correctly when receiving the new coordinates from Zbrush. We know from Ironsoul's point that if the vertex and polygon counts were getting off then Poser couldn't form a morph target at all and would only import the data as an OBJECT file. So there's no changing vertex or polycount here at all. This is a simple arrangement issue. Poser sends Coordinates A out to Zbrush and when Z sends it back, Poser isn't aligning it properly. It's not the GoZ app, as it works fine with Poser 10 and with base resolution figures in Poser 11. So the issue comes with the HD option. Poser is not able to realign vertex data from its own HD alterations.

So this is the problem I think. Anyone agree or disagree? Any ideas on solutions here? Do we need a realignment option applied for GoZ bridge like we do with FBM import? Could this be all that's wrong?

Maybe I've over-simplified the problem, but sometimes breaking it down to stupid-simple makes finding a solution...simpler.