Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.42f1
2021.3.14f1
2022.1.23f1
2022.2.0f1
2023.1.0a20
Issue ID
UUM-20012
Regression
No
GameObject remains constrained by previous animation keys after animation state transitions
Reproduction steps:
1. Open the “AnimationIssue“ project
2. Open the “SampleScene” scene
3. Enter the Play Mode
4. Observe the left-and-right-moving “Bad” GameObject
Expected result: the GameObject also rotates
Actual result: the GameObject does not rotate
Reproduced in: 2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a20
Reproduced using: macOS Monterey 12.0.1 (Intel)
Notes:
- We expect to be able to rotate the animated GameObject via script when its current animation does not animate rotation
- Being unable to rotate the animated GameObject seems to be a byproduct of a previous animation state that animated rotation
- Also reproduced in Player
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
- [Android] The Input on the UI is not decoupled from the frame rate when using the "OnDemandRendering" method
- It is not possible to hide the toolbar of the Game window when observed in 2022.2 or later streams
- WebGPU error When over 2GB memory consumption
- WebGL error When over 2GB memory consumption
- "Rendering Debugger" displays incorrect overdraw count when using "Unlit/Texture" shader
Resolution Note:
This is caused by a limitation of the Animator. Once a transform vector is animated, the channel is binded to the Animator and cannot be altered from an external source, like a script.
Workaround: One way to work around this problem is to use an additional GameObject in the hierarchy for your script transforms, keeping them independent from the animated GameObjects, although in the same hierarchy.