Search Issue Tracker
By Design
Votes
1
Found in
2018.2.9f1
Issue ID
1087512
Regression
No
Rotation constraints are applied in World Space when the parent of the constrained object is rotated with AddForceAtPosition()
How to reproduce:
1. Open the user's project
2. Enter Play Mode
Expected result: Rigidbody rotation constraints are applied in Local Space
Actual result: Rigidbody rotation constraints are applied in World Space
Reproducible with: 2017.4.12f1, 2018.1.9f2, 2018.2.11f1, 2018.3.0b5, 2019.1.0a3
Note: Works as expected when rotation is applied through transform.Rotate()
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
AddForceAtPosition produces different rotation behaviour than MoveRotation in this case.