Search Issue Tracker
Won't Fix
Won't Fix in 6.0.X
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.
Resolution Note (6.0.X):
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.