There are a few thigs you can do without physically merging the assets, depending on your workflow.

If you use Smart Content, setting the Compatibility will create the proper dependencies. Right clickon the Materials folder, and select Edit Metadata. You can add another Compatibility to the one that exists.

If using Content Library, you can create Links to the original material presets and move them (yes, move them) where you want, like, to a Materials sub-folder for the converted G9 version. Select the Assets in the Materials folder, right-click on one of them and select "Create Links for Asset..."

You can do both, too, if you don't always use the same process.

I used the RSSY Clothing Converter and Hair Converter to convert my huge library of Genesis 8 assets into Genesis 9-compatible objects. My problem is that this process created new products for all of the converted items, so I now have to click the Genesis 9 Converted product to add the hair and then find the original Genesis 8 product to apply the materials.

Is there any way to combine the two products together in the metadata/database? I'm not seeing an obvious way, but maybe it's staring me right in the face.

Hey there, can someone tell me what I'm doing wrong here. I've gotten the method using Transfer Utility to work a couple times, but other times I'm getting a "geometry did not match" error when using Morph loader pro to bring in the G9 morph.

Some context:

-I understand things need to be in base resolution before exporting the morph

-What I'm trying to do here is transfer a lot of my G8 library over to G9, so I want to be able to eventually set this up to most efficiently do multiple iterations of this process one after the other

Here are the steps I'm using:

Step 0 - Already, I've created a Gen 8.1 fitted G9 OBJ file using the steps in WP Guru's Youtube video that was posted in this thread. (Load in a G9 and G8.1 base model, fit the G9 model to the G8.1, export the new G9 fitted model). This has successfully been used twice to create new G9 Shape morphs, so I believe I do not need to ever re-do this process again (correct me if I'm wrong).

Step 1 - Load in Gen 8.1 base model

Step 2 - Import the G8.1 fitted G9 OBJ file (Note: it comes in at base resolution)

Step 3 - Run Transfer Utility on the fitted model (remembering to uncheck "Parent to Source Figure" in the dialog)

Step 4 - Hide Gen 8.1 base model and select it

Step 5 - Apply morph from Parameters tab to model (this also changes the visible fitted model's shape)

Step 6 - Select the fitted model and export it as an OBJ (make sure Filter Objected is selected to be safe)

Step 7 - Delete fitted model from scene

Step 8 - Load in Gen 9 figure and select it

Step 9 - Use Morph Loader Pro to apply the exported OBJ shape morph to the Gen 9 figure (Remembering to set reverse deformations to Yes)

What am I missing here? Thanks!

Use easy import with the defult options, the armatures will be automatically merged this way and that's how the daz figures are supposed to work in blender, keeping separate armatures isn't any good. As for wiggle if the bones are driven with daz morphs then you can't move them in blender, again use easy import with default options to get all bones posable by default.

In general if you're new to blender/daz then use easy import to simplify the process for thngs you don't understand, that's what it's for.

https://bitbucket.org/Diffeomorphic/import_daz/wiki/Import/Easy Import DAZ

Or describe the exact steps to reproduce the issue if you believe there's a bug.

https://bitbucket.org/Diffeomorphic/import_daz/issues

Hi All,

Been working on some G9 shoes and am wondering how to future proof / make them work for multiple character shapes. I originally modeled them around the base G9 Feminine shape and have tested them with the 30+ different character shapes with mostly good results.

Process I'm using (correct way or not, no idea) for importing shoe obj for some background.

•  import shoe as .obj
•  convert prop to figure with triax weight mapping option selected
• fit shoe to G9 (makes mesh shrink wrap to foot and looks horrible to be expected)
• open morph loader pro, add new morph using the original shoe .obj with reverse transform enabled and set slider to 100% to get the original shoe shape back

The shoes autofit nicely to most character shapes, but characters with toe length adjustments tend to cause the shoe to distort / follow the contour of the toes too much. 

Process for the problematic character shapes:

• export out the wonky looking autofit shoe shape and custom character shape as individual obj's
• import both into blender, edit shoe in blender so it looks good on new character, export as "xyz shoe fix" obj
• zero out the original G9 reverse shoe morph from before
• load new "xyz shoe fix" obj as morph with same settings as above, set new morph to 100%, shoe looks good on new character

Is there a more efficient way to do it without making a dozen character specific fit fix morphs? Is is possible to make a "G9 default foot shape" morph that resets the characters feet to the base feminine shape without overriding the rest of the custom characters body shape? I'm waiting for someone to release some morphs for G9 like the Realfeet / Sweetfeet for G8 so I'll have to make a a slew of shoe morphs for those 

(also read about adding rigity maps to stop the shoes from deforming as much, that's beyond me at this point)

I know its hard to reply without screenshots, I'll work on adding some later on.

TLDR: The best process for loading in shoe .obj so it magically works on all G9 characters.

That's right... Since there's no metadata, you may only try to search 'by Files' with a key word from the product. Or you may manually install this 3rd-party product to Smart Content (cms), or with some product like Content Wizard.

diffeomorphic can correcty import daz cameras

See http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log_4_21_0_5#4_20_1_68 , in particular (I think)

• The “Update Base Geometry…” action (DzUpdateGeometryAction) can now be triggered from script with a settings Object (const QVariantMap& if calling from C++), via DzAction::triggerWithSettings(), to control its operation

  • If a RunSilent property is true the “Update Base Geometry” dialog is not displayed - the “Update Vertex Positions (from current shape)” option is the default choice

  • If an additional UpdateVertexPositions Boolean property is true, the “Update Vertex Positions (from current shape)” option is discretely chosen

    • If an additional Filename String property is not empty (provides the full path of a file to import), the “Update Vertex Positions (from file)” option is discretely chosen

  • If an additional UpdateFullGeometry Boolean property is true and an additional Filename String property is not empty (provides the full path of a file to import), the “Update Full Geometry (from file)” option is discretely chosen

  • An additional Importer Object property can be used to provide importer options

I want to create a displacement map for a workaround of creating HD morph. Here are my steps:

1. Sending the character to zbrush with GoZ
2. Subdivide the chararactor 5 times.
3. Creating morphs
4. Export displacement map with ZPlugin -> Multi Map Exporter
5. Import exported map into daz

The displacement map works, but seems like the entire torso was pushed outwards. I have no idea how to fix this, I alse tried method mentioned here but with no luck.

Does anyone successfully create a displacement map from zbrush? Please help.

crosswind said:

Converting high heels shoes is a bit cumbersome from G8 - G9 or vice versa. It's easy for the vendors to do so but not for us since we don't have the original project files...

But actually all heels could be 100% perfectly converted across generations as long as we know the tricks + knowing one modeling / sculpting software. Key steps as below:

0) Well use Clone to align 2 figures, try to make them have the same feet poses AMAP. Save G9's feet pose as a High Heels Pose Preset ( very important! );
1) Load high heels to G8, auto-fit high heels to G9 with G8's Clone
2) Export G8's high heels to obj file. Import it to G9's high heels with Morph Loader Pro to make a 'Base Fix' morph dial (import options: Reverse deformations + Delta only)
3) Reset G9's pose, apply G9's High Heels Pose Preset
4) Export G9 figure + G9's high heels to obj file. In Blender or Zbrush... tweak the high heels' shape by sculpting. Import back to Ds to update 'Base Fix' morph on the heels
5) Check all cbs (corrective morphs) in hidden properties of high heels by rotating G9's feet. Fix them if there's distortion, as well as bs (base shape) of the characters you use. Fix them as needed.

