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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment