Search Issue Tracker
Fixed in 6000.5.0a8
Fixed in 6000.0.69f1, 6000.3.11f1, 6000.4.0b10, 6000.6.X
Votes
4
Found in
6000.0.67f1
6000.3.7f1
6000.4.0b7
6000.5.0a6
6000.6.0a1
Issue ID
UUM-134064
Regression
Yes
DX12 Player brightness changes when changing Display resolution with Screen.SetResolution()
How to reproduce:
1. Open the attached “IN-131872“ project
2. Build and Run the Player
3. Observe the Player
Actual result: Player brightness changes between resolutions
Expected result: Player brightness does not change between resolutions
Reproducible with: 6000.0.67f1, 6000.3.7f1, 6000.4.0b7, 6000.5.0a5, 6000.5.0a6
Not reproducible with: 6000.5.0a4
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Reproducible in BiRP, URP and HDRP
- Does not reproduce with DX11, Vulkan, OpenGL
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 6000.5.0a8):
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.6):
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.4.0b10):
Fixed in 6000.4.0b10
Resolution Note (fix version 6000.3.11f1):
Fixed in 6000.3.11f1
Resolution Note (fix version 6000.0.69f1):
Fixed in 6000.0.69f1