Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
4
Found in
2018.4
2019.3
2019.3.4f1
2020.1
2020.2
2021.1
Issue ID
1230810
Regression
No
[Playables] Most recent Animation Event is not triggered again when resetting Playable Time with SetTime(-1)
How to reproduce:
1. Open attached project "Unreliable_Animation_Events_at_Start_with_Playables.zip" and SampleScene scene
2. Enter Play mode
3. Observe Console window(Start Middle End are printed)
4. In Game view, press 1
5. Observe the Console window
Expected result: End Middle Start are printed
Actual result: Middle Start Middle End are printed
Reproducible with: 2018.4.29f1, 2019.4.15f1, 2020.1.14f1, 2020.2.0b12, 2021.1.0a7
Comments (1)
-
Quasimodem
Oct 16, 2020 02:29
This bug has been a showstopper for us. As part of our port to the Switch, we've had to move our AnimationController-based system over to a Playables-based system and this bug has cost us dearly.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a2
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0b4
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.3f1