Search Issue Tracker
By Design
Votes
1
Found in
5.4.1f1
Issue ID
836103
Regression
No
CommandBuffer.Blit does not produce the same result as Graphics.Blit
Reproduction steps:
1. Open the project
2. Open the "Test_CommandBufferBlit" scene
3. Play the scene and notice the gray screen
4. Open the "Test_GraphicsBlit" scene
5. Play the scene
Actual result: CommandBuffer.Blit and Graphics.Blit produces different result (image attached)
Expected result: CommandBuffer.Blit and Graphics.Blit produces the same result (image attached)
Reproduced on: 5.5.0b6, 5.4.1p3,
Shaders are not working correctly on 5.3 and 5.2 versions.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
From user's code we can see that the script doing Graphics.Blit also set the Camera.targetTexture. But in commandbuffer one, the user didn't do that, and that's why the depth/stencil contents get lost.