Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6, 2017.1, 2017.2
Duplicate in 5.6, 2017.1
Votes
0
Found in
2017.1.0p2
Issue ID
938978
Regression
Yes
Animator.Update(0) fires events twice
Steps to reproduce:
1. Open user attached project
2. Load TestScene.unity
3. Press spacebar to trigger an animation
4. Observe that two event calls are displayed in the console
Expected result: Animator.Update(0) should not fire events
Reproduced in: 2017.3.0a3, 2017.2.0b6, 2017.1.0p3, 5.6.3f1, 5.5.4p2, 5.5.1f1
Not reproduced in 5.5.0p4, 5.4.6f1
Regression since: 5.5.1f1
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 SceneVisibilityState when trying to open a project containing another project in the Assets folder
- Reflection probe bounces don't work when Rendering Path is set to 'Deferred'
- Shader error undeclared identifier "UNITY_TRANSFER_LIGHTING" when building project
- Shader effect with specific view disappears when multiple materials in scene are present
- Crash on ShaderLab::IntShader::CreateLocalKeywordRemap when loading custom shaders on standalone build
Add comment