Search Issue Tracker
Fixed
Fixed in 6000.0.25f1, 6000.1.0a1
Votes
1
Found in
6000.0.21f1
Issue ID
UUM-83050
Regression
Yes
The Physics Debugger displays incorrect Collision Volume when compared to its Collider bounds
How to reproduce:
1. Open the “PhysicsDebuggerBug.zip“ project
2. Open the “PhysicsDebugger“ Scene
3. Open the PhysicsDebugger in Window > Analysis > Physics Debugger
4. Enable the “Collision Geometry“ checkbox in the Physics Debug overlay Menu
5. Observe the Scene view
Expected result: The Collider volume fits the green Collider outline
Actual result: The Collider volume fits the Geometry outline only
Reproducible in: 6000.0.20f1, 6000.0.21f1
Not reproducible in: 2021.3.44f1, 2022.3.49f1, 6000.0.19f1
Reproduced on: macOS 14.4.1 (M2), Windows 11
Not reproduced on:
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
Add comment