Search Issue Tracker
Not Reproducible
Votes
2
Found in
6000.0.37f1
6000.1.0b5
6000.2.0a2
6000.3.0a1
Issue ID
UUM-96797
Regression
Yes
The Game view renders extremely saturated or almost black when FSR 1.0, HDR and DX12 are enabled
How to reproduce:
1. Create and open a new URP Sample project
2. Open any Scene
3. Go to Edit > Project Settings > Player
4. Set the “Direct3D12” Graphics API for Windows
5. Enable “Allow HDR Display Output“ and “Use HDR Display Output“ in the Project Settings
6. Select the “Assets/Settings/PC/PC_High“ Render Pipeline Asset
7. In the Inspector enable the “FSR 1.0“ in Quality > Upscaling Filter
8. Switch over to Scene view and then to Game view
9. Maximize the Game view window
Expected result: The render does not change
Actual results: Either the render is excessively saturated or is mostly black
Reproducible in: 2023.3.0a19, 6000.0.37f1, 6000.1.0b5, 6000.2.0a2
Not reproducible in: 2022.3.57f1, 2023.3.0a10
Could not test in: 2023.3.0a11 - 2023.3.0a18 (crash whenever the Graphics API is changed to DX12)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- The issue does not seem to be reproducible in the HDRP Sample Project, so I suspect this is only a URP problem
- User reports that TAA might also have some significance for the reproduction, although I found it has no impact
- Not reproducible with DX11, other upscaling filters, or with HDR turned off
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Unity 6000.0.50f1 seems to have the issue already fixed.
Please try upgrading to 6000.0.50f1 or higher and kindly file another bug report if the issue continues.