Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4.3f1
2020.1
Issue ID
1194494
Regression
No
HingeJoint Limit is not respected when Game Object is disabled and enabled in Play mode
How to reproduce:
1. Open user's attached project ("JointLimitTest.zip") using the EnvIronman VM (more information in Edit).
2. Open SampleScene scene
3. Enter Play mode
4. Disable and enable Test Game Object
Expected result: HingeJoint Rotation limit is respected
Actual result: HingeJoint Rotation limit is exceeded
Reproducible with: 2017.4.34f1, 2018.4.12f1, 2019.2.11f1, 2019.3.0b9, 2020.1.0a11
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note:
Joint anchors are initialised each time gameobjects are enabled, and are set relative to the current poses. In this particular project, this causes the limit to be 45, 90, and so on because of re-activations.