We looked at UAnimInstance before, have you gone senile !
Last time we looked at UAnimInstance was in the context of using it to access montage controls to give us finer control over our animation playback. This time we are going to move the Event Graph definition from a blue print driven anim instance and migrate all that functionality into our own C++ class.
Why bother rolling our own ? Blueprints are easy !
We can certainly use blueprints for all this work but having low level c++ access gives us a lot of control over our animation settings.
For example if you want to extend your animation system to support Inverse Kinematics, it becomes much simpler to compress that logic via convenient c++ method definitions rather than having to draw out a spaghetti bowl full of blue print nodes that make it hard to debug and troubleshoot.
Let’s take a look at some of the methods involved in this process.
As you can see from our code, there is really not much to it.
Outside of overriding the methods you want to take control of the rest comes down how much or how little animation data you want to expose to the blueprint.
The only real major point of complication is to ensure that the pawn attached to this animation instance is correctly cast before you get at it’s details.
With your own anim instance you can now start compartmentalizing your complicated logic, handle various player types against different blend space behaviors and generally modify your animation to suit your game.