Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.3.14f1
2019.1
2019.2
2019.3
2020.1.0a1
Issue ID
1163718
Regression
No
[Android] "WebCamTexture" does not work with TOF/Depth cameras
Reproduction steps:
1. Open "1163718" project
2. Build & Run for Android
3. Press "Switch Camera" until you see a black screen
Expected Result: All cameras render
Actual Result: Cameras capable of Depth perception return null and don't render
Reproduced with: 2020.1.0a1, 2019.3.0b1, 2019.2.3f1, 2019.1.14f1, 2018.4.7f1, 2018.3.14f1
Did not reproduce on: 2017.4.32f1 (No cameras seem to work)
Repro Devices:
Samsung Galaxy S10 5G (SM-G977U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a11
Cameras which supports only depth data are now ignored (probably later we'll consider providing depth data support for Android as well, but this should be treated as new feature, not a bug)