I ever converted some. Here's an example.

 Thank you, I'll give this a try.

Are you exporting/ importing in the right orientation?

What is the orientation in Plasticity?

Anyway you can change it by changing the import orientation in DS, or reexport from Plasticity with the relevant axis mirrored.

Converting high heels shoes is a bit cumbersome from G8 - G9 or vice versa. It's easy for the vendors to do so but not for us since we don't have the original project files...

But actually all heels could be 100% perfectly converted across generations as long as we know the tricks + knowing one modeling / sculpting software. Key steps as below:

0) Well use Clone to align 2 figures, try to make them have the same feet poses AMAP. Save G9's feet pose as a High Heels Pose Preset ( very important! );
1) Load high heels to G8, auto-fit high heels to G9 with G8's Clone
2) Export G8's high heels to obj file. Import it to G9's high heels with Morph Loader Pro to make a 'Base Fix' morph dial (import options: Reverse deformations + Delta only)
3) Reset G9's pose, zero Clone, apply G9's High Heels Pose Preset
4) Export G9 figure + G9's high heels to obj file. In Blender or Zbrush... tweak the high heels' shape by sculpting. Import back to Ds to update 'Base Fix' morph on the heels
5) Check all cbs (corrective morphs) in hidden properties of high heels by rotating G9's feet. Fix them if there's distortion, as well as bs (base shape) of the characters you use. Fix them as needed.

I ever converted some. Here's an example.

Two parts to this...

I've managed to figure out just about every hurdle I've come across with getting Daz chars working with Unity. The only thing still vexxing me - like 'very close to rage quitting gamedev' vexxing me.. it's now 10pm, been working on this nearly 15 hours and no closer to figuring anything out - is skin peeking through clothing during Unity animation.

I've tried Magica Cloth 1 and 2 to try to brute force cloth simulation / collisions. I've tried Unity's built in cloth simulation.. worked even less.

What is the right way to do this? Any and all suggestions are appreciated!

Part 2..

