Search Issue Tracker
Fixed in 2022.3.23f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X
Votes
0
Found in
2021.3.21f1
2022.2.11f1
2023.1.0b8
2023.2.0a6
Issue ID
UUM-29957
Regression
Yes
Screen Space Ambient Occlusion is not visible when the intensity of “DIrectional Light” is 0.0001 or lower
How to reproduce:
1. Open the user’s attached “URP Beta.zip” project
2. Open the “SSAOBug” Scene (Assets > Scenes > SSAOBug)
3. Open the Game window
4. In the Hierarchy window, select “Directional Light” GameObject
5. In the Inspector window, change the Intensity in the “Light” component to “0.0001”
6. Observe the Game window
Expected result: Screen Space Ambient Occlusion is visible
Actual result: Screen Space Ambient Occlusion is not visible
Reproducible with: 12.1.0 (2021.2.0f1), 12.1.6 (2021.2.19f1), 12.1.10 (2021.3.21f1), 14.0.6 (2022.2.11f1), 15.0.4 (2023.1.0b8), 16.0.0 (2023.2.0a6)
Not reproducible with: 10.10.1 (2020.3.46f1), 12.1.0 (2021.2.0b16)
Reproduced on: macOS 13.2.1 (Intel)
Note: reproducible in the Editor and in the Standalone Player (macOS)
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2023.3):
Fixed in: 2023.3.0a4
Resolution Note (fix version 2022.3):
Fixed in: 2022.3.23f1