Export As: [ PDF | ODT ]

How to setup an ExP product

  1. Create a blank Runtime structure to avoid having to hunt down 1000 files later to assemble for distribution. You will need:
    • “Runtime\Libraries\!DAZ\Michael 4” (or which ever figure this is for (for the exp files))
    • “Runtime\Libraries\Pose\YOURPRODUCT” (for the INJ files).
    • Now would be a good time to make a backup of your actual “Runtime\Libraries\!DAZ\Michael 4” folder.exp_1.jpg
  2. Open Studio and load your figure with morphs.
    • For ease of use, you should work with a CR2 that has your morphs saved in it. exp_2.jpg
    • If your morphs are in the community INJ channels, rename the internal channel names with the Property Editor, and remove the channels from any bones that shouldn't have them.
    • With the figure selected, open the ExP export tab. (make sure all the morphs are zero'd first).exp_3.jpg
    • Expand the figure's Node/Properties and scroll past the bones to the morphs.
    • Select your morphs from the list (ctrl+click to multi-select so you can do them all at once) right click and 'Select>All File Types>Same-Named Properties'. That will set all the file types (Group, Channels, ERC, Links) for any channel in the figure with the same name. exp_5.jpg
    • If you have morphs that do not have channels in the BODY (extra JCM's, ect), or are named differently in the bones, you will need to select them in their bones as well.
  3. Fill out your export options:
    • The “Product/Package Name” will determine the folder names for the exp file and the INJ poses.exp_6.jpg
    • The “Unique Product ID” determines the prefix for the exp files and must be unique, if some other exp set uses the same name, the two may overwrite each other. If you are going thru DAZ, a SKU can be provided to ou to use there. If you are not going thru DAZ, use a combination of the Vendor Name and Product Name, such as “MineUltra”
    • Point the “Output Folder” to the empty “Runtime\Libraries\!DAZ\Michael 4” folder created in step 1. That is where the exp files will go. Once you've pointed it at a folder, the “Base Delta Path” and “User Library Path” should fill themselves in.
    • The “Base Delta Path” should be “Runtime\Libraries\!DAZ\Michael 4\Deltas” which is correct. That's where the actual morph deltas will go.
    • Change the “User Library Path to “Runtime\Libraries\Pose\YOURPRODUCT”
    • Make sure all 4 of the boxes are checked. “Omit…”, “Generate…”, “Include…” and “Create..”
  4. Now Export
    • Your “Runtime\Libraries\!DAZ\Michael 4” folder should now contain a folder for each bodypart affected by your morphs and those folders have some files in them. The “Runtime\Libraries\Pose\YOURPRODUCT” should contain an ALL INJ and REM file and a subfolder with separate INJ/REM files for each separate morph.
    • The separate INJ/REM files in the Pose folder may need some editing and some of them may need removed. If you have a morph dependent on other another morph (extra JCM's type thing) they should both load from the same INJ for example. Or if you want 1 INJ to load all the breast morphs, ect. These are regular INJ/REM files and you can set them up however you want them.
    • To test everything, 'COPY 'your new Runtime to your Regular M4Runtime (which you backed up first) and run the DzCreateExPFiles-M4.bat.
  5. To add PowerLoader support:
    • Navigate to “DAZ Built-In Content>Scripts>Utilities” and run the “PowerLoader Developer”
    • Make sure Michael 4 is selected as the figure.
    • Find the row that shows “No Metadata Found” for your set.
    • Right click that row under “Delta Folder” and point it at your delta folder. It should fill in with all your morphs.exp_11d.jpg
    • Right click under Label and rename it.exp_11e.jpg
    • Right click the row again and select “Record Current Settings to File”
    • Browse to the location of the file it just created and COPY the new .dsx file to the same folder in your build Runtime.
    • Don't forget to give it a thumbnail.
  6. Make thumbnails for everything.
    • Zip it up and get it to your beta testers. Remind them to run the appropriate .bat file after installing.