The only thing that seems to / should work is scaling my clothing a few percent larger than the character body. If there's an attribute slider? (not sure the correct term.. being able to adjust a specific property of a item) it works fine. But only if there's a coded attribute. When I go to export, any manual scaling via the scaling sliders doesn't happen. For example: I'll 150% scale something - obviously way too big, but I should see SOMETHING from this - but during the export process everything gets scaled right back down to 100%, then blown back up to 150% at the end. I've noticed it happens for a lot of things.. T / A poses getting reset especially. Why does Daz do this? In the past I've had to Bake Joint Rotations for exports to work properly, but then I'm screwed if I want to go back and work on the character in Daz.

Help?

James said:

Well, mmm 1% somehow is not correct for plasticity. It comes shorter than 179.95cm.
But I can just scale it to 179.95cm in plasticity.

If you are going from DS to Plasticity and back to DS try to avoid any scaling as that will potentially be baked into your mesh when you go back (assuming you use matching import/export settings in bot applications). Does Plasticity have an option to set world scale or the like? That will tell you what its base unit it and you can immediately get the scaling to use from that.

I must be missing something here, when I do the things you all have said to do, I still cannot get the HDRI to load into the scene, nor can I get any way to import one. I can make HDRI files in Bryce 7.1 Pro, which I think should be able to be used in DAZ Studio, but they won't import, and neither will any others I grab from online 3rd party sources. I have the one HDRI called FMEE GreenHills which loads from the Smart Content pane, no trouble. It has the 3Delight version and the Iray version. My PC cannot handle Iray, so I use the 3delight version. I know that HDRI's do work for 3Delight, as this one does. Is there a way to import them into the content library?

It depends on what you are trying to do with the FBX file
for example Mixamo FBX files are  very useful for animation retergeting to genesis 1 thru 9
after import into Daz studio.

Richard Haseltine said:

HamEinar said:

Major brainfart here as I updated GoZ - but since I'm running 4.21.1.48 it no longer works... Anyone have access to GoZ for beta 4.21.1.48 installer?! I do not want to install and run the latest beta!

Only Daz may give you the file. You could use the General reelase for GoZ purposes, or just export OBJ/import into ZBrush/Export from ZBrush/Import to DS.

How do I get in touch with "Daz" to get this - as I am paying $35 a month for ZBrush.

In the same scene, after gpu render failed. The iray preview failed as well, heres the log for the preview:

2023-10-26 11:32:37.008 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.
2023-10-26 11:32:37.008 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating motion transforms.
2023-10-26 11:32:37.008 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.
2023-10-26 11:32:37.158 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - TRIT:GEOMETRY ::   1.0   TRIT   geo  warn : Object DS_shape_219c_7141: the parametric approximation level is set to 4. The original value of 5 would produce too much geometry in a single mesh.
2023-10-26 11:32:39.154 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - TRIT:GEOMETRY ::   1.0   TRIT   geo  warn : Object DS_shape_252b_8948: the parametric approximation level is set to 2. The original value of 3 would produce too much geometry in a single mesh.
2023-10-26 11:32:41.334 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - TRIT:GEOMETRY ::   1.0   TRIT   geo  warn : Object DS_shape_25b2_9080: the parametric approximation level is set to 3. The original value of 4 would produce too much geometry in a single mesh.
2023-10-26 11:32:43.488 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Auto instancing compression ratio 1.00 (Full instancing compression ratio 1.00)
2023-10-26 11:32:43.488 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0
2023-10-26 11:32:44.566 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (1 triangle object with 38 M triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 38 M triangles, 0 fiber instances yielding 0 segments) took 1.078 s
2023-10-26 11:32:44.566 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating section objects.
2023-10-26 11:32:44.566 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.
2023-10-26 11:32:44.826 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 782 textures, 0 lambdas (0 unique)
2023-10-26 11:32:44.841 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Emitter geometry import (11 light sources with 99271 triangles, 1 instance) took 0.003 s
2023-10-26 11:32:44.841 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.
2023-10-26 11:32:44.841 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.
2023-10-26 11:32:45.672 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.
2023-10-26 11:32:45.672 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
2023-10-26 11:32:45.673 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
2023-10-26 11:32:45.673 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.
2023-10-26 11:32:45.673 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.
2023-10-26 11:32:45.673 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
2023-10-26 11:32:45.676 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
2023-10-26 11:32:45.676 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
2023-10-26 11:32:45.678 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using interactive scheduling, caustic sampler disabled
2023-10-26 11:32:45.678 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.
2023-10-26 11:32:45.678 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
2023-10-26 11:32:45.679 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
2023-10-26 11:32:45.679 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
2023-10-26 11:32:45.679 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
2023-10-26 11:32:45.679 [ERROR] Iray :: Internal rendering error.

Nope. I have tried importing FBX files many times and have never had an FBX file import correctly with bones. Your best bet is .OBJ and then rerig in DS.

I have been told, but cannot test, that Motion Builder FBX files will import correctly. Unfortunately FBX is not a terribly standardised standard.