Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.3.15f1
6000.4.4f1
6000.5.0b5
6000.6.0a5
Issue ID
UUM-141225
Regression
No
"No HDR monitor detected." warning shown in the Rendering Debugger is not clear about needed additional settings
Steps to reproduce:
- Make sure a monitor with HDR enabled is used
- Create a new HDRP project
- Open Window > Analysis > Rendering Debugger
- Navigate to the Rendering tab
- Observe the warning under HDR foldout
Actual results: "No HDR monitor detected." warning is shown without indicating that additional settings need to be enabled in (Project Settings > Player > Allow HDR Display Output)
Expected results: "No HDR monitor detected." warning is shown with clarification that "Allow HDR Display Output" needs to be enabled in Player settings
Reproducible with versions: 6000.2.0a2, 6000.3.15f1, 6000.4.6f1, 6000.5.0b6, 6000.6.0a4
-Not reproducible with versions: 6000.0.73f1, 6000.2.0a1- (Initially thought it was a regression, but was later informed the setting was moved under a different tab)
Tested on (OS): Windows 11, macOS 26.4
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
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
- "Too many sprite tiles on Image" error is spammed in the Console when editing Pixels Per Unit Multiplier on a Tiled Image Type for Scroll View
- Reimporting the Multiplayer Center Starting Sample automatically opens the "Example" scene without prompting to save the current dirty scene
- "'FindObjectsSortMode' is obsolete" errors are thrown when installing "Terrain Tools" package
- The broken Prefab Variant Variant GameObject remains when its parent Variant is recreated
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.