mhx runtime issues

Issue #493 resolved
Alessandro Padovani created an issue

It would probably make more sense to place mhx together with rigify in the rigging category.

Comments (10)

  1. Alessandro Padovani reporter

    As for commit 6248aca and mhx 8da87e9, there’s also an error when I try to snap fk.

    steps:

    1. import G8F and merge rigs
    2. convert to MHX
    3. pose the ik hand
    4. snap fk to ik

    And it seems that the tweak bones are always generated even if I uncheck them in the convert panel.

  2. Alessandro Padovani reporter

    Then mhx is strictly related since it uses the daz importer to generate the rig, instead of a generic metarig. So may be you could use a single repository to distribute both mhx and the daz importer, instead of separate repositories for each project. Also to simplify bug reports where rig generation and rig usage may be related.

    Indeed you already use a single repository for the blender addon and the daz addon that technically are separate projects.

  3. Thomas Larsson repo owner

    The bugs should be fixed now. I forgot to test with old mhx rigs without Engeteduoiti’s alternative way to locate the pole targets.

    As for distributing both addons in a single repo, I need to think about that. Blender looks at the file __init __.py at the top level to make an entry in the list of addons, so one needs to make a superdirectory which contains both directories (or all three, including the bvh retargeter as well). But yes, it is doable.

  4. Alessandro Padovani reporter

    Commit 520172a + mhx 7932ccc work fine as for tweak bones and fk snapping.

    There’s a odd issue that when I snap, the hidden ojects in the scene are unhidden by the snap tool. That is, if I have a hidden cube, that has nothing to do with the figure, the snap tool unhides the cube.

    steps:

    1. hide the default cube in the viewport, and/or add other objects and hide them
    2. import G8
    3. convert to mhx
    4. pose and snap, the hidden objects are unhidden

  5. Alessandro Padovani reporter

    Tested with commit 2e226bd + mhx a29be6b and I can confirm the issue. Tried with various combination of mhx options and G3 G8 figures it always happens. I noticed that this only happens with objects inside the default collection. If the objects are outside the default collection then they work fine.

  6. Log in to comment