Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
6
Found in
2020.3.37f1
2021.3.6f1
2022.1.9f1
2022.2.0b2
2023.1.0a6
Issue ID
UUM-12639
Regression
No
Interpolation breaks when temporarily moving an interpolated Rigidbody's Transform
How to reproduce:
1. Open the user’s attached project “Repro.zip”
2. Enter Play Mode
Expected result: Interpolated Rigidbody falls down smoothly
Actual result: Interpolated Rigidbody jitters while falling
Reproducible with: 2020.3.37f1, 2021.3.6f1, 2022.1.9f1, 2022.2.0b2, 2023.1.0a6
Reproduced on: Windows 10
Note: According to this article (https://blog.unity.com/manufacturing/expanding-the-robotics-toolbox-physics-changes-in-unity-20221) (Interpolation and extrapolation, point 2) this use case is now supported in 2022.1, but it is clearly still broken
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
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
- Look Dev window flickers when resizing the window after docking it
Resolution Note:
Setting the transform of an interpolated body will still break motion due to the control conflict. While it may be desirable to address this eventually, it's not clear when that happens so I'm closing this case as won't fix for the moment just to reflect that. To add on top of what's been said before, we still need to Sync in the interpolation code because if we don't then we potentially lose user-set poses because of the the way transform dispatch flags are set internally. We no longer sync-clear in the path that runs on the Update that is followed by FixedUpdate that frame though. The blog should have been more explicit about that.
Resolution Note (2023.1.X):
Setting the transform of an interpolated body will still break motion due to the control conflict. While it may be desirable to address this eventually, it's not clear when that happens so I'm closing this case as won't fix for the moment just to reflect that. To add on top of what's been said before, we still need to Sync in the interpolation code because if we don't then we potentially lose user-set poses because of the the way transform dispatch flags are set internally. We no longer sync-clear in the path that runs on the Update that is followed by FixedUpdate that frame though. The blog should have been more explicit about that.