Search Issue Tracker
Fixed in 2022.3.21f1
Fixed in 2022.3.X, 2023.2.X, 2023.2.11f1, 2023.3.X
Votes
5
Found in
2022.3.1f1
2023.1.0b20
2023.2.0a18
Issue ID
UUM-38158
Regression
No
Depth is not rendered in a depth-only camera which is set up by a custom script
Reproduction steps:
1. Open the attached "repro_IN-42176.zip" project
2. Open the "SampleScene" Scene
3. Enter the Play Mode
4. Enable the Frame Debugger and observe the output for the "Custom Camera"
Expected result: Depth is rendered on a depth-only camera
Actual result: Depth is not rendered on a depth-only camera
Reproduced with: 14.0.8 (2022.3.1f1), 15.0.5 (2023.1.0b20), 16.0.2 (2023.2.0a18)
Couldn’t test with: 12.1.12 (2021.3.27f1) - Couldn’t resolve errors
Reproduced on: macOS 13.4 (by user), Windows 10
Note: Depth-only camera is initiated with the “DepthCapture“ script
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note (fix version 2023.3):
So by default this will not look like it's fixed due to another issue that's being investigated. But the gist of it is - default value of UniversalRenderPipeline.SingleCameraRequest is not ok to be used in RenderRequest, because it must have destination set(https://docs.unity3d.com/ScriptReference/Rendering.RenderPipeline.StandardRequest-destination.html). In your case this is targetTexture set on the Camera which calls the render request. This is going to be fixed in the future.
So please set the destination in your script and it should work fine now.
Resolution Note (fix version 2023.2):
For the fix to work, it's necessary to pass the 'destination' to UniversalRenderPipeline.SingleCameraRequest and remove the reflection type.
Resolution Note (fix version 2022.3):
For the fix to work, it's necessary to pass the 'destination' to UniversalRenderPipeline.SingleCameraRequest and remove the reflection type.