Keep DAZ rig throws error with MHX rig

Issue #1792 resolved
Poppedri created an issue

Using Bitbucket build.

DAZ Importer 1.7.2.1872

Blender 3.6.2

Python: Traceback (most recent call last):
  File "C:\Users\Personal\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\import_daz\error.py", line 223, in execute
    self.run(context)
  File "C:\Users\Personal\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\import_daz\mhx.py", line 614, in run
    self.convertMhx(context)
  File "C:\Users\Personal\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\import_daz\mhx.py", line 755, in convertMhx
    self.tieBones(nrig, rig)
  File "C:\Users\Personal\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\import_daz\fix.py", line 582, in tieBones
    self.tieBone(pb, gen, assoc, facebones, rig.DazRig)
  File "C:\Users\Personal\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\import_daz\mhx.py", line 1802, in tieBone
    rb.name.startswith(("hand0.", "foot."))):
AttributeError: 'NoneType' object has no attribute 'name'

Seems to work fine when converting to Rigify, but not MHX. And only when “Keep DAZ rig” is checked.

Comments (6)

  1. Alessandro Padovani

    1.7.2.1872, blender 3.6.4

    I don’t get any error here, tried various combinations with mhx and “keep daz rig”. You may want to give exact steps and if this is related to a specific figure.

    my steps:

    1. load G8F
    2. convert to mhx with “keep daz rig“

  2. Poppedri reporter

    Okay, I see my mistake. I was using models that were imported previously from 1.7.1 Daz importer. Re-importing them using 1.7.2 works as intended.

  3. Alessandro Padovani

    I don’t know if @Thomas Larsson wants to do something about this, if 1.7.2 is not supposed to be back compatible then we can close as invalid.

  4. Thomas Larsson repo owner

    The original daz rigs shouldn’t change between versions, since they are defined by DS. I converted a file from 2022 to mhx and didn’t encounter any problems. However, I see how the error arises and it should not happen anymore. Instead you should see lines starting with “Cannot tie” in the terminal window. It would be interesting to hear what those lines are.

  5. Log in to comment