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

SetAnimation crashes Unity

alex.seeck

Hi everyone,

I have a small prototype running, with a SkeletonAnimation with 3 Animations with it.

Enter makes the character enter the screen from the right
Idle then makes him idle in the center
Exit then makes him leave the screen

First I did this after pushing a GUI Button:
currentState.SetAnimation (0, exit, false);
currentState.SetAnimation (0, enter, false);
currentState.AddAnimation (0, idle, true, 0);

But I realised, that the animation transitions across the screen because exit and enter somehow get interpolated.

Therefore I am listening to the Spine.AnimationState event End to check if the Exit animation finished. With AddAnimation nothing happened so I tried using SetAnimation in the function that listened to End and... crash Unity.

In essence I'd like to avoid the transition from exit to the enter animation, but I'm also curious, why Unity just crashes during that event?

Thanks in advance.

Addition: I changed listening from End to Complete, which solved the crash, but even SetAnimation is still interpolation across the screen, so now I have no idea how to prevent that.

Pharan

To remove the interpolation, select the SkeletonData asset in your project view. You should see a field called "Default Mix" in the inspector. You can set that to 0 if you don't want interpolation. (In Spine terminology, it's called "mixing").

There's currently a bug(?) where Complete doesn't fire when you have mixing. Other people have been running into the same problem recently. I'm not sure what the intended design is yet, but it totally makes sense to me that you should be able to rely on Complete firing even if there's mixing. The only workaround right now is that you need to set mixing to 0 for Complete to fire.

The crash doesn't make sense though.
What do you mean by "crash" anyway? Like the entire Unity editor stops working and you have to close and restart it? Or it just throws a few exceptions?
And what version of Unity are you using?

alex.seeck

Hi Pharan,

thanks for the quick reply.
The default mix was totally the right value to change. I thought this was the value just set for every new mix and not for any other mix.

First: Yes, listening to Complete works with not crashing anymore (I was listening to End before; what's the difference between those anyway?)
Second: Yes, the Editor just completely froze and I needed to kill it.
Third: It's Unity 4.6.2f1

Pharan

On Complete vs End.
viewtopic.php?f=8&t=4050&p=19552#p19552

Well, we fixed your problem but I'd still like to know why it was crashing. Seems like a problem all the same.
What does the code in your event handler for Complete look like? (when it was crashing)

alex.seeck

I did 3 tests to be absolutely sure that I could reproduce the crash and this is how it finally crashed every time:

string exit = "Exit";
Spine.AnimationState currentState;

void Start(){
   currentState = GetComponent<SkeletonAnimation> ().state;
   currentState.End += FinishAnimation;
}

void FinishAnimation(Spine.AnimationState state, int trackIndex){
   if (!state.GetCurrent (0).ToString ().Equals (exit))
      return;
   currentState.SetAnimation (0, enter, false);
}

Furthermore:
If

currentState.SetAnimation (0, enter, false);

is changed to

currentState.AddAnimation (0, enter, false, 0);

nothing happens.

I hope this helps to clarify if I misused something, or if there's actually a bug in Spine

Ok, I just read a bit further in your link and found this:

Bonus info:
Because of this, End is a bit dangerous. You should never bind a function that calls SetAnimation on End.

Which is exactly describing the behaviour and therefore it's not a bug.