Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0a1
2018.3.0a1
2018.3.14f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1163915
Regression
No
CommandBuffer.Blit(RenderTargetIdentifier, RenderTargetIdentifier, Material) does not render the Render Texture
How to reproduce:
1. Open the attached project
2. Open the "demo.unity" scene
3. Enter Play mode
Expected result: Both Render Textures are rendered.
Actual result: Render Texture with CommandBuffer.Blit(RenderTargetIdentifier, RenderTargetIdentifier, Material) doesn't get rendered.
Reproducible with: 2019.3.0a7, 2019.2.0b7, 2019.1.8f1, 2018.4.2f1, 2018.1.9f2, 2017.4.29f1.
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note (2019.3.X):
When using `m_Camera.SetTargetBuffers(m_ColorRenderTexture.colorBuffer, m_DepthRenderTexture.depthBuffer);` the alias for CameraTarget will not be set (this is only valid for single render textures).
If you go via this route you need to manually manage your render targets. You can do as follows to have it work as expected:
var rt1 = new RenderTargetIdentifier(m_ColorRenderTexture);
cmdBuffer.Clear();
cmdBuffer.Blit(rt1, blitRenderTexture);
cmdBuffer.Blit(rt1, blitRenderTextureWithMaterial, material, 0);
-Tim C