Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.37f1
2021.3.7f1
2022.2.0b3
2023.1.0a4
Issue ID
UUM-10184
Regression
No
Profiler Module details panel text becomes red and UI breaks when Show Stats for current frame option is pressed after color blind mode is disabled
Reproduction steps:
1. Create a new Unity project
2. Go to Window > Analysis > Profiler
3. In the Profiler Controls press the burger button
4. Select Color Blind Mode
5. Enter the Play Mode
5. Disable Color Blind Mode
7. Select the "Show Stats for 'current frame'" option
8. Observe the Profiler Module details panel
Expected result: Profiler Module details panel text stays grey and UI stays the same
Actual result: Profiler Module details panel text becomes red and UI breaks
Reproducible with: 2020.3.37f1, 2021.3.7f1, 2022.2.0b3, 2023.1.0a4
Notes:
- Make sure that the Profiler results mode is set to Timeline
- The issue is not reproducible when using Profiler (Standalone Process)
- The issue is reproducible on Windows 10, not reproducible on macOS Monterey 12.3.1 (Apple M1 Max)
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
- The Scrollbar becomes unusable when adding Elements to the List
- "One or more data file missing for baking set NewScene Baking Set. Cannot load shared data." error in Player when a specific project is built
- Choosing new HDR Colour using RGB values breaks colour on Intensity Selectors
- Rendering/Decal Layer Mask options are different inside Prefab Mode and outside Prefab Mode when the project is upgraded to Unity 6
- Incorrect Realtime GI Light Probes baking when more than one Light Probe Group is used and "Baked Global Illumination" is enabled
Resolution Note:
This issue will not be fixed for the following reasons:
- Profiler Window UI must be migrated to UIToolkit in the near future. This issue exists within the legacy IMGUI-based UI implementation, so it will be addressed in the future refactor.
- It is a low user-pain issue which does not break functionality, is rarely encountered by most users, and affected users can work around it (by refreshing UI).
Whilst we would love to fix every issue, we must spend our limited time wisely and fix the most high-priority/high-user-pain issues for our users.