Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2022.1.0a12
Issue ID
1370338
Regression
No
[Physics] Articulation Drive force limit uses impulse values rather than forces
Steps to reproduce:
1. Create new project (Or just open attached one and enter play mode)
2. Create 2 Articulation bodies, make one a child of the other
3. Set parent AB to be immovable
4. Set child AB to be prismatic joint on the vertical axis
5. Set child AB to have stiffness of 50 and a force limit of 2
6. Enter play mode
Expected: The force limit of 2 is not enough to hold the body aloft, so child AB should fall towards the direction of gravity
Actual: The force limit of 2 is enough to hold the body, proving that it is actually using impulses (when divided by Time.deltaTime, effectively making the force limit equal to 100)
Reproduced on: 2021.2.0b1, 2021.1.12f1, 2020.3.13f1
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
- Shader Graph Material is left in broken state when switching from a .git branch with no HDRP to a branch that contains HDRP
- Crash on buffer_add_value_full when hovering over SerializedProperty.boxedValue in Debug Mode after ISerializationCallbackReceiver.OnAfterDeserialize modifies value
- Editor is not capitalised consistently in Preferences window
- [Linux] “Restore Defaults” warning window appears behind Profiler Modules dropdown
- [iOS] Time.deltaTime is switching between 9.998583E-06 and approximately 0.01 seconds
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a15
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.3f1.3946
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.23f1
Resolution Note:
Fixed in: 2021.1.28f1