Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.44f1
6000.0.17f1
Issue ID
UUM-79016
Regression
No
Layers dropdowns on the Colliders Components have different style than other Editor dropdowns
How to reproduce:
1. Create a new Unity project and a new scene in it
2. In the Hierarchy, right-click -> Create Empty
3. In the Inspector, add a "Box Collider" Component
4. Navigate to the "Include Layers" or "Exclude Layers" field and open the dropdown
Expected results: The dropdown matches the Editor's style
Actual results: The dropdown has a different style
Reproducible with: 2022.3.44f1, 6000.0.17f1
Can't test with: 2021.3.43f1 (No such fields)
Reproducible on: Windows 11 Pro
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:
Thank you for bringing this issue to our attention. This issue is known for all inspectors using dropdowns for layers are behaving the same (check the light inspector for instance). Unfortunately, after careful consideration, we will not be addressing your issue now, as we are committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.
Resolution Note:
Thank you for bringing this issue to our attention. This issue is known for all inspectors using dropdowns for layers are behaving the same (check the light inspector for instance). Unfortunately, after careful consideration, we will not be addressing your issue now, as we are committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.