Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
Issue ID
1111663
Regression
No
CommandBuffer.Blit will not show unless Graphics.Blit is also executed as an override
Steps to reproduce:
1. Download and open the attached project
2. Enter Play mode
3. Press the on-screen buttons
Expected result: there shouldn't be a need for an additional Graphics.Blit to blit a CommandBuffer
Actual result: CommandBuffer only blits if Graphics.Blit is also executed
Reproduced on 2017.4.0f1, 2018.3.2f1, 2019.1.0a13
Notes:
- the onscreen buttons enable/disable a script with Graphics.Blit in it
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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Resolution Note:
The backbuffer does not point to a RenderTexture when in Forward rendering. Use framedebugger to help to find out why. And do this to make sure back buffer has a texture:
void OnRenderImage(RenderTexture source, RenderTexture destination)
{
Graphics.Blit(source, destination);
}