Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.0b21
Issue ID
UUM-42141
Regression
Yes
Changes in lighting cause smudges in the Game view when the Resolution is set to 4K and the "Allow DLSS" of the Main Camera is checked
How to reproduce:
1. Open the “IN-46310_repro“ project
2. Open the “SampleScene“
3. Enter Play Mode
Expected result: The lighting changes in the Game view without smudges
Actual result: The lighting changes in the Game view leaving smudges
Reproducible with: 2023.1.0b21
Not reproducible with: 2022.3.4f, 2023.1.3f1, 2023.2.0a23
Could not test with: 2021.3.28f1 (errors)
Fixed in: 2023.1.0f1
Reproducible on: Windows 10
Note: If the Editor crashes, delete the Library folder and reopen the project
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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
Resolution Note:
Using the preconfigured project (IN-46310_Repro) and following the steps in the description section:
I was able to reproduce the issue with 2023.1.0b20. I can see the smudges.
I was not able to reproduce it with 2023.1.10f1, 2023.2.0b6 and the latest Trunk (2023.3.0.a4). I attached gifs of my testing.
Since this issue is only reproducible with a specific old beta version and not official later versions, IMO, we can definitely close this bug ticket. It's hard to track what specific PR fixed it, but there was many changes to the VolumeManager and StaticLighingSky after 2023.1.0b20 (since we merged the branch graphics/rpw/volume-rework2), so it's highly probable the fix is in there.