Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
Issue ID
UUM-55407
Regression
No
The depth buffer on CPU is not saved when using Multitarget Renderer
Reproduction steps:
1. Open the attached “ReproProject” project
2. Open the “Assets/Scenes/SampleScene.unity” scene
3. Enter the Play Mode
4. Open Window > Analysis > Frame Debugger
5. In the Frame Debugger window press Enable
6. In the Frame Debugger window go to UniversalRenderPipeline.RenderSingleCamrea: Main Camera > ScriptableRenderer.Execute: Universal Render Pipeline Asset_Renderer > CopyDepth > Draw Mesh frame
7. Shift-click on _CameraDepthAttachment icon
8. Observe the shown texture
9. Observe “Assets/DepthTexture.renderTexture”
Expected result: DepthTexture.renderTexture has information
Actual result: DepthTexture.renderTexture appears black
Reproducible with: 2021.3.32f1
Couldn’t test with: 2022.3.13f1, 2023.1.19f1, 2023.2.0b17, 2023.3.0a13 (error CS1503: Argument 1: cannot convert from 'UnityEngine.Rendering.Universal.RenderTargetHandle' to 'UnityEngine.Rendering.RTHandle') - RTHandle has been deprecated
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.