Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2020.3.25f1
Issue ID
1394069
Regression
No
Error thrown when disabling rigidbody with a custom inertia tensor and constraint
To reproduce:
- Open Assets/Scenes/SampleScene.unity
- Enter play mode
- Select the "Cube" gameobject and set it to inactive
- Observe the "Inertia tensor must be larger than zero in all coordinates." error in console
Expected result: No errors in the console
Actual result: "Inertia tensor must be larger than zero in all coordinates." error is thrown.
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] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a4
Setting inertia tensor to be equal to zero is now supported. Since zero can never be a valid inertia tensor component from a physics standpoint, the physics engine interprets zeros as infinite values instead. So, for example, a body with (0, 1, 1) inertia tensor is going to be infinitely hard to rotate around X.
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b9
Resolution Note (fix version 2021.2):
Fixed in 2021.2.13f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.31f1