Page MenuHome

Fix T78217: Improve horse metarig
AbandonedPublic

Authored by Demeter Dzadik (Mets) on Jun 29 2020, 7:43 PM.

Details

Summary

@J. O. (Papercut) suggested that the horse metarig would be more accurate/more usable if the setup for the fore limb would be copied over to the hind limb.

I also took the liberty to rename the limb bones from human skeleton names to femur, tibia, cannon, pastern & coffin (I really wanted to call it hoof but apparently coffin is more accurate?)

I don't know anything about horses, so I'll let @J. O. (Papercut) argue for this patch, see T78217#969156.

To test without needing to build blender, here's the metarig:

Diff Detail

Event Timeline

Demeter Dzadik (Mets) requested review of this revision.Jun 29 2020, 7:43 PM
Demeter Dzadik (Mets) created this revision.
J. O. (Papercut) added a comment.EditedJun 29 2020, 9:05 PM

Thank you very much for the revision, @Demeter Dzadik (Mets).
I asked my horse friends and experts and we all agreed on that it's more convenient to give these bones names that are broader terms. Someone I asked said "We aren't making any surgery here, so I think hoof would be best for using it.", which sums it up very well.

Here's a sketch of what we would like to name the bones. This is easy to understand for beginners and experts, so nobody will struggle with the renaming - yet it will be "more horse-y", as you stated earlier.


(* respective front and hinds/back)

Hoof*
Pastern*
Cannon*
Forearm
Arm? Chest? Ellbow? Humens?
Shoulder
Neck
Jaw
Head
Ear
Spine
Tail
Hip? (rather not "Pelvis")
Thigh
Gaskin
Cannon*
Pastern*
Hoof*

(Cannon with two n's.)

I went and tested the file again, to make sure it all works, which it does. Looks like a solid solution to me. Thanks for the time and effort that went into this.
If there is anything else you need to know, just let me know. I'm happy to help as far as my knowledge and available time goes.

Demeter Dzadik (Mets) abandoned this revision.EditedJul 3 2020, 11:51 AM

Marking as abandoned. This patch didn't tackle the issue without compromises, the proper way to address it would be by implementing a new rig type or implementing some parameter on an existing type for this case as proposed in T78463.