fix for scale propagation

Issue #1218 resolved
Alessandro Padovani created an issue

daz studio 4.15.0.30, blender 3.3.1, diffeomorphic 1.6.2.1248

The scale propagation for the genesis figures seems wrong, unless I miss something. That is, in daz studio when we scale a bone only that bone is scaled, while in blender the scale propagates to children. This also affects animation when bone scaling is used.

To fix this we have to set inherit scale = none in blender for each bone, this way we mimic daz studio.

Below an example with G9 where we scale the thigh in daz and blender.

Comments (7)

  1. Thomas Larsson repo owner

    Now inherit scale = None for all bones when the character is imported. Since I’m not sure that this is always the desired behaviour, I added a checkbox at the bottom of the Posing panel to toggle it back on for all bones.

  2. Thomas Larsson repo owner

    It’s the Make All Bones Posable tool that must keep the inherit scale property. Fixed now.

    Another fix was scale drivers (Tongue In-Out), which compensated for the difference between DS and Blender.

  3. Alessandro Padovani reporter

    Commit 3ada1be works fine thank you for the fast fix.

    @Maneki if you’re Surody on the daz forum yes I replied you there, thank you again for pointing this out. If there’s nothing to add I’ll mark as resolved.

  4. Alessandro Padovani reporter

    note for @Thomas. important.

    I just noticed that the pose properties are not keyframed, even if auto keying is on. This means they will not work for animation. Perhaps it would be better to keyframe the pose properties when the user sets them. Or warn the user that they don’t work for animation so they are intended only to be set at scene loading.

    Please note that all the scale and location and rotation properties/constraints can be keyframed.

    Let us know what you think.

  5. Alessandro Padovani reporter

    No reply so I guess the pose properties are intended for posing, not for animation. We can always keyframe by hand if needed.

    Marking as resolved since the main issue is fixed.

  6. Log in to comment