Search Issue Tracker
Won't Fix
Votes
2
Found in
2017.4.0f1
2018.3.0a1
2018.3.8f1
2019.1.0a1
2019.2.0a1
Issue ID
1137906
Regression
No
Camera Depth is not respected with multiple Cameras when Camera Viewport values are not default
How to reproduce:
1. Open the "Bug" Scene in the attached "CameraViewportDepthRegression.zip" Project
2. Make the "Camera 1 - bug" GameObject Active and "Camera 1 - works" GameObject Inactive
3. Observe the Game View
Expected Behavior: Based on Camera Depth fields the Green Cube is Behind the Red Cube and in front of Blue Cube
Actual Behavior: The Green Cube is behind the Blue Cube and in front of Red Cube
Reproducible with: 2017.4.24f1, 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Note: The Behavior between "Camera 1 - works" and "Camera 1 - bug" GameObjects should be very similar as one of them has Viewport parametre altered by only 0.001. However, it is completely different.
Comments (1)
-
elena7
May 10, 2019 02:34
Can someone in Unity please look into this problem???
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] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
We are currently moving away from fixing bugs in the camera stacking in the legacy rendering system. The code is fragile and fixing one bug normally introduces many more.