Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.17f1
2021.1
2021.2
2022.1
Issue ID
1362001
Regression
No
"No cameras rendering" message flickers in the Game view when CommandBuffer is executed by Graphics.ExecuteCommandBuffer
Reproduction steps:
1. Open the attached "CommandBufferNoCamera.zip" project
2. Open the "SampleScene" Scene
3. Enter Play Mode
4. Observe the Game view
5. Exit Play Mode
6. In the Hierarchy select the "CommandBufferController" GameObject
7. In the Inspector enable the "Graphics Mode" property
8. Enter Play Mode
Expected result: The results with "Graphics Mode" disabled and enabled are visually the same in the Game view
Actual result: "No cameras rendering" message flickers in the Game view, rendering is also done in other Editor windows
Reproducible with: 2019.4.30f1, 2020.3.17f1, 2021.1.20f1, 2021.2.0b11, 2022.1.0a7
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
The user has disabled the camera, this is why the message appears and it is working as intended.