This tutorial requires functionality that is only present in DAZ Studio 126.96.36.199 and newer. Refer to the DAZ Studio 4.x page for information relating to current version numbers.
DAZ 3D introduced a new method of rigging figures, known as TriAx Weight Mapping, in DAZ Studio 4.x. This method of rigging produces much more aesthetically pleasing results1) than the Parametric Joint Parameter system that has been in use and considered the norm for more than a decade.
While DAZ Studio has always had its own native formats2), significant effort has been made over the years to support the Poser format and its various file extensions. With DAZ Studio 4.x, this continues to be true. DAZ 3D has worked with Smith Micro to provide support for this new technology in Poser 9 and Poser Pro 2012. And while the experience of using a TriAx Weight Mapped figure in Poser is not quite at the same level that exists in DAZ Studio, DAZ 3D has updated its CR2 Exporter plugin3) to produce files that can be read by Poser.
It is important to note that the process of exporting a TriAx Weight Mapped figure, such as Genesis™4), for use in Poser 9 is in its infancy and still needs a bit of refinement. We realize the process, in its current form, is less than ideal and we aim to significantly improve/simplify it. But, we do not want to prevent users that are knowledgeable enough and/or brave enough to go through the steps from being able to use this exciting new content in the applications they choose.
Note: These steps assume you have already launched DAZ Studio 4.x, and that you have the TriAx based figure that you want to export already loaded into the scene.
Note: This step assumes that there is only one figure, the figure you want to export, in the scene.
Technical Issue: In Poser, using Edit > Restore > Figure will cause the figure to “explode.” It appears that the Cr2 Exporter is not scaling some joint values (OffsetA) properly. Using Figure > Zero Figure, then Edit > Memorize > Figure, then Edit > Restore > Figure appears to work around the issue. This has been fixed in a build after 188.8.131.52.
As stated earlier, this process is in its infancy and needs refinement, but you will get good results if you follow the instructions above.