Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.6f1
2023.2.0b2
Issue ID
UUM-44766
Regression
No
Animation's behavior remains changed when the Animation's settings are changed and then reverted
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Open the Animator Window, Windows > Animation > Animator
5. In the Hierarchy Window, select “Player” GameObject
6. Press space with the keyboard
7. Inside the Game View, observe that no jumping animation is played
8. In the Animator Window, select the “jumping -> riding” transition
9. In the Inspector Window, tick then untick the “Has Exit Time” Property
10. Repeat the 6th step and observe the animation inside the Game View
Expected result: Jumping animation is not played
Actual result: Animation is played
Reproducible with: 2021.3.29f1, 2022.3.6f1,2023.1.6f1, 2023.2.0b2
Reproducible on: Intel macOS 13.5
Notes:
- It should also be expected that the jumping animation is played. However, the main issue is that the results are inconsistent
- Inside the Animator Window, it can be seen that during the 6th step, the “jumping” animation is not played. It can also be seen that after all the reproduction steps, it is played
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.
Resolution Note (2023.2.X):
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.