Search Issue Tracker
Active
Votes
0
Found in
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-121405
Regression
Yes
HDR Output gets disabled in the Editor when Reflection Probe is enabled during runtime
Reproduction steps:
1. Make sure your display supports HDR and HDR is enabled
2. Open the attached “IN-119083.zip” project
3. Open the “SampleScene”
4. Enter Play mode
5. Open the Frame Debugger Window (Window > Analysis > Frame Debugger)
6. Under “Ints” dropdown, observe that “_HDR_OVERLAY” and “_HDRColorspace” are enabled
7. From the Hierarchy, select the “Reflection Probe” GameObject and enable it
8. Observe the “Ints” dropdown again
Expected result: HDR output remains enabled
Actual result: HDR output is disabled (the “Ints” dropdown is greyed out, empty)
Reproducible with: 6000.0.0b13, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Not reproducible with: 6000.0.0b12
Reproducible on: Windows 11
Not reproducible on: no other environments tested
Note:
- Having the Reflection Probe enabled when the application starts maintains HDR output, but having the Probe disabled and then enabled sometime after the application starts deactivates HDR output
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Safe area ignores navigation bar on Android when targeting level 35 API or higher
- File watcher does not trigger after the AcquireFloatingLease and before the Entitlement check
- HDR Output gets disabled in the Editor when Reflection Probe is enabled during runtime
- The "Build and Run" Menu option tries to build for the selected Build Platform instead of the Active Build Platform
- Font kerning breaks at runtime when multiple UI Documents use different fonts
Add comment