Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2019.3.0b9
2019.4.0f1
2020.1
2020.2
Issue ID
1257833
Regression
Yes
OnStateEnter is not called when using the Timeline with an Animator on the same GameObject
How to reproduce:
1. Open user's attached "SMBehaviorBug" project
2. Open the "SampleScene" Scene
3. Enter the Play Mode
4. In the Game view press the "ChangeState - Bug" button
Actual result: The "Start 521822810" message is logged in the Console
Expected result: The "Start 521822810" message is not logged in the Console
Reproducible with: 2019.3.0b9, 2019.4.2f1, 2020.1.0b14, 2020.2.0a16
Not reproducible with: 2018.4.24f1, 2019.3.0b8
Notes:
- The State does start only OnStateEnter is not called
- Deleting and re-adding the Animation Track to the Timeline fixes the issue and the OnStateEnter for the Main state is called
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment