Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.8f1
2022.1.14f1
2022.2.0b6
2023.1.0a9
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-12876
Regression
No
Collision.impulse returns zero when colliding two RigidBody GameObjects
Reproduction steps:
1. Open the user’s attached project
2. Enter Play Mode
3. Observe the Console Window
Expected result: Collision.impulse is not zero
Actual result: Collision.impulse is zero
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a9
Reproducible on: Windows 10 Pro 21H2
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
After review we have elected not to address this issue at this time.