Search Issue Tracker
Won't Fix
Votes
3
Found in
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-59711
Regression
No
Lighting is too bright when Screen Space Global Illumination and/or Screen Space Reflections are set to "Mixed" Tracing mode
Reproduction steps:
1. Open the attached “IN-61095_Mixed Tracing Bug.zip“ project
2. Open the “OutdoorsScene”
3. Enter Play mode
4. Select the “Full RT” GameObject in the Hierarchy
5. Enable it in the Inspector
6. Observe the overall look, colours and brightness of the lighting in the Game view
7. Disable it in the Inspector
8. Perform the same steps (4-6) with the “Both Mixed” GameObject in the Hierarchy
Expected result: The lighting has a similar red colour tone and overall brightness between “Full RT” and “Both mixed”
Actual result: When switching to “Both mixed”, almost all of the red indirect lighting is gone and the white walls with the ceiling become much brighter
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- Reproducible in Player
- Reproducible in a new 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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.