Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.15f1
2023.2.4f1
Issue ID
UUM-58365
Regression
No
UI overlay becomes visible in ray-traced reflections when HDR Color output is enabled
Reproduction steps:
1. Open the attached "repro_IN-59322.zip" project
2. Open the "Assets/Scenes/Work/23Accord1025.unity" Scene
3. Observe the Game view
Expected results: The "User Interface" GameObject is not visible on the "Sphere" GameObject
Actual results: The "User Interface" GameObject is visible on the "Sphere" GameObject
Reproduced with: 2022.3.15f1, 2023.2.4f1, 2023.3.0a7
Not reproduced with: 2023.3.0a18
Couldn’t test with: 2021.3.33f1 - HDR not supported before 2022.1 stream
Fixed in: 2023.3.0a8
Reproduced on: Windows 11 (10.0.22621) (user's), Windows 10 (22H2)
Not reproduced on: No other environments tested
Notes:
* Not able to test if the issue is reproducible in the Player as the build always fails due to compilation errors
* Make sure to enable HDR Display output ("Edit > Project Settings... > Player > Other Settings > Allow HDR Display Output > Use HDR Display Output")
* Make sure to enable Ray-tracing ("Edit > Project Settings... > HDRP Global Settings > Camera > Rendering > Ray Tracing”)
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
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