Search Issue Tracker
By Design
Votes
0
Found in
5.4.0f3
Issue ID
863707
Regression
No
Function 'AddForceAtPosition' influences Rigidbody.MovePosition and Rigidbody.MoveRotation
Reproduction steps:
1. Open the attached project;
2. Open the scene 'TestPhys';
3. Ensure 'Impulse' on TestController ('Sphere' gameobject) is unchecked;
4. Enter in the Play mode;
5. Observe how the sphere rotates and moves until coming to a stop;
6. Stop Play mode;
7. Set "Impulse" on the TestController ('Sphere' gameobject) to true;
8. Enter in the Play mode;
9. Observe how the sphere rotates and moves;
Expected result: 'Sphere' should stop after function 'AddForceAtPosition' end (expected_result.gif).
Actual result: 'Sphere' vibrates and a little bit moves (actual_result.gif).
Note: When "IsKinematic" quickly turn on and then off, 'Sphere' moves correctly.
Reproduced with: 5.3.6p4, 5.4.2f2, 5.5.0f3, 5.6.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
Add comment