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
- UTF-8 character in index.html is corrupted when building a WebGL project
- Help box icon in "Tile Palette" window is blurry in both Unity themes
- Memory leak when importing a non-embedded-texture FBX exported from Character Creator 5 with “Mouth Open as Morph” and “Convert Skinned Expressions to Morphs” enabled
- Drop-down component is overlapped with the default Tile Palette layout line
- VisionOS Player and Simulator crashes on "nw_read_request_report [C1] Receive failed with error "No message available on STREAM"" when playing a video through VisionOSVideoComponent
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.