Search Issue Tracker
By Design
Votes
0
Found in
2020.3.41f1
2021.3.14f1
2022.1.23f1
2022.2.0b16
2023.1.0a20
Issue ID
UUM-20141
Regression
No
There is no way to get SSAO (Screen Space Ambient Occlusion) on an object when the object is rendered with the "Render Objects" feature
Steps to reproduce:
1. Open the “SSAO bug” project
2. Open the Game view
Expected result: Both guns look the same
Actual result: The one gun with a custom layer does not have AO (Ambient Occlusion) and looks differently
Reproducible with: 10.10.1 (2020.3.41f1), 12.1.8 (2021.3.14f1), 13.1.8 (2022.1.23f1), 14.0.3 (2022.2.0b16), 15.0.1 (2023.1.0a20)
Reproduced on: macOS Monterey 12.5.1 (Intel)
Note:
- Expand the “Main Camera” GameObject to see guns GameObjects
- Also reproducible in the Player
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
This is currently by design. There are several improvements planned for Render Objects that will address things like this.