Search Issue Tracker
Feature Request
Votes
0
Found in
2021.3.52f1
2022.3.62f1
6000.0.50f1
6000.1.4f1
6000.2.0b3
Issue ID
UUM-107454
Regression
No
There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
Reproduction steps:
1. Create a new project (any template supporting “HDR Display Output” is fine)
2. Go to Edit > Project Settings…
3. In the Project Settings window, search for a setting to adjust Editor interface HDR Paper White value/Editor UI brightness (use the Search box)
Expected result: A setting that changes the Editor’s UI Paper White value exists and allows for Editor’s interface brightness adjustment
Actual result: No such setting exists, Editor UI Paper White nits are locked (seemingly at 160.0f nits)
Reproducible with: 2021.3.52f1, 2022.3.62f1, 6000.0.50f1, 6000.1.4f1, 6000.2.0b3
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- The current approach of how the Editor’s interface handles HDR Display Output is lacking because of this issue, therefore, this is reported as a Usability issue instead of a Feature Request
- It is impossible to adjust the brightness of the Editor’s interface independently from the Scene/Game view
- For certain users, the Editor’s interface may look uncomfortably bright and for others, uncomfortably dark, even though the interface itself is locked at the same brightness value because each display and system process HDR signals differently; hence, a setting to adjust Editor’s interface brightness in HDR is indeed a necessity
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
This is not a bug, but a feature request, moving it to the feature request workflow.