Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b8
Issue ID
1100348
Regression
No
[Android] SystemInfo.graphicsMemorySize returns different value depending if Vulkan or OpenGLES is used
How to reproduce:
1. Open attached project "GraphicsMemorySize" (or use APK's attached and skip to the third part)
2. Build&Run to Android with Vulkan or OpenGLES2/3
3. Open the application and observe the graphics memory size returned
Expected result - Application should return same value of graphics memory size
Actual result - Application returns different value of graphics memory size depending on Graphics API
Reproducible with - 2019.1.0a12, 2018.3.0b12, 2018.3.0a1
Note - Did not reproduce the issue on iOS, both iPad Mini 4 and iPhone XS return same values on Metal and OpenGLES respectively
Reproducible with:
VLNQA00017, Huawei Nexus 6P (Nexus 6P), 8.0.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00143, Samsung Galaxy S9+ (SM-G965U1), 8.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Huawei FIG-LX1 (FIG-LX1), 8.0.0, CPU: HiSilicon Kirin 659, GPU: Mali-T830
VLNQA00233, Meizu - (PRO 6 Plus), Android 7.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
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 Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
- Graph and Camera options for Render Graph Viewer disappear after maximising the window
Resolution Note (2019.1.X):
On Android, VRAM size on GL is estimated, while Vulkan returns actual values.