I have been out of the scene for quite some time, and I'm not too familiar with the Gen2 and Gen3 characters, but I am in the process of getting up to speed.

My question is... are MOR files still the standard for distributing custom morphs into G2M and G2F for use in Poser?

If so, are the community channel names the same as in M4/G4?

In M4, I would create a MOR file using the channel names PBMCC_01, PBMCC_02, etc.

To link a full body morph, I would do the following... actor BODY:1 { channels { valueParm PBMCC_02 { name MitchelHead hidden 0 keys { static 0 k 0 1 } } } }

When I tried doing that today with G2M, a muscular full body morph appeared, which was not a part of my custom morph.

Could anybody point me in the right direction for setting up MOR files targeting G2M and G2F, or let me know if a newer method is prefered?

Thanks in advance! LadyGodiva

While I haven't tried, Genesis handles morphs very differently than previous figures.

Both Studio's cr2 export and the DSON Importer generate .pmd files, so I think you may need to create a binary morph injection...

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 natively so people wouldn't have to open DS to make content, like V4.

that's kind of why it was important to have poser read this stuff natively so people wouldn't have to open DS to make content, like V4.

Huh? I don't understand. Since when did I have to use DS to make content for V4? Since when did I have to use DS to make content for V anything? I've been doing it wrong since Millennium Woman Victoria. Genesis whatever may well need Studio or some extra cost tool from DAZ to generate morphs but saying that is necessary for older figures like V4 is misleading at best.

parkdalegardener posted at 7:48AM Wed, 23 September 2015 - #4230268

that's kind of why it was important to have poser read this stuff natively so people wouldn't have to open DS to make content, like V4.

Huh? I don't understand. Since when did I have to use DS to make content for V4? Since when did I have to use DS to make content for V anything? I've been doing it wrong since Millennium Woman Victoria. Genesis whatever may well need Studio or some extra cost tool from DAZ to generate morphs but saying that is necessary for older figures like V4 is misleading at best.

No, you didn't read it properly. I said it was important to have DSON read natively by Poser so that content can be created similarly like you would for V4. Since Poser doesn't write the formats needed, you have to use a different program to make it. V4 content can be created in Poser because it creates and reads the files needed.

As a side note, Victoria 4 was made in DS, not Poser as it uses the ExP technology to add in morphs/characters like morphs ++, A4, Stephanie 4, etc.

Victoria 4.0 didn't use ExP, which debuted with V4.1 and Studio 1.5.

However, MM is correct as far as creating morphs that can be used in both Studio and Poser. I think one could create a .pmd injection using D3D's Binary Morph Editor, but it would only work in Poser, as Studio can write .pmd files on export, but can't read them...

WandW posted at 10:11AM Wed, 23 September 2015 - #4230281

Victoria 4.0 didn't use ExP, which debuted with V4.1 and Studio 1.5.

However, MM is correct as far as creating morphs that can be used in both Studio and Poser. I think one could create a .pmd injection using D3D's Binary Morph Editor, but it would only work in Poser, as Studio can write .pmd files on export, but can't read them...

The morphs++ use EXP and V4 was made in DS so it's a moot point as far as 4.0 or 4.1. It uses ExP tech to handle morphs. The OP wanted to know the method for making Genesis 2 morphs for distribution, and using DS is the only way to do it without violating EULA as you have the tools available in the program to transfer only your work. If you are distributing content you made to others, you have to do it correctly or not at all.

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

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.

Even if you don't get along with the DAZ|Studio interface for regular use, creating a morph and saving it as DUF is quite easy to do, and will work much better than trying to do it from within Poser. Once you've saved it, you can just load Genesis in Poser, and your new morph is always there, ready to use. You're then free to forget about DAZ|Studio until the next time you need to create another morph (or create Poser companion files for a product that doesn't include them - this is even easier than creating morphs).