Search Issue Tracker
Fixed
Fixed in 2021.3.45f1, 2022.3.48f1
Votes
0
Found in
2021.3.43f1
2022.3.46f1
Issue ID
UUM-80058
Regression
No
Rigidbody2D.SetRotation breaks Interpolation when resetting rotation with interpolation enabled
Reproduction steps:
1. Open the attached “ReproduceSetRotationStutter.zip” project
2. Enter the Play mode
3. Observe the third Sprite from the left
Expected result: The Sprite does not stutter or jitter
Actual result: The Sprite stutters unpredictably
Reproducible with: 2021.3.43f1, 2022.3.46f1, 2023.1.0a18
Not reproducible with: 6000.0.19f1
Fixed in: 2023.1.0a19
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Comments (1)
-
kayroice
Oct 01, 2024 18:07
After upgrading from 2022.3.47 to 2022.3.48, I'm experiencing an issue where 2D GameObjects will receive what looks like an interpolated rotation from what seems to be their Rigidbody2D component. The Rigidbody2D's Interpolation value (Rigidbody2D.interpolation) is set to "Interpolate."
What's happening is that I'll spawn a GameObject, set its rotation to a y-axis value of 180 degrees (Quaternion(0f, 1f, 0f, 0f)) so that it's "looking left", and then move it to a new position using its Transform. While moving it to a new position the y-axis rotation value of the Transform (which was previously set to 180 degrees) will get a new interpolated rotation value between 0 and 180. If I set Rigidbody2D.interpolate to a value of None, then the Transform will not receive a new interpolated value, as expected.
Downgrading to 2022.3.47 with the exact same code, and GameObject settings will not produce this behavior (in fact, no other version of Unity 2022, 2021, 2020, or 2019 has produced this behavior). Upgrading to 2022.3.48 with the same code and settings will consistently produce the unexpected interpolated rotation value behavior.
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
- Decal not projected on top of a Lit Material when MSAA is enabled, and Rendering Path is Forward or Forward+ in a Standalone Build
- Separation lines between minimized fields become invisible when scrolling in the Profiler
- Drag & drop and object picker assignment fail when ExposedReference variables are used in a Timeline clip
- AudioSource.time prints out 0 when AudioSource is not playing even if it is manually set
- [Android][GameActivity] Crash on "UnityMotionEventCallbacks::_GetPointerIdImpl" when giving 8 simultaneous touch inputs
Resolution Note (fix version 2022.3.48f1):
Fix for this issue will be available on Unity 2022.3.48f1 and above
Resolution Note (fix version 2021.3.45f1):
Fix for this issue is available on Unity 2021.3.45f1 and above