Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.50f1
2022.3.60f1
6000.0.44f1
6000.1.0b12
6000.2.0a8
6000.3.0a1
6000.4.0a1
Issue ID
UUM-101380
Regression
No
[Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
Steps to reproduce:
1. Open the attached project "SampleTest.zip"
2. Switch the platform to Android
3. Build to a Android device
4. Observe the rendering of objects
Expected Results: the cube renders behind the yellow pipe
Actual Results: the cube renders in front of the yellow pipe (See attached Results.png)
Reproducible with: 2021.3.50f1, 2022.3.60f1, 6000.0.44f1, 6000.1.0b12, 6000.2.0a8
Reproducible with these devices:
VLNQA00422, Samsung Galaxy S21 Ultra 5G (SM-G998B), Android 11, CPU: Exynos 2100, GPU: Mali-G78
VLNQA00547, Samsung Galaxy Tab A8 (SM-X200), Android 13, CPU: Unisoc Tiger T618, GPU: Mali-G52
(SauceLabs) Samsung Galaxy S10 (SM-G973F), Android 12
Customer devices:
Galaxy S10+ (Android 11)
Galaxy S21 Ultra 5G (Android 11)
HUAWEI nova 7 (Android 10)
HUAWEI P40 Pro (Android 12)
Galaxy S10e (Android 12)
Not reproducible with these devices:
Galaxy S21 Plus (Android 14)
Galaxy S21 Ultra (Android 14)
Galaxy S10e (Android 11)
Couldn't test with these devices (app fails to load):
VLNQA00381, Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4
VLNQA00282, Samsung Galaxy S10e USA (SM-G970U), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
Notes:
-To avoid applying SSAO to a specific object, rendering is divided using two cameras. The first camera renders objects with SSAO applied, and the second camera renders objects without clearing the buffer using the "Don't Clear" option.
However, an issue occurs on specific devices where depth processing is handled incorrectly
-Issue reproduces with Vulkan and OpenGLES3 Graphic's API's
-Issue reproduces with BiRP, however adding URP breaks 1 of the camera's and the rendering becomes inconclusive (only the red cube is rendered)
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 this issue. After reviewing your submission, we found that the behavior you encountered was due to incorrect usage of the API rather than a defect in the system.
We have provided an example of proper API usage for your reference. Please follow this example to achieve the desired results. If you have further questions or need clarification on API usage, please feel free to reach out.