[Unity] Mecanim/Animator integration coming in the future?

Andrige

Hey Esoteric,
I have not worked with Mecanim yet, but this tutorial video made by the Unity team really showcases some nifty stuff about it. In short, what I found interesting at a glance is controlling animations based on velocity and the visual workflow itself.

So my questions are - Should I wait for an official release from you on such an integration? Should I instead look towards using nicloay's importer? Or finally is there a way to do this through script alone?

And to spice up my first post on this forum, some other stuff:
First off - I backed your project way back to support this software, and finally I'm far ahead with my prototype to start the transition from sprites to Spine. After trying it out for real this time I must say this program is damn awesome, sooo glad I backed it! The user experience and design is top notch, and I can definitely sense you guys are taking the best aspects of 2D/3D editing programs and absolutely owning it.

And lastly, my first animation in Spine:
Loading Image

Pharan

Spine-Unity (Spine-C#) is a bit agnostic and uses its own Animation data structure that can also be used in XNA. It has no knowledge of Unity and its data structures and aren't saved as .anim files like native Unity animations. That's one reason why it isn't possible.
The other reason is that Spine's Animation data structure needs to do things that Unity's Animation system can't. SPINE IS SIMPLY TOO POWERFUL. lol
There would be no facilities in Unity's Animation format to store and animate stuff like draw order and FFD.

I don't think it's feasible to turn Spine.Animations into UnityEngine.Animations for this purpose.
But instead of forcing Spine to fit into Unity's animation system, maybe there's a way for Mecanim to be made to interface with Spine.
There might be some way Mecanim can be made to call SetAnimation and mixing functions to approximate what it's able to do with UnityEngine.Animations.
I'm not 100% sure what's possible with Mecanim though. I've never tried implementing this. But it has crossed my mind.

Andrige

Yeah, I can see the limitations. The FFD will probably be a nightmare too.

However, I have been working non-stop since I wrote this thread, and after working with Spine as-is, I must say it does the job sufficiently. The Animation State Data which allows me to set the blend rates between animations works just fine, and I'm well underway to convert all the animations I need to Spine already.

So yeah... I mean Mecanim integration would be swell but I'm totally fine working with what we have right now.

/thread :p