• Editor

  • Blog: New Spine Runtimes documentation

    anglais

  • Nate

  • Message #1
  • Modifié
  • Ce post est en anglais
Related Discussions
...
21 jours plus tard

API Reference - Spine Runtimes Guide That's a lot of information :s

  • Nate

  • Message #4
  • Ce post est en anglais

Tell me about it! It was no small feat to write, but it's a super nice system that is easy to keep up to date. 8)

The API reference is not something you'll probably want to read start to finish (that is what the runtime guide is for), but I hope you guys find it useful to look things up when you have questions.

24 jours plus tard

Is there an upgrade guide from 3.4 to 3.5? I understand that AnimationState and how mixing works has changed, but not sure exactly what I should expect. After upgrading my animations dont play well together anymore, and I dont see the "End" event fire like it used to.

Also, from what I've read, is it correct that when an animation completes, it should be cleared and mix back to setup pose? Unless I queue up another animation or clear it myself, I still see the ended animation in the TrackEntry list (when I call animationState.GetCurrent(index) for example)

Thanks for the help

I have pretty the same questions as msm. A lot of my animation transitions are broken after 3.5 update and I can't find any way to fix it. Seems like every transition now more or less is mixing with setup pose and sometimes it looks very wrong. Can't find any guide or info on how to migrate old animations to new mixing behavior. Is there a way to simulate old transitions at all?

msm, Metaphore, please send us your animations and animation state setups (mix durations in AnimationStateData, setAnimation, addAnimation calls) so we can fix any issues you've found!

I met the totally same problem. End event was not fired when the animation complete. When I changed the animation by code, the End event was fired.