Search Issue Tracker
Fixed
Fixed in 6000.0.59f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Votes
1
Found in
6000.0.55f1
6000.1.15f1
6000.2.0b13
6000.3.0a4
6000.4.0a1
Issue ID
UUM-113638
Regression
Yes
Screen Space Ambient Occlusion is not visible when the directional light intensity is 0.001 or lower with the Deferred Rendering Path selected
Reproduction steps:
1. Open the attached “IN-110954“ project
2. Open the “Scene.unity” Scene
3. Disable the "Directional Light", or set its intensity to anything below 0.001
4. Observe the Game view
Expected result: Ambient occlusion is still visible
Actual result: Ambient occlusion is no longer visible
Reproducible with: 6000.0.6f1, 6000.0.55f1, 6000.1.15f1, 6000.2.0b13, 6000.3.0a4
Not reproducible with: 2022.3.65f1, 6000.0.5f1
Reproducible environments: macOS 15.5 (M3 Max)
Not reproducible environments: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment