Search Issue Tracker
Fixed
Fixed in 1.0.1
Votes
0
Found in [Package]
1.0.0
Issue ID
PROFB-290
Regression
No
Project Auditor - 'Physics2D: Layer Collision Matrix has all boxes ticked' can take you to the wrong tab
In the Project - Project Settings we list an issue for 'Physics2D: Layer Collision Matrix has all boxes ticked' when clicked this can take you to the Project Settings - Physics2D - General Settings instead of Project Settings - Physics2D - Layer Collision Matrix.
After playing with this some more I think it looks to take you to Project Settings - Physics2D and just shows the tab that was last used rather then taking you to the Layer Collision Matrix tab.
!image-2025-02-18-09-17-22-514.png|thumbnail!
!image-2025-02-18-09-17-38-188.png|thumbnail!
Also the description here is a bit odd as it says 'In Physics2D Settings', the tab is called Physics 2D General Settings and also the tick boxes are actually in the Layer Collision Matrix tab
!image-2025-02-18-09-20-26-431.png|thumbnail!
Steps to reproduce:
- Create a Blank 2 Project
- Go to Project Settings - Physics2D - Layer Collision Matrix and ensure all boxes are ticked (I think this happens by default)
- Run the Project Auditor
- Go to Project - Project Settings
- Click 'Physics2D: Layer Collision Matrix has all boxes ticked'
- Notice the tab it takes you to
\\
Actual results: User should be taken to Project Settings - Physics2D - Layer Collision Matrix
Expected results: User can be taken to Project Settings - Physics2D - General Settings
\\
Reproducible with versions: 1.00
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment