Error when transferring vertex groups and shapekeys "DazDriversDisabled"

Issue #2114 resolved
Calibrator created an issue

Full error

Python: Traceback (most recent call last):
File "/home/calibrator/.config/blender/4.2/scripts/addons/Diffeomorphic-import_daz-b828270aca48/error.py", line 220, in execute
self.prequel(context)
File "/home/calibrator/.config/blender/4.2/scripts/addons/Diffeomorphic-import_daz-b828270aca48/error.py", line 238, in prequel
self.storeState(context)
File "/home/calibrator/.config/blender/4.2/scripts/addons/Diffeomorphic-import_daz-b828270aca48/transfer.py", line 46, in storeState
self.storeMesh(self.mesh)
File "/home/calibrator/.config/blender/4.2/scripts/addons/Diffeomorphic-import_daz-b828270aca48/error.py", line 299, in storeMesh
ob[key] = 0.0
~~^^^^^
TypeError: Cannot assign a 'float' value to the existing 'DazDriversDisabled' Int IDProperty

I was using 1.7.3 with blender 4.2, it’s been working fine so far. Suddenly I pressed the wrong “disable drivers” and now I can’t transfer vertex groups and shapekeys. I updated to 4.2.0 but didn’t help. I disabled and re enabled drivers a bunch of times, I even used the morph shapekeys, everything works fine except transferring.

Also I noticed that there’s 2 “disable drivers” options. 1 is when selecting the mesh and the other when selecting the rig. I dunno why there’s 2 but it looks like one of them broke my model. Here’s hoping you got a solution and I don’t have to re do a lot of work.

Comments (12)

  1. Thomas Larsson repo owner

    I only briefly tested Blender 4.2 last week, and didn’t run into this bug. However, I did encounter the same type of problem elsewhere. It should be fixed now, even if I didn’t try Blender 4.2.

  2. Calibrator reporter

    Does it fix already broken models tho? I tried the latest build from ~24 hours ago and that one didn’t fix the problem. I still couldn’t transfer stuff.

  3. Alessandro Padovani

    You should not use blender 4.2 in production since it’s not supported yet. To fix already broken models is not the purpose of the new commit. If there’s nothing to add we can close as resolved.

  4. Calibrator reporter

    Damn, I can now transfer vertex groups but the morphs menu under “Daz Setup” is still empty. It is what it is.

    I do have one more thing to add tho. Why are there 2 “disable drivers” buttons? And why is 1 of them appearing on the mesh when it does nothing? That should not be clickable when the mesh is selected.

    I am not sure what the difference is between “disable drivers” under Daz Setup and Runtime but one of them should go. I know I always use the one under Runtime cause the one under Setup sometimes has no effect.

  5. Thomas Larsson repo owner

    There are two Disable Drivers buttons in the Runtime tab, in the Morphs and Locks and Limits panels. They are the same. If drivers are disabled the rig is in a state where it isn’t possible to add new morphs, hence the Enable Morphs button in the Setup tab prevents that.

    However, the code only worked fine for armatures, as you noted. In the last commit it also works if a mesh is selected. It then acts on the parent armature.

  6. Calibrator reporter

    I’m not sure I understand this part

    hence the Enable Morphs button in the Setup tab prevents that.

    but it also probably doesn’t matter in my situation anyways. Since you solved the issue with disabling morphs when the mesh is selected I suppose case is closed.

    Also, if there’s any way to overwrite whatever the old version broke I’ll appreciate the help. I’ll try and look for one in the meanwhile until I get properly annoyed and quit, or until you have a solution.

  7. Calibrator reporter

    Oh yeah, I’ll also drop this screenshot if it may help you coming up with a potential solution if you wanna try.
    The morphs tab is empty when the character’s mesh is selected.

  8. Thomas Larsson repo owner

    I have now tested the latest commit with Blender 4.2.0 beta without any obvious problems.

  9. Calibrator reporter

    Ok I just updated to that one. Unfortunately it doesn’t fix my broken model but it is what it is I guess. Thanks, also you can probably close this.

  10. Log in to comment