Search Issue Tracker
By Design
Votes
0
Found in
5.4.0b17
Issue ID
797805
Regression
No
Command buffers don't work until the camera is re-enabled
Steps to reproduce:
1. Open project
2. Open "editor_tool_scene" scene
3. Go to Main Camera in object hierarchy and locate "Simple Screen Space Ambient Occlusion" script
4. Edit script and comment out 159-161 lines (These code lines disable and re-enable main camera)
5. Change Mode property to Integrate or Multiply
Results: You can see that SSAO doesn't change even though command buffer was updated as it for some reason needs to re-enable camera.
Note: User mentioned that sometime SSAO command buffer doesn't need to re-enable camera to take effect in certain scenes (Couldn't reproduce that).
Workaround: Disable and then enable camera in SetupCommandBuffers() method.
Reproduced with: 5.3.4b18; 5.4.0b17; 5.3.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when rendering 60 real-time lights in the far distance
- Black artifacts appear in the Scene view when moving the mouse with the Scene and Device Simulator windows open
- [OculusXR][GLES] Render pass validation errors on Quest devices when Multi Pass is selected using OpenGLES if HDR or MSAA camera settings differ from URP asset
- Extended component titles exceed the window's display boundaries
- Light is not applied properly to Terrain Details when using Light Layers
Add comment