Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note:
After review we have elected not to address this issue at this time.
Resolution Note (6000.0.X):
After review we have elected not to address this issue at this time.