Search Issue Tracker
Fixed
Votes
0
Found in
2022.3.50f1
6000.0.22f1
Issue ID
UUM-83740
Regression
No
Colliders are shown with incorrect scale when observed through the Physics Debugger Collision Geometry view
Steps to reproduce:
1. Open the attached “IN-85792.zip” project
2. Open the “SampleScene”
3. Open Window → Analysis → Physics Debugger
4. Enable Collision Geometry
5. Observe the drawn collision boxes
Expected result: All colliders are drawn with the same size that the actual Box Colliders are
Actual result: All colliders are drawn with the default(1,1,1) cube size
Reproducible in: 2022.3.50f1, 6000.0.22f1
Couldn’t test in: 2021.3.44f1 (Different Collision Geometry visualization)
Reproducible on: Windows 11, Windows 10
Not reproducible on: No other environment tested
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:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-83050