I got bored today and thought since not everyone has NodeCanvas that I would put together a small example of how Mecanim can be used as an FSM tool to control Skeleton Animation (NOT Animator) by using State Machine Behaviors. I usually prefer programming everything out, so getting this working on a very basic example so easily was surprising.

Here's the video and attached project. Keep in mind this is stripped down very bare and doesn't make use of public variables which make it easy to expose drop down selectors of spine animations. That would require a bit more work, but it "appears" easily doable and with the free built in tool.

In case people aren't familiar with Mecanim, it's basically a system you feed inputs to and then create transitions from based on the current state of those variables. If you change your movement speed to .5 and are in Idle currently and Idle defines a transition to Run with movementSpeed >= 1, it simply moves to that new state.

The code on the right at the end shows the behavior I place on every state in the FSM.

I'm horrible at explaining anything, true coder with no capacity to communicate so if you have questions or just want to know what's going on feel free to reply.

Correct this is the SkeletonAnimation, NOT Animator which creates unity animation clips.

I'm already using nodecanvas to do this so haven't pushed testing further, but I imagine the only limit is how well you can code and how good you are with mecanim if you need to add layers etc. I don't see any limitations, it's a visual FSM.. if anything hard coding it out is more limiting.

You saying any script you ever have a compile error on you lose all your serialized data on even your own custom classes? That's not normal behavior if so.

Hey Affinity, this post was for those that do not have NodeCanvas. You do not combine Node and Mecanim.

If you use this example, you would still instantiate your animations as SpineAnimation not Animator. This one allows you to place a behavior on each mecanim node.

Did you just mean to reply to Spine + NodeCanvas? by chance?

Sorry looks like I put some transitions in game that simply don't have animations to go to, so it gets super pissed off about that

So to break this down a bit more.. if you were to call any of this from code, you would be setting horizMovement and vertMovement based on your character controller.. hopefully that part is easy. You definitely need to already know mecanim before using this example.

Any State -> Attack, this would be called if you used animator.SetTrigger("attack"), then once that state enters it would play your Attack animation and the Behavior attached to this state would exit automatically because it is not set as loop in the inspector of that node and has an exit time of 85% into the animation. This sets a trigger called "transition" to fire which is simply the condition on the transition from Attack to Idle if you click on the transition line.

Are you getting a compile error or just runtime? Don't click the getHit trigger, it's just there as an example.

I definitely don't use nodecanvas anywhere in this attached example. The Node example is in my other thread and it does not use mecanim.. they are totally separate ways of implementing SpineAnimation.