Never! I'll NEVER use Mecanim!

But I will use Unity 5, because according to the Release Notes:

AudioClip now supports multi selection and editing, so you no longer have to change the same property on all clips one by one, just select all the clips you want to change and get it over with all at once.

Thanks Mitch for your great work. :-) This is going to be fun creative life with spine and your runtime :-)

I have never used mecanim, is it any idea to switch? Any advanteges? (I see @Pharan doesn't seem to think so )

@davidsvson.
There are a lot advantages. Mostly ease of setup, without having to code animation controllers yourself, especially for fun things like blend trees.
I like to roll my own though 'cause sometimes it's hard to get Mecanim to do what you want. Mecanim was really made with 3D animation in mind, whereas I personally like to handle my Spine animations like PlayStation-era 2D sprites.

If Mecanim is what you're used to, it's definitely a good thing to have.
If you've never used Mecanim before, expect to spend some time watching videos and searching how-tos to learn how to use it, as with any part of Unity.

Thanks @Mitch @Pharan and @wrongtarget!

I'll not convert to mecanim in my current project but will try it out for the next one.

Great news! I'm seeing a lot of glitches though with Unity 5.

For testing purposes, I moved a character to a Mecanim state machine (previously setting/mixing clips in code).

• I have a non-interruptible transition to a state (player turns from right to left), which then transitions (non-interruptible) to "idle" at normalized Exit Time 1.0 (no other conditions). This animation is not played entirely, it often ends up with frames half-way in the turning movement, as if leaving too early

• Flipping the skeleton is erratic as well. I can use either
  transform.rotation = Quaternion.AngleAxis(facing < 0 ? 180 : 0, Vector3.up);
  or
  GetComponent<SkeletonAnimator>().skeleton.FlipX = facing < 0;
  to flip the skeleton for all left-facing states. It was working before moving to Mecanim, but now it's erratic. Almost seems as if the state machine is messing with the FlipX state of the skeleton (or is it the root bone transform / both?)

Thanks
Rouven

You have no idea how much this helped our workflow when trying to figure out how to sync animations in Bolt networking. Bolt has mecanim support which automagically sync's everything so adding this basically made our day x 500.

Lifesaver.

I'm pretty new to Spine, and I'm having trouble figuring things out. I've tried the Generate Mecanim Controller thing, but I'm not sure how to use it.
So far I was using the "bake all skins" button, which worked fine, I then created a new animator that used the animations from the ones from the bake. It was fine, except that I had to bake stuff again everytime I changed something.
I've tried "Generating Mecanim Controller", and assigning that generated controller to my baked prefab, but it doesn't seem to work. What am I missing ?

@Mitch That didn't change anything, unfortunately. I have disabled and even removed my second (upper body) layer in the Animator, but the issues persist within the Base Layer.

I just noticed the keys that are dropped are only those that attach an image to a slot. All Scale/Rotate/Translate keyframes are applied just fine.

Sure, just PM me your email address!

This looks amazing! Will these features be included in the tk2d runtime aswell?

It worked, thanks

Would love to see this in the official runtime tho, no pressure