Search Issue Tracker
Won't Fix
Votes
3
Found in
5.1.1f1
Issue ID
720772
Regression
No
MovePosition() isn't interpolated
Steps to reproduce:
1. Open attached project ("Interpolate.zip")
2. Open scene PhysicsInterpolationBug
3. Notice that scene has two cubes: Cube, which has Rigidbody with Interpolation disabled and InterpolatedCube, which has Interpolation enabled
4. Run scene and notice that both of the cubes move the same (movement of InterpolatedCube isn't interpolated)
5. Change "Current Movement Type" of each cube to "Velocity" or "AddForce" and notice that movement of InterpolatedCube is indeed interpolated
Workaround: Instead of MovePosition, AddForce or velocity can be used.
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Eideren
Aug 21, 2015 12:45
I'll add that MoveRotation behaves in the same way : ignoring whatever interpolation type stated on the Rigidbody component.