Intro to Limb Kinesiology, Fixing the Foot, Finishing the Leg
If nothing else, make sure you at least watch the video from 45m and on for an introduction to Kinesiology.
The rest is a fairly clean and straight forward bit of nodelling that brings the whole leg back together and gets us a fully guided component
Not a lot to add to the above.
We take stock of the work we had left behind, “fix” the foot, clean some odd spots, and call it a day with a fully functioning guidable leg by the 45th minute.
Since there was time to spare, and a good question in chat, I decided to ramble on for another 15 minutes about the kinesiology of limbs and how it relates to twist and joint behavior, which hopefully you will find interesting.
Like a few episodes ago I feel this episode, while still with a clear main theme of the Guide, needs an introduction.
I have, in the past, redone streams when I thought they weren’t up to par. In this case I decided not to (redo it), because I don’t feel it’s a “bad one”.
The first half is without hitches and we go about our business of analyzing where we stand, recapping, and setting things up.
Somewhere in the second half being indecisive about how to tackle the framing of the knee buffer, I chased my tail around a bit while looking at options, and on some fairly simple mistakes (largely involving the aim constraints).
The episode is still worth watching through, but it feels like I have been hand waving the graph cycle subject for too long so that the second part of the episode might be confusing to a good slice of the audience.
Lastly, at the very end, in the last few minutes before wrapping up, I explain something about containers (assets) in Maya, how they interact with the node editor, and why you might find that opening one of the scenes I share might show you a node editor with no connections despite the rig working fine.
So, with all that in mind I decided to do a special intro to explain how constrain cycles work, why they exist, what other cycles you might encounter and what their consequences are as well as how to solve them.
Part one of I’m not entirely sure how many episodes where we will finish the guide and set up for the leg component proper.
There isn’t anything specific about the episode I feel needs outlining. We have some work ahead of us to make the full rig configurable by guide and finished, and this is one of those sessions of honest work to get there.
I wouldn’t call it boring, I actually quite enjoyed streaming it and am looking forward to the next one or two we’ll need to finish this, but it’s one largely about keeping the graph in check while nodelling new parts on.
In this episode we do a pretty extensive refactoring (strict) of the leg and leg global components.
I’m not gonna lie, I’m actually quite happy with how it turned out.
Refactoring, in programming, is often done poorly and when people say “I have to refactor this for the future” they often mean “I’ll rewrite it according to my understanding of the problem space and destroy every interface in the process”.
We remained strict about it instead, moved a bunch of functionality across components and suppressed some unnecessary parts of the graph, both across and inside components, with the public interfaces left entirely unscathed.
The fact it was done methodically and entirely by just reasoning about the graph’s topology and our expectations is the part that I believe was successful. Worth a watch, even if I say so myself.
This is an atypical episode: for the most part we don’t modify anything in the rig.
In a way that’s not atypical in software development; some times you need to stop for a moment, take stock of what you did and why, and refactor some of the work before you can proceed to the next Milestone.
This is what happened in episode 17. I took a long hard (thoroughly commented) look at what I wanted to do next and what I had done insofar to plan my next steps.
It’s not a bad episode di per se’, I have re-done a couple of those in the past and would have re-done this had I thought it was useless, but it’s not an eventful or entertaining one.
There is one exception though contents wise which is a bit more exciting: Towards the very end someone asked a question about the Maya Profiler, a very useful but often overlooked and under explained feature.
If you don’t care for the slower paced episodes I still recommend you watch the video, but definitely pick it up from minute 53 when I start talking about the profiler. If you don’t mind the lack of climactic events and you have been following the stream sequentially then it’s not a bad one to have on your second monitor while drinking a beer.
Because of the peculiar nature of it, and the above note about the profiler, I felt I had to preface it with an intro video, but the intro video simply explains what you’ve read here. I’m embedding it for completeness but if you’re on this page and read it it will be unnecessary.