Search Unity

  1. Check out the Unite LA keynote for updates on the Visual Effect Editor, the FPS Sample, ECS, Unity for Film and more! Watch it now!
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. Improved Prefab workflow (includes Nested Prefabs!), 2D isometric Tilemap and more! Get the 2018.3 Beta now.
    Dismiss Notice
  4. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice
  5. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

Animations stuck in first frame in build

Discussion in 'Animation' started by tfgrip, Jul 5, 2018.

  1. tfgrip

    tfgrip

    Joined:
    Oct 12, 2017
    Posts:
    13
    Hello,

    we are currently working on a project that manages animations via Playable API. We had to upgrade Unity from 5.6 to 2017 (and then 2018) and we are currently experiencing issues with some animations not playing in builds.

    Everything works in editor as expected, but in builds some of the animations get stuck in what seems to be the first frame. There are some animations that are running without issue however, and we can't see any obvious difference.

    The code is taking the same code path, values seem to be set up the same as well. We're having a hard time figuring out where even to look for a problem.

    We were thinking that maybe we haven't updated from old experimental Playable API properly, but that doesn't explain why in editor animations play alright. Is there, however, some info about what has changed? We can't no longer see PlayableHandle in docs, even though the handles still exist in some way.

    Do you have any idea where to look at for a problem?

    Thank you.
     
    Last edited: Jul 6, 2018
  2. tfgrip

    tfgrip

    Joined:
    Oct 12, 2017
    Posts:
    13
    We have solved it, it wasn't an issue with playables per se. Certain constants were behaving differently in build, causing conditions to evaluate differently and setting timescale on some animations to 0.