Unknown "Easy Import Daz" Error in Daz Importer v4.1.0 in Blender 4.1.0 & 4.1.1 (for characters with Genesis 8.1 Hairs)

Issue #2137 invalid
88JRising created an issue

Here is the list of the items I imported:
Genesis 8.1 Mesh
Genesis 8.1 Eyelashes
HS HDLH Hair G8F (product link: https://www.daz3d.com/hs-haruko-dual-length-hair-for-genesis-9-8-and-81-females)
Ruo Xi 01 Lower (product link: https://www.daz3d.com/ruo-xi-collection-for-genesis-8-females)
Ruo Xi 01 Upper
Wet Dress Shoes (product link: https://www.daz3d.com/dforce-hd-wet-and-dry-classic-dress-for-genesis-8-females)

All items are supported in genesis 8.1 Female.

To recreate this error that makes the Blender exit or output a Red Error in Info:
1. Export the Character to Blender using the following items mentioned above.
2. Use Easy Import with the following settings:

3. Click Easy-Import then wait for it to output the Daztoblendererror.txt file I attached below. Sometimes it just crashed fully.
This bug is non-existent when I used v1.7.3 on Blender 4.0.2.

Python: Traceback (most recent call last):
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\error.py", line 223, in execute
self.run(context)
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\main.py", line 758, in run
self.easyImport(context)
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\main.py", line 767, in easyImport
bpy.ops.daz.import_daz_manually(
File "D:\Program Files\Blender\4.1.1\4.1\scripts\modules\bpy\ops.py", line 109, in call
ret = _op_call(self.idname_py(), kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: Error: Python: Traceback (most recent call last):
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\error.py", line 223, in execute
self.run(context)
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\main.py", line 287, in run
self.loadDazFile(filepath, context)
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\main.py", line 184, in loadDazFile
asset.postbuild()
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\cycles.py", line 130, in postbuild
self.tree.postbuild()
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\cycles.py", line 2137, in postbuild
marked = pruneNodeTree(self, active)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\tree.py", line 624, in pruneNodeTree
makeDazImages(tree)
File "C:\Users\Myself\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\import_daz\tree.py", line 770, in makeDazImages
tree.nodes.remove(node)
RuntimeError: Error: Unable to locate node 'Vector Math' in node tree
Location: D:\Program Files\Blender\4.1.1\4.1\scripts\modules\bpy\ops.py:109

Comments (7)

  1. 88JRising reporter

    I don’t encounter this error if:
    -importing only environment props
    -importing any genesis body mesh without clothes or eyebrows/eyelashes attached.

    Here’s a body mesh I just imported naked today:

  2. Alessandro Padovani

    This is just a comment to help, not related to the error. Usually you either use “face units” or “facs”, not both, because they are two alternative sets of morphs for facial posing. Also “feminine“ is not supported for G81 it’s for G9. Be aware that “body morphs“ will not work with ik rigs, unless you check “mhx compatible“. Also “transfer to hair“ is usually not needed since hair have their own morphs for posing.

    In general you may want to start with a easy import preset, in this case G81, which will set the standard features for you, then add or remove features eventually.

    p.s. When reporting bugs be sure to update to latest development version first, see #2129.

    p.p.s. The error seems related to daz images, if so it depends on the daz asset, please wait a reply by Thomas. You could also import the separate assets and see which one fails.

  3. Thomas Larsson repo owner

    I’m pretty sure that this bug was fixed a while ago, but after the stable 4.1.0 release. You can either update to the latest build, or disable the Prune Node Trees option in the global settings.

  4. 88JRising reporter

    @Thomas Larsson and @Alessandro Padovani thanks to the both of you for fixing the bugs and the right combination of checks in the Import settings. It appears that the bug is now fixed. :D
    Tried the experimental version, and it now works!

  5. Log in to comment