Search Issue Tracker
Active
Votes
0
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.0a1
Issue ID
UUM-120144
Regression
No
Ambient occlusion appears incorrect when character is rendered with a fixed FOV using Render Objects
Reproduction steps:
1. Open the attached “IN-113002” project
2. Open the “Scenes/SampleScene” Scene
3. Enter the Play Mode
4. Observe the character hands in the Game View
Expected result: Character’s hands remain visible at a fixed FOV, and ambient occlusion shadows are correctly applied based on the character’s projected depth.
Actual result: Character’s hands are visible, but ambient occlusion appears incorrect, showing shadows from other objects through the hands
Reproducible with: 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Reproducible on: Ubuntu 25.04, Windows 11
Not reproducible on: No other environments tested
Notes:
- As a workaround, under “Settings/PC_Renderer” set the “Screen Space Ambient Occlusion” Render Feature source to "Depth" and check the "After Opaque" option.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Cascade Shadow atlasing has failed" errors are spammed when two Directional Lights with the Shadow Map are enabled and there is a 3D GameObject in the scene
- Crash on mono_traverse_object_internal when opening a Prefab while in Play mode on a specific project
- About Unity window has huge blank spaces between elements on MacOS
- Crash on UI::Canvas::UpdateEventIndexesRecursive when a script modifies nested Canvases in Play mode while using command line argument -debugallocator
- Custom Render Texture text in Shader Graph’s Graph Inspector’s Active Targets section does not fit when added even if the Active Targets section has a lot of space, and half of it is unused
Add comment