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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
AddForceAtPosition produces different rotation behaviour than MoveRotation in this case.