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
- 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:
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.