Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
951267
Regression
No
Black Game view with Frame Debugger when using CommandBuffer.Blit() over Graphics.Blit()
Reproduction steps:
1. Open "frame debugger black screen.zip" project
2. "Window" -> "Frame Debugger"
3. Enable the Frame Debugger
4. Select "Draw Mesh Cube" -> "Preview"
5. Select "MoonRenderPipelineAsset"
6. Check "Blit With Command Buffer"
Expected Result: The Cube should be rendered the same as with "Graphics.Blit()"
Actual Result: The entire Game view becomes black
Reproduced with: 2017.3.0a7, 2017.3.0a4, 2017.2.0b11, 2017.1.1p2, 2017.1.0f3
Did not reproduce on: 2017.3.0b1, 5.6.3p3
Note:
Could reproduce on 2017.3.0b1 and 5.6.3p3 because of script errors.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors when rendering a camera to render texture with only depth
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
Add comment