Bone information in custom layers for MHX and Rigify rigs not saved under "Save Pose Preset"

Issue #971 resolved
Arthur Dent created an issue

Diffenomorphic : 1.6.2.0969

Blender : 3.20

Daz : 4.20.0.17

MHX : 1.6.1.0043

When saving (via the “Save Pose Preset” button) duf pose presets for any G8M character with dickator geograft, imported using Easy Import, and with the rigs merged and converted to MHX (same applies for Rigify), all the translation, rotation and scale information for bones on the custom layer (shaft1-9,rectum etc) is not saved at all. However dickatator morph information is saved correctly.

On the other hand, saving duf pose presets for any G8M character with dicktator geografts but having a Daz rig results in all the relevant bone information being saved correctly.

Steps to reproduce

  1. Load up a basic genesis 8 male in Daz and add dicktator
  2. Export into blender using the easy import as follows

    1. Merge rigs, unselect create duplicate bones, non-confirming rig set to always
    2. Use favourite morphs and i have all dickator morphs saved in one json file
    3. Merge geographs with merge UV layers selected. Geometry nodes unselected
    4. Rig Type : Mhx or Rigify
  3. Tweak any one of the custom bones and then use “Save Pose Preset”

  4. Open up duf file in VSCode and search for shaft1

Repeat the above steps but this time select Rig type as Daz then open up the duf file and again search for any dictator bone.

I have attached a sample pose file saved from a G8M with a rigify rig illustrating the missing bone information but containing all the relevant morphs

Comments (5)

  1. Thomas Larsson repo owner

    Should work now. We don’t want to save all bones, because both mhx and rigify have a lot of mechanism bones that should never be touched. But all bones on the custom layers can be posed and are now saved.

  2. Arthur Dent reporter

    Thank you for this.

    Have you perchance pushed the relevant commit for this fix combined in another commit ?

    I ask because when i went to download / test the fix, I could not see your usual commit message “Fix for issue 971 “ etc briefly describing this issue 🙂

  3. Log in to comment