Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
2
Found in
6000.0.68f1
6000.2.0a6
6000.3.0a1
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-101038
Regression
Yes
Splash Screen disables HDR output
Steps to reproduce:
- Open the project
- Switch to the "Windows-WithoutSplash" build profile
- Build and run on an HDR monitor. (Take note of the brightness and colours).
- Switch to the "Windows-WithSplash" build profile
- Build and run on an HDR monitor. (Take note of the brightness and colours after the splash screen).
\\
Actual results:
The text says "HDR output is off".
Expected results:
The text says "HDR output is on".
\\
Reproducible with versions: 6000.2.0a6, 2022.3.23f1
Not reproducible with versions: 2022.3.22f1
Can’t test with versions:
\\
Tested on (OS): Windows DX12, and Mac.
\\
Notes:
- The splash screen is in SDR, that's ok. But then it should switch back to HDR output after the splash screen. Whether the splash screen is there or not, it should behave the same.
- This also can happen in the editor, by previewing the splash screen. Start playmode on a HDR monitor, it should say "HDR output is on", then preview the splash screen. At the end of the splash screen, you will see "HDR output is off", when you would expect "HDR output is on".
- A workaround is to call `HDROutputSettings.main.RequestHDRModeChange(true);` on the start of the application.
Comments (2)
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Lozoo501
Sep 27, 2025 06:19
Oops, the workaround does work but HDROutputSettings.main.active did not show true when executed immediately afterwards.
Lozoo501
Sep 27, 2025 06:05
It also happens in version 6000.0.57f1, but the workaround has no effect. So the only way is to disable the splashscreen.