Aniamtion Blend is weird in Unity 5.6.5

Forums 💬 Slate Sequencer ⚙️ Support Aniamtion Blend is weird in Unity 5.6.5

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #20634
    tiwafic
    Participant

      Hi.
      I’m using Unity 5.6.5 and Slate 1.7.2.
      The Aniamtor Track’s Animation Blend is strange in sometimes.

      [attachment file=”1478″]

      In this sample, frame 623 is begin to blend “attack01” and “idlebattle” two animations.

      [attachment file=”1479″]
      In frame 622, current animation is “attack01”.
      In frame 623, model suddenly change to the other strange shape, just like jumped some frames or “model get shocked”.
      Not smooth change to “idlebattle” animation.

      This situation is not happen 100% time, but it’s happen many times in a complicated Animator Track.

      Is Animator Track have something wrong in Unity 5.6.5?

      #20637
      Gavalakis
      Keymaster

        Hello,

        Generally speaking, because the Animator Track in Slate is using the all-new Unity Playables API, it works better in Unity 2017, because back in Unity 5.6, the Playables API was still in “experimental” mode. With that said, I have not encounter this issue neither in Unity 5.6 or 2017. Do you maybe have a simple project you can send me over (support_AT_paradoxnotion.com) showcasing the problem so that I can take a better look at it?

        If so that would be great.
        Thanks!

        #20636
        tiwafic
        Participant

          I didn’t set this Animator Track’s base Animation yet.

          Now I found the fix way, if anyone have the same situation, maybe can follow those steps to solve this:

          1. Set a base Animation Clip to this Animator track.
          2. Uncheck Use Root Motion.
          3. Click UNITY EDITOR(Not Slate) Play Button, let the game running(Important).
          4. Stop Unity Editor playing mode.
          5. Now maybe the problem is solved.

          #20635
          Gavalakis
          Keymaster

            Thanks for the follow up. I will check some things in the code relevant to what you propose as a fixing workaround and see if I actually missed something to determine if there is a bug there.
            Thanks!

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.