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
- Value discrepancy between LateUpdate and OnAnimatorIK when state transition occurs
- Keyword space mismatch error is constantly appearing in the Editor Console window when shaders contain compilation errors
- Inspector Window Tag Search Bar is not populated with the copy-pasted text when using CTRL+V to paste a tag name
- CompilationPipeline.assemblyCompilationFinished is not invoked when using RequestScriptCompilationOptions.CleanBuildCache
- Error “A renderer material mask can't store more than 128 materials.“ is present when the GPU Resident Drawer is disabled
Add comment