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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.