Search Issue Tracker
Active
Under Consideration for 2022.3.X, 2023.2.X, 2023.3.X
Votes
15
Found in
2022.3.12f1
2023.1.19f1
2023.2.0b16
2023.3.0a12
Issue ID
UUM-55081
Regression
Yes
Rigidbody component's values do not translate to the PhysX calculations when they are being overridden via a script
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)
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
- Tilemap Collider 2D is not updating the Collider shapes when removing Tiles on the Tilemap component
- Inspector with the scrollbar is unusable when Material properties are edited and the scene is saved
- The Rendering Profiler module statistics are zero when Application.targetFrameRate is set
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
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?