Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0a1
2018.2.6f1
Issue ID
1078008
Regression
Yes
[Android][GLES] Camera.SetTargetBuffers won't write depth to depth texture on Android devices
Steps to reproduce:
1. Open attached project
2. Build & Run on Android device
3. Observe the difference between editor and device
4. Connect to device using framedebugger
5. Observe the first Draw Dynamic under Blit depth and color section
6. Notice that there is no depth info in this rendertexture
Expected result: Camera.SetTargetBuffers should write depth to depth texture
Reproduced in: 2018.3.0a11, 2018.2.6f1, 2018.2.0b1, 2018.2.0a1
No repro in: 2018.1.9f1, 2017.4.11f1
Regression since: 2018.2.0a1
Tested devices:
Reproduced:
VLNQA00109, Xiaomi MI NOTE Pro (MI NOTE Pro), 7.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00023, Xiaomi Mi 4i (Mi 4i), 5.0.2, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 405
VLNQA00144, Samsung Galaxy S9 (SM-G960U1), 8.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00054, Xiaomi MI 3W (MI 4LTE), 6.0.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
VLNQA00093, Samsung Galaxy S6 Edge (SM-G925F), 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
No repro:
iPhone X iOS 12.0
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
deviljz
Dec 13, 2018 07:38
2018.2.14 this issue still happened
aoicocoon
Oct 19, 2018 03:41
@TOMASKINIULIS
In the future there will have a patch for 2018.3 to fix this issue?
tomasKiniulis
Oct 17, 2018 12:51
Hey,
The fix will be available with 2019.1 version of Unity. A backport for 2018.3 and 2018.2 are being worked on as well.
aoicocoon
Oct 17, 2018 12:43
Can anyone tell me what future version can fix this issue?