Search Issue Tracker
By Design
Votes
15
Found in
5.5.0f3
Issue ID
867687
Regression
No
SetTargetBuffers plus RenderTextures don't work with deferred shading
When using SetTargetBuffers on a camera to render to a RenderTexture, rendering only works if the camera is not using the DeferredShading render path
How to reproduce:
1. Open attached project and "MainScene"
2. Set the "Deferred Shading" checkbox on the "Problem Camera Controller" script on the gameobject "ProblemCamera"
3. Press play
Expected behavior: Camera rendering works
Actual behavior: Game view window is all blue on Mac and random color on Windows
Reproducible: 5.3.7p3, 5.4.4p1, 5.5.0p4, 5.6.0b3
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
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
sbsmith
Dec 01, 2017 00:46
This is still present in 2017.2
If you set a camera's targetTexture it will only draw colour and not depth. In the frame debugger you will see the correct target name as the render target. If you use SetTargetBuffers, it will not write anything to the RenderTexture. In the frame debugger you will see the name "No name" as the render target. Any combination of the two will result in either one of the undesired behaviours, but never what you want.