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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
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.