LadyGodiva posted at 10:52AM Wed, 23 September 2015 - #4230306

Male_M3dia posted at 9:35AM Wed, 23 September 2015 - #4230267

If you using poser to create injection morphs for Genesis 2, you are doing it completely wrong and can't distribute content like that (as no store will take it). Poser does not support the DSON specification natively which is how you create content for Genesis. All content is saved in a .duf file and morphs are loaded dynamically in a .dsf file in a data directory when the figure is loaded. So if you're creating content for genesis, you have to learn DAZ Studio (especially if your morph changes the rigging, or is for a figure other than the base genesis figure like V6 as you need to strip out those morphs and save only your changes or you violate the EULA). Poser only reads the content you create their through the DSON importer. There are docs on DAZ's documentation center on how to create content, but it's generally use the morph loader pro to load your custom morph, then save a morph asset to save the morph into genesis' file structure... then create a shape preset and companion files... a less than 10 minute job, including adding any author information and location in genesis' body part that your morph affects for your content. Dimension3d also has a standalone tool that will load morphs, without loading DS, but you will still need to test whatever you create so you're back at learning DS... that's kind of why it was important to have poser read this stuff naively so people wouldn't have to open DS to make content, like V4.

I was aware that G3 content were all being distributed as DAZ studio files, but wasn't sure if G2 still supported poser style MOR injection or not.

So is it the case that "all" morph content for G2 characters are distributed as DAZ studio files, regardless if the end user is going to use them in Poser or not?

LadyGodiva

Yes, all content is distributed as DAZ studio format, which consists of the DSON specification. The Poser DSON importer reads that information via companion files: dummy poser files that contain python instructions that access the DSON files (.duf, dsf, etc). Every genesis generation uses the same format of dufs and are set up and distributed the same way. You would put the genesis files in one zip file and your poser companion files in a separate file so they don't have to be installed in the same place. Also in the poser companion files you can open up the .mc6 file that is generated and create your poser materials there (by copying in the information there). Don't delete the few lines as the top though as that's needed to tell the importer that it's a material file before it uses your material settings.