Hi there!

 You may have seen morph products by myself and Meipe, the most recent being Curves+.

 We've had a few users who have had issues with morph conflicts (we used the CC and DC morph channels). We thought we'd be safe with the hip/thighs, as I didn't know many products which morphed that area... but yea, I was mistaken.

 So long story short, we're looking at .PMD as an alternative.

 Are there any bugs we should know about with .PMD morph injections? Our #1 priority is ease of use and avoiding frustration for the end user.

 ExP is not an option - we don't want the user to need to update their V4, as we have many products in this Curves+ series planned. The injects must be able to be loaded on custom V4 characters and not require the user have to start fresh.

 We realise that DAZ Studio users will not be able to use .PMD unless they have DAZ 3, and the InjectPMD script. We'll be providing a separate DC/CC inject for DAZ users. 

 So... full steam ahead with .PMD?

 Any replies would be much appreciated, thank you. :)

I have had no problems at all with them.  When I add morphs to clothes using Morphing Clothes, I often have it save the morph as a .pmd injection...

Reading the morphs from a PMD should be no problem. There are/were some problems with writing the PMD files in scenes where they got corrupted under certain circumstances. Most poser figures use PMD files for morphs and that has never been a problem.
Having external binaries off does not have an impact on the reading of the PMD, just writing them

So go ahead

Actually I much prefer exp to any of the alternatives. I actually convert them myself when I have to. Since I always start with a brand new v4, it has never been an issue

Lyrra

I never had a problem loading PMD files. There are certain issues when saving big scenes using PMD, but loading always worked for me without exception, and I've been using it since it got introduced.

However, you might want to clarify in the readme it is NOT required to turn on the "external morph targets" in the Poser options in order to load this files, Poser will load them just fine with it turned off, it just won't refer to it in the future, and will instead save all the information in the scene.

I agree with Hiroushi.  Never had a problem loading PMD files and I predominantly avoid using the External morph targets feature to offset any future issues.  It will make sense to post the notation in the readme file to clarify any misgivings the user may have using the product.

 Thanks guys! .PMD is the way to go then. :) We just wanted to be sure.

Sorry to intrude on this tech related discussion but I have some basic questions that I've been having difficulty finding concise answers to...

I'm interested in making some injection files of characters I've created or am creating.

I'm a mac user on a PPC PowerMac G5 running tiger.

I plan on purchasing INJection Pose Builder 1.5 which will run on my system.

I've created character morphs that combine custom ZBrush morphs with dialed morphs from V4 ++ and Aiko 4. The custom morphs from Zbush did not contain any of the dialed morph data when I created them. They were edited onto the default V4 model, loaded as morph targets, and then rounded out with the Daz morph dials. I still have the original morph target files.

I would like to create Daz Eula/licence compliant injection files for redistribution of these characters.

How can I go about doing this the proper way? I keep getting vague answers everywhere I look, and I've done quite a lot of looking.

Any help from experienced professionals in this regard would be greatly appreciated.

Thank you.

Oh yeah, I'm also using External Binary Morph targets which generate a .pmd and have the characters saved within (other than the character) empty Pz3 scene files.

i have noticed the inj bug when trying to apply the girl 4 expressions to v4 withgnd4 already loaded,and have to do the girl4 inj first.

@primorge i havent yet bothered to package up morphs into inj's or pmd's. i have only gone into manually editing them in the cr2 file