It is caused by the model being translated vertically either when exported out of Poser or whilst in the application that was used to create the morph.

Thanks for the quick answer. So if I understand you well, it must be inside the .obj file? What can be done about it?

If you can line the model up again in your modeling application you may stand a chance. However be aware that it needs to line up exactly. I would never trust positioning/scaling using a mouse, I always type the values in. Other than that you can try and import the morph in OBJ format with no boxes selected and try and line it up within Poser. Pan in verrrrrry verrrrry close and get the best fit at the neck you can. Then export the OBJ and use that as your morph target.

If you can indicate how you made the morph I may be able to think of another alternative. That is you may already have the correct data but are just not manipulating it correctly.

Check the Poser export sequence. There's an option to export "As Morph Target (No World Transformation" and you use that. (That's Poser 5, and if it won't select that option, switch Windows focus to another program and back.) Poser 4 may have a different label for the option. I believe it's mentioned in the morph-making tutorials, at least for Poser 4.

Thanks. I followed PhilC's idea (read it yesterday) and opened the full S3 obj and the headmorph obj in my 3D app. Indeed: he morph is for V3, and is located higher. When bringing it down to the exact height, and deleting S3's head to place it exactly point on point, I noticed that several points of the head and the body aren't exactly matched in pairs. This must at least cause a problem when texturing. I will now move all the headmorph points untill they are exactly on the S3 neck points, and then it should work: using a V3 headmorph on the S3 body. Must say I like this kind of thing more than posing. Thanks, I learned a lot.

When I first hit the problem, with a free version of Poser 3 given away with a computer magazine in the UK, I ended up taking the exported .obj file and importing it into a spreadsheet. I don't recall the details of what I did, there are various import options, but each line of the .obj was a spreadsheet row, and the various numeric values in each section, X, Y, and Z, were in a distinct column. Once I figured the offsets, which was a simple Y-displacement, I could recalculate the values, export as text, and it worked. Though I may have had to slip it through UVmapper, I don't recall. It was only after I did all the work that I discovered the export option. Incidentally, I've seen some morph targets which are just the vertex information -- no connecting lines. Looks odd in a 3D mesh editor, but that seems to be all Poser needs. If you go the spreadsheet route, you could remove a lot of the file. Come to think of it, you could probably extract the block of numeric data in the text editor, use something like AWK to apply the correction, and reassemble a minimal morph target file.