Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0a1
2017.4.0f1
2018.1.0a1
2018.2.0a1
2018.2.15f1
2018.3.0a1
2019.1.0a1
Issue ID
1099433
Regression
No
Animation transition is delayed when the trigger is pressed
How to reproduce:
1. Open the attached Test.zip project
2. Open the Animator window
3. Select Cube and enter the Play mode
4. Wait for the animation to be completed and then press the trigger
Expected: Animation transition happens immediately after the animation is finished and the trigger was pressed
Actual: Animation transition happens only after a few seconds
Reproduced on: 2017.4.16f1, 2018.1.9f2, 2018.2.17f1, 2018.3.0b11, 2019.1.0a9
Comments (3)
-
jynerso
Sep 19, 2020 18:49
omg.. This bug also appears when the animation does not repeat.
-
shubhamswaraj2021
Aug 19, 2020 13:19
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
-
ErikTouve
Sep 16, 2019 20:02
Sure would be awesome to actually fix it and make it *optional* or something. At least fix the documentation to state that it actually doesn't work.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on vkGetInstanceProcAddr when setting graphics API to "Vulkan" on Fantasy Kingdom learning project
- Overlay Camera "clear depth" not working on Vulkan+Pixel8
- Shadows from Shadow Caster 2D using 2D Colliders show incorrectly when tiles are removed at runtime
- Stencil buffer is incorrectly cleared across Vulkan render passes during depth-only clear operations when using CommandBuffer API
- A non-existent webpage is opened when "Learn about Unity Build Automation" hyperlink is clicked
Resolution Note:
Exit time only applies if the conditions are are met at the exact "exit time". If you set it after, then it should never be taken.
The fact is, today, this transition is getting taken at T= 1+exitTime, 2+exitTime, 3+exitTime, and so on. This is technically a bug, as it should never be taken. But at this point, changing this behaviour means potentially breaking thousands of State Machines that rely on this bug to function properly. For this reason, we will not be fixing this.