This is perhaps also an animation question, but I can see that keyframes can be added to custom properties. In relation to the driver we make in this video, if I were to set a keyframe with the custom prop at 0.000 and then another at 1.000 at a further point in the timeline, I assume the bone would perform its function that has been set up with the driver when the animation is played? The only variable might be the time difference in which the keyframes are set apart?
At around 11:00 Wayne turns his driver graph into a spaghetti noodle - I did the same but set it up so when I scrub through the "My Prop" custom property the owner bone bounces back and forth a little as if it were rebounding. Idk, like a magnet zapping from one end to the other and then it bounces a little.
I'm just playing around per Wayne's instruction - but would something like this ever be used in animation? Maybe not my specific example of a magnet, but if an animation cycle was required where the cycle was always the same, could this be done using drivers and custom properties?
Maybe another example is an automatic sliding door needs to open. Except this one is a little stuttery and jammy, and it slides open this exact way everytime. Instead of animating the door stutter with multiple keyframes and then needing to copy/paste all of the keyframes everytime a character were to walk through it, could I use this method to automatically perform the scripted animation set up via the driver map?
This could be an unecessary method, I might learn of some better things when I get into the animation courses - but I wanted to ask nonetheless! And ignore this if it doesn't make sense. I find that a helpful way for me to learn these concepts and tools is to try and think of examples for where I'd use them!
Yes you could do that. Most animators would just use the action(the container that holds the keyframes) and place the action in the NLA(non-linear animation) editor for each time the door opens. Then again keyframing a custom property would be just as easy.
I really like your thinking here Harris.
As Dwayne said, yes you 'can' do that. However, it's not the most flexible or easiest way to do something like that. But I really like how you are trying to posit a different use for the information you are learning.
I haven't ever found a need to go 'full spaghetti' mode with the driver mapping.
However, there is sometimes a need to fire a driver off at the 50% mark with different interpolation types though.
Hope this makes sense.
This might be for something like a corrective shape key which needs to turn on and then off at a specific value.