Hi @KK, you might be right about my browser cache.

I think Sasha's arms are the best of the four V4s I've recently tested.

In this pic note how the PoserPlace WM fixes the shoulder but elbow is not wonderful. Alfaseed WM is better (I think PoserPlace shoulder is better than AlfaseeD but in my opinion better to have both looking decent than one looking great and the other not good). All figures are using the fitness morph set to 1.

I think Sasha_2019 is the best V4 of all - especially now she supports so many morph packages.

and as if by magic the Sasha link worked for me this morning - maybe there is a limit per day or something. Anyhow, I'm stoked to read that there is support for more morph packs in Sasha 2019 - such as creature creator :)

I usually prefer the AlfaseeD weight mapped v4 over the poserplace one (bent elbows, for example, seem better to me). It's available at:

http://www.renderforever.com/index.html

Still getting file not found (but in french) for the latest Sasha - I really like the original release so hope to get SR1 soon.

Agreed, we need to know what Renderosity's plans for Poser are. If they need to Crowd Fund future development then I will be there voting and supporting with my wallet!

Am exporting to Unity. I love Poser but it’s always been flakey.

Thanks bsteagal, good to know it's not just me.

I tried DazStudio FBX export and yes it's much better, everything seems to work from DazStudio. The morph/blend-shape names from Poser are nicer than those from Daz but it's more important that they actually work!

Okay, I spoke too soon, now it seems every time I export an FBX all my morph categorisation gets screwed up and no morphs in the exported fbx file. grrr. I'm sure it's related though. There is no way Poser should be changing anything in the pz3 file just because I exported something as fbx though, surely? In fact, it doesn't' - it only changes what is currently in memory. If I reload/revert to saved then the categories of morphs are back. So it's "primarily" still a fail to export body morphs issue but likely due to inability to find files is my guess.

pikesPit posted at 1:13AM Mon, 12 February 2018 - #4304084

The chest dials shouldn't be all in the "Morph" group. Instead they should be in their separate groups like "Morphs++" etc. There's something going wrong during the loading of V4 / M4. When you load the base figure, there are "loadScript" lines in it which call a plethora of other .pz2 files which contain the groups, the morph channels, and the actual morph data. This can only be done during the loading process of the figure. If that process fails, you'll get the results as you have: You proceed to load the Base and Morphs++ and Poser will create the (hitherto non-existent) dials from scratch. Because there are no groups predefined, Poser puts them all into the "Morph" group. However, for some strange reason this won't work in the BODY actor: If Poser doesn't find the FBM channel it will load everything into the first other FBM channel it can find, or skip if there are no FBM channels present at all. And that's exactly what happens in your case. The reason why M4/V4 aren't initialized correctly are plenty; One probability is that the runtime was moved and the batch files point to a wrong location now. Your best bet would be to completely reinstall the figures, and then try again. Peter

I know this is an old thread but wanted to say thank-you as this sorted a problem for me too. I was having issues with morphs not exporting due to my not importing the whole set of morphs. Once I started afresh with a new scene and imported all the morphs of a set the full body morphs export :)

i.e. loading "Bodybuilder" by itself meant it would not export. But loading all of morphs++ fixed it.

It's being "sold" as a feature for game development and along with the other game development oriented features just doesn't seem to work (props exported lose all materials/textures for example). So I guess they repurposed it with the 2014 Game Dev edition and continued in that vein with Poser Pro 11 - albeit not very well. Very annoying to spend money on something for certain features only for those features to be useless for their intended purpose.