DeeceyArt posted at 5:13 PM Mon, 27 January 2025 - #4493250

What's weird is LF2 and LH2 share the same mesh and such and one works while the other doesn't. Did you apply the LH2 morph to LF2?

Applying my original morph to LF2 gives her the same issue.

odf posted at 6:57 PM Sat, 25 January 2025 - #4493207

Thanks for sharing that! I'd been working under the assumption that the recent Blender versions don't mess up the vertex order anymore. Better keep this possibility in mind then for the future and run my fix-up script whenever morphs behave weirdly upon loading. :-)

I've never had it mess up anything OTHER THAN LH2's obj. It's weird as all heck. We tried turning him upside down and never figured out what could cause an issue.

That ate up some WEEKS of his development too. Because I'd tweak his shape in Blender, then back to Poser, his collar rigging exploded. Then I fixed that, and realized that AFTER fixing that, all the morphs were broken, and back and forth until we decided to just open his obj in Blender, export without doing anything and BOOM! broken morphs.

Unfortunately, removing body from the name has the same results. I don't believe I have the license to share it on its own, but my obj file does contain proper collar groups. The best way I can think of to show it is by importing the morph obj as a prop into Poser and showing it off in the group editor.

Are the left and right collars in your morph named exactly the same as in L'Homme? That's the only reason I can think of why they wouldn't work.

Click the Properties tab, and make sure that the INTERNAL name of the collars are lCollar and rCollar.  Casing is important. They both start with a small letter and then followed by a capital C

Hmm, it looks like I found a solution! Splitting the collars by their vertex groups in blender and then exporting/loading each collar individually as a morph target. I was surprised that this needed a work-around, but it works just fine. I would still appreciate advice on this issue if anyone has any!