mpfb2
mpfb2 copied to clipboard
makehumancommunity
MHX rig in mpfb
Is it possible to impliment makehuman rig (mhx)-the one which is created when importing from makehuman to blender in mpfb?. I ask the same question in make human community.
Depends on what exactly you mean by this. The thing is that MHX is connecting a whole lot of other things to the rig, such as drivers and deformation helpers.
It is possible that a very similar rig could be created in MPFB, but replicating all the other functionality related to it would be harder. One big part of this is that the MHX assets cannot be merged into MPFB, as they are license incompatible. Everything in MHX is GPL, whereas MPFB promises that all bundled assets are CC0.
So doing something similar to what MHX does could probably be acheived, but adding full MHX compatibility is unlikely to happen.
@ekswathi, could you elaborate on which aspect or feature of MHX you're missing? For my part, the only thing I miss in MHX is I find it clearer and more aesthetically pleasing than Rigify. However, I'm not yet sure if there's a feature of MHX that's truly missing. That being said, I think the default armature could also be refined to offer similar functionalities to MHX, if needed.
main reason i am interested in MHX rig is that it work well with the addon Retarget Bvh addon. thank you
For what I see, it seems to support Rigify https://bitbucket.org/Diffeomorphic/retarget_bvh/src/master/known_rigs/
I think @joepal1976's approach of improving MPFB-supplied rigs is very good, and I think there could be a double strategy. First, promoting MPFB rigs (default? other?) to be recognized and supported by addons such as Retarget BVH Secondly, implement a mechanism within MPFB to allow third-party rigs (like MHX, but also ARP, or even custom rigs) to be used (and to support assets such as clothes etc). This relates somehow to my feature request https://github.com/makehumancommunity/mpfb2/issues/151 concerning ARP armature support.
Such an approach could potentially alleviate licensing constraints by not directly integrating incompatible assets, but rather providing mechanisms to leverage different rigs according to project needs.