Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Spine events versus Mecanim Events

Rick74

Hey guys,

So being new to spine and trying to incorporate Spine animations into my game, I'm noticing that when I have an event on the very last frame of a spine animation, that it's not reliably firing off in Unity. However, when it was using mecanim events it never missed a beat.

One thing I did notice is that a Spine animation when converted/instantiated as a mecanim controller would be twice as long as the frame count in spine.

Could this account for the unreliability of events on the last frame?

It's also VERY POSSIBLE that I'm doing something wrong on the export/import that is accounting for this behavior. Like I said...I'm new to this.

Cheers!

08 Sep 2016, 10:48

Well I just did a test and if I move the events to 3-4 frames before the end of the animation, they fire off flawlessly.

Is this a bug?

Pharan

Currently, events from a fading-out animation do not fire.
There's a major rewrite of the AnimationState code and it should fix this inflexibility.
See item #4 here: [runtimes] AnimationState improvements · Issue #621 · EsotericSoftware/spine-runtimes · GitHub

For now though, if that was your problem, I point your attention to this:
spine-runtimes/AnimationState.cs at master · EsotericSoftware/spine-runtimes · GitHub

Just open AnimationState.cs and follow the instructions in the comment. That's a little dirty fix users can apply until we can get the new AnimationState code out the door.

Rick74

Pharan a écrit
Currently, events from a fading-out animation do not fire.
There's a major rewrite of the AnimationState code and it should fix this inflexibility.
See item #4 here: [runtimes] AnimationState improvements · Issue #621 · EsotericSoftware/spine-runtimes · GitHub

For now though, if that was your problem, I point your attention to this:
spine-runtimes/AnimationState.cs at master · EsotericSoftware/spine-runtimes · GitHub

Just open AnimationState.cs and follow the instructions in the comment. That's a little dirty fix users can apply until we can get the new AnimationState code out the door.

Actually I have zero transitions on my animations inside the Animator and I call them with the crossfade function.

animator.Crossfade ("AnimationName", 0);

https://docs.unity3d.com/ScriptReference/Animation.CrossFade.html

0 represents any transition time, so their should be zero transition/fade.

Thanks for the response!