Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2018.3.0a5
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a5
Issue ID
1165338
Regression
Yes
Hinge joint motor applies torque as impulse instead of as force when useSpring property is set true
How to reproduce:
1. Open the attached project ("case_1165338-HingeJointForceModeBug.zip")
2. Open the repro scene ("SampleScene")
3. Enter the Play Mode
4. Select the cube from the scene
5. Inspect it's "Current Y Torque" value
Expected results: Torque Y value is equal to the desired value (it's being applied as a force)
Actual results: Torque Y value is 50 times bigger (it\s being applied as an impulse)
Reproducible with: 2018.3.0a5, 2018.4.3f1, 2019.1.8f1, 2019.2.0b8, 2019.3.0a8
Not reproducible with: 2017.4.29f1, 2018.3.0a4
Note:
The issue does not reproduce when the useSpring property is set to false
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2020.1):
Fixed in: 2019.3.0b5, 2020.1.0a3