Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.44f1
2022.3.49f1
6000.0.22f1
6000.1.0a7
Issue ID
UUM-83384
Regression
No
Lighting Settings Advanced Filtering sets "Direct Denoiser" to "Optix" as default even though it is not supported and is disabled in the dropdown
How to reproduce:
1. Create a new HDRP Project
2. In the Project window, right-click -> Create -> Rendering -> Lighting Settings
3. Open the created Asset in the Inspector and navigate to the "Filtering" under the "Lightmapper"
4. Change the "Filtering" to the "Advanced"
5. Observe the "Direct Denoiser"
Expected results: "Direct Denoiser" is set to a supported option
Actual results: "Direct Denoiser" is set to "Optix" even though its choice is disabled in the dropdown and can't be selected again once unselected
Reproducible with: 2021.3.44f1, 2022.3.49f1, 6000.0.22f1
Reproducible on: macOS Sequoia 15.0 (M1)
Not reproducible on: No other environment tested
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
- UI Toolkit Debugger Pick Element does not react to the Burst Inspector window when hovering over the Burst Inspector window
- Some buttons in the Burst Inspector window crop the button text from the left side making it unreadable when the window is smaller, and the window has to be almost fullscreen for the full button text to show
- Text in the Burst Inspector Left side panel overlaps/goes out of bounds when scrolling
- Multiple "Incompatible keyword states" or “Keyword state size mismatch (60 vs 59 keywords)“ Errors when opening the project
- Non-editable Repeat - X and Repeat - Y settings appear when UI Builder Canvas Background is set to image
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.