Search Issue Tracker
By Design
Votes
0
Found in [Package]
4.8.0, 4.9.0
Issue ID
1123528
Regression
Yes
[LWRP] [Regression] Second camera depth-only doesn't work
Steps:
1. Create a new LWRP project / LWRP template project
2. Create a second camera
- set to Depth-only
- set Depth to 1
- set Culling Mask to some layer only e.g. UI
3. Create a cube and set later to UI so that it is rendered by second camera
Actual: The content of Main Camera is not shown, but the blue default clear color + the cube
Expected: The content of Main Camera is shown + the cube
Reproducible in: 2018.3.5f1, 2018.3.4f1
Reproducible in package: 4.9.0, 4.8.0
Not-reproducible in package: 4.6.0, 4.3.0, 4.1.0
-
Pimpace
Feb 11, 2019 12:07
Dear Devs, would you please tell us at least a workaround for this matter? Perhaps we can achieve this via a custom render pipeline code or something.... I know LW- and HD- RPs are in review, but not to finding anything on this matter is frustrating as hell.
-
NGC6543
Feb 07, 2019 03:31
I want to know how to get this in LWRP, too!
-
BAIZOR
Feb 04, 2019 12:53
RE: Resolution Note:
"This feature has been removed due to camera stacking is producing lots of issues. There will be a better solution for LWRP to achieve this."Question: How?
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
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
Resolution Note:
This feature has been removed due to camera stacking is producing lots of issues. There will be a better solution for LWRP to achieve this.