Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
3
Found in
2017.4
2018.4
2019.3
2019.3.4f1
2020.1
2020.2
Issue ID
1230811
Regression
No
[Playables] "Animation Start" function is not trigger when SetTime() with 0 or smaller value is called twice
How to reproduce:
1. Open attached project "Unreliable Animation Events at Start with Playables.zip" and scene "SampleScene"
2. Enter Play Mode.
3. Observe Console window (Start Middle End are called)
4. In Game view, press 2 (this calls SetTime(-1) twice)
5. Observe the Console window
Expected result: Start Middle End are called
Actual result: only Middle and End are called
Reproducible with: 2017.4.38f1, 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Notes: the issue does not reproduce if:
1. "Move Up.anim" is opened in text editor
2. Right above "functionName: AnimationStart", time value is changed from 0 to a really small value (like 0.0001)
3. Save the text file and repeat How to reproduce steps
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
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a4
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b11
Resolution Note (fix version 2020.1):
Fixed in 2020.1.13f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.15f1