Search Issue Tracker
Won't Fix
Won't Fix in 1.3.X
Votes
0
Found in [Package]
1.3.0
Issue ID
ISXB-96
Regression
No
Animation state gets paused when Animator.CrossFade is called from New Input System callback event
How to reproduce:
1. Open the user's attached project "CrossFadeBugTest.zip"
2. Select the "Cube" GameObject and press Play
3. Press the Return/Enter key
4. Observe the animation state's progress bars in the Animator window
5. Press Spacebar
6. Repeat step 4
Expected result: Animation states play out simultaneously
Actual result: Current animations state gets paused until the other state plays out
Reproducible with: 1.0.0, 1.0.2, 1.2.0 (2019.4.37f1, 2020.3.32f1), 1.3.0 (2019.4.37f1, 2020.3.32f1, 2021.2.17f1, 2022.1.0b14, 2022.2.0a9)
Note: Pressing the Return/Enter key triggers the CrossFade function from Update and Spacebar calls it from a New Input System callback event
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.