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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Add comment