Search Issue Tracker
Feature Request
Feature Request in 6000.6.X
Votes
0
Found in
6000.0.71f1
6000.3.12f1
6000.4.1f1
6000.5.0b1
6000.6.0a1
Issue ID
UUM-137915
Regression
No
"Debug Draw Mode" unchecked checkboxes are not visible
How to reproduce:
1. Create a new project
2. In the Scene view toolbar, click on the "Debug Draw Tool"
3. Observe the menu
Expected results: The checkboxes are visible even though they are not checked
Actual results: The checkboxes are not visible
Reproducible with: 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Reproducible on: Ubuntu 24, macOS Tahoe 26 (M1)
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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.