Search Issue Tracker
Fixed
Fixed in 6000.3.13f1, 6000.4.1f1, 6000.5.0b2, 6000.6.0a2
Votes
0
Found in
6000.3.0a5
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-137414
Regression
No
MassConfiguration Issues with PhysicsBody
When using PhysicsShape with PhysicsShapeDefinition.startMassUpdate disabled, for the purpose of setting the PhysicsBody.massConfiguration directly, the PhysicsBody is not configured correctly unless PhysicsBody.ApplyMassFromShapes is called.
This is by design by Box2D however it is not intuitive.
In additional, there are only getters that directly expose the mass, rotationalInertia and localCenterOfMass so a full MassConfiguration must be set. To make this more intuitive, we should add setters for these properties.
Finally, the scripting documentation is rather sparse in describing these methods and properties so they should be improved too.
Discussions Post: [https://discussions.unity.com/t/physicscore-2d-is-it-required-to-call-applymassfromshapes-before-setting-massconfiguration]
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
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
Resolution Note:
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.5.0b2):
Fixed in 6000.5.0b2
Resolution Note (fix version 6000.4.1f1):
Fixed in 6000.4.1f1
Resolution Note (fix version 6000.3.13f1):
Fixed in 6000.3.13f1