Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.35f1
2021.3.5f1
2022.1.6f1
2022.2.0a17
2023.1.0a2
Issue ID
UUM-7388
Regression
No
In play mode switching Articulation Body's Target value and locking that axis causes the object to dissapear and throw errors
In-play mode switching Articulation Body's Target value and locking that axis causes the object to disappear and throw errors
To reproduce:
1. Open attached project
2. Enter play mode
3. Select Capsule game object
4. Change Target value to 10 in Y Drive
5. Switch Swing Y from Free to Locked
Expected result: The Swing Y locks
Actual result: The object disappears and a lot of errors are thrown.
Invalid worldAABB.Object is too large or too far away from the origin
Assertion Failed on expression: 'IsFinite(d)'
and others.
Reproduced on: 2020.1.0a15 (Feature introduced in this version)
Note: repro gif attached
Note2: Position for the game object is NaN
Comments (1)
-
Dale-Nation
Feb 26, 2024 08:00
When Physx5
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note:
This case has to do with spherical joints. Currently, there is a known issue with PhysX 4 articulations that make spherical joints unstable when they're overconstrained. It's recommended to use two consecutive revolute joints instead of a single spherical instead, as that tends to be simulated much better.