Search Issue Tracker
By Design
Votes
0
Found in
5.5.0f3
Issue ID
861461
Regression
Yes
RigidBody2D kinematic state does not remove force from object
Reproduction Steps:
1. Open "Rigidbody2D.isKinematic Bug.zip" project
2. Open "Scene" scene
3. Play scene
4. Press "A" key to move "Rigidbody"
5. Press "D" key to change "Rigidbody.isKinematic" to "true"
6. Notice it stops
7. Press "LeftArrow" key to move "Rigidbody2d"
8. Press "RightArrow" key to change "Rigidbody2D.isKinematic" to "true"
9. Notice it does not stop
Expected behaviour: When Rigidbody2D is kinematic it removes all forces just as Rigidbody does.
Actual result: Rigidbody2D does not remove forces, it does not allow to add any more.
Reproduce on versions: Unity 5.5.0p3, 5.6.0b3
Did not reproduce on 5.4.4f1
Regression introduced in 5.5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment