Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3
2019.3.11f1
2020.1
2020.2
Issue ID
1244224
Regression
No
[D3D12] Extra/redundant Color Render Target is used for depth and shadow passes
How to reproduce:
1. Launch Unity using RenderDoc
2. Open the attached project named "Case_1244224"
3. Enter Play mode and capture the Game view using RenderDoc
4. Using the RenderDoc's Event Browser select Camera's Shadows.RenderShadowMap -> Shadows.RenderJob
5. Observe the used Render Targets
Expected result: Only the Depth texture is used
Actual result: Both Depth and Color render targets are used when running D3D12
Reproducible with: 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Could not test with: 2018.4.23f1(Render Event structure was different and Shadows.RenderJob could not be checked for comparison with new streams)
Grpahics APIs tested: D3D11, D3D12, Vulkan, OpenGLCore
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.1f1