Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
6.0.0-pre.5
Issue ID
ARFB-398
Regression
No
Incorrect size of environment depth texture is returned when using “TryAcquireEnvironmentDepthCpuImage” and “environmentDepthConfidenceTexture” in AROcclusionManager
How to reproduce:
1. Open the user’s attached “ARFoundation-samples-unity.zip” project
2. Add “Debug.Log(depthImage.width + " " + depthImage.height);” to the “DisplayDepthImage.cs” script
3. Build just the “DepthImage” Scene, run the app on a mobile device, and observe the logs
Expected result: 2048x1536 is logged
Actual result: 256x192 is logged
Reproducible with: 6.0.0-pre.4, 6.0.0-pre.5 (2023.2.4f1, 2023.3.0b1)
Could not test with: 6.0.0-pre.3, 2021.3.34f1, 2022.3.17f1 (Errors after downgrading project or package)
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
LNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
Not reproducible on: No other environment tested
Notes:
- the same issue is with environmentDepthConfidenceTexture
- not reproducible if not setting the “EnvironmentDepthMode” property to “Best” in “AROcclusionManager”
- using an Android device, the logged numbers were 640x480
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[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
Resolution Note:
The GPU & CPU depth images are handled by different code paths that aren't consistent about how they handle resolution.
We're aware of this and may address it in a future release.