Search Issue Tracker
Fixed
Fixed in 2022.3.23f1, 2023.3.0a4
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0a4):
Fixed in: 2023.3.0a4
Resolution Note (fix version 2022.3.23f1):
Fixed in: 2022.3.23f1