Currently the idea for what rigged expression should be like is as follows:
User finalizes character with expressions
Expression shape keys + Rig is added
---> drivers are imported assigning rig values to shape keys.
End result is a fully rigged character with shape keys for various functions. So the rigging process becomes fully automatic for the user, including the face and body.
MB-Lab
Vitruvian
The current issues with this is that Charmorph's expression tab in finalization only supports packed L3 morphs (which doesn't seem to have a button or anything in character editing) and Charmorph only imports positive 0 to 1 shape keys when some shape keys might rely on negative values to invert the action. (ex. moving the mouth up and down.)
This can be solved by adding a morphs.json to L3 morphs and having them be imported during finalization. Instead of just 1 packed file allow loose L3 files to be imported as well with metadata to determine maximum values. Ex. -2 to 1 or -1 to 3.
Here is vitruvian as reference, there is a driver mismatch as I was working with an older version of the rigify face rig, but it shouldn't matter since the same idea applies here.
Vitruvian_2.zip
Hopefullyidontgetbanned
commented
5 months ago
Currently the idea for what rigged expression should be like is as follows:
User finalizes character with expressions
Expression shape keys + Rig is added ---> drivers are imported assigning rig values to shape keys.
End result is a fully rigged character with shape keys for various functions. So the rigging process becomes fully automatic for the user, including the face and body.
MB-Lab
Vitruvian
The current issues with this is that Charmorph's expression tab in finalization only supports packed L3 morphs (which doesn't seem to have a button or anything in character editing) and Charmorph only imports positive 0 to 1 shape keys when some shape keys might rely on negative values to invert the action. (ex. moving the mouth up and down.)
This can be solved by adding a morphs.json to L3 morphs and having them be imported during finalization. Instead of just 1 packed file allow loose L3 files to be imported as well with metadata to determine maximum values. Ex. -2 to 1 or -1 to 3.
Here is vitruvian as reference, there is a driver mismatch as I was working with an older version of the rigify face rig, but it shouldn't matter since the same idea applies here. Vitruvian_2.zip