Search Issue Tracker
Won't Fix
Votes
31
Found in
2022.3.12f1
2023.1.19f1
2023.2.0b16
2023.3.0a12
Issue ID
UUM-55081
Regression
Yes
ConfigurableJoint's drives behave differently after the PhysX 4.1.2 update
Reproduction steps:
1. Open the attached “IN-58119 Rigidbody Override Bug - 2022.zip“ project
2. Open the “SampleScene”
3. Enter Play mode
Expected result: “Max Vertical” and “Max Mag Vertical” values displayed in the Game view increase to about 5
Actual result: “Max Vertical” and “Max Mag Vertical” values displayed in the Game view increase to about 20-30
Reproducible with: 2022.1.0a14, 2022.3.12f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a12
Not reproducible with: 2021.3.31f1, 2022.1.0a13
Reproduced on: Windows 11 Pro (22H2)
Not reproduced on: No other environment tested
Notes:
- Reproducible in Player
- Reproducible in a new project
- Perform the same reproduction steps with the attached “IN-58119 Rigidbody Override - 2021 No Repro.zip“ project to see the expected result
- The “Rigidbody Override (Script)” component in the Inspector for the “Hand” and “Gun” GameObjects is responsible for overriding their Rigidbody component values
- In 2023.2.0b16 and 2023.3.0a12 Unity Editor versions, a Physics.Physx error is logged in the Console when entering Play mode
Full error message (2023.2.0b16 and 2023.3.0a12):
[Physics.PhysX] Command Body::WakeUp is not supported on PxRigidDynamic instances with physx::PxRigidBodyFlag::eKINEMATIC flag set.
UnityEngine.Physics:set_gravity (UnityEngine.Vector3)
PhysicTest.TestTimeManager:Awake () (at Assets/Scripts/TestTimeManager.cs:17)
-
yant
Dec 11, 2023 12:40
The gravity-related message is getting fixed, but it's not exactly the core of the problem in this particular report. Additionally, the error message won't appear in 2022.3 but the problem will be. Here, we see a behaviour change difference that supposedly happened with the PhysX 4.1.2 update a while back.
-
creat327
Dec 09, 2023 10:07
same here, what amazes me the most is that it is reported and known issue for several releases. This is a critical bug, what's Unity waiting to fix it? to 2025?
-
ColtonKadlecik_VitruviusVR
Nov 22, 2023 18:09
Yea I'm not sure if the error message is 100% connected to my main problem which is that the inertia tensor calculations have changed/are not working correctly.
-
alloystorm
Nov 22, 2023 05:30
This happens to me too when I try to change the gravity at runtime. It appears when you set gravity it tries to iterate all physics objects and call wakeUp on them. Including the ones that are kinematic, as the error message suggests.
I guess I can live with that if that's the only problem.
I can't see your sample project, just wondering if there's any other case that triggers this error and if there's any other symptons?
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
The TGS solver in PhysX 4.1.2 has been improved to produce results that closer match theoretical results for soft springs, and as a consequence of that, some behaviours might appear as joints becoming weaker. In reality, the damping that was inherent to the solver method itself was improved. There's more information posted to the forum thread for this ticket.