Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4
2019.1
2019.1.0f2
2019.2
2019.3
Issue ID
1154937
Regression
No
[Android][Vulkan] FrameTimingManager reports GPU Time as 0
Repro steps:
1. Open attached project
2. Build and run on Android
3. Press the "Start Per Capture" button, observe the "GPU Time" graph
4. If the reported time seems normal, add some Physics object with the "+Physics Obj" button
5. Try changing the orientation of the device several times
Actual: The graph bottoms out at 0, sometimes consistently, sometimes intermittently
Reproducible with: 2018.4.3f1, 2019.1.8f1, 2019.2.0b7, 2019.3.0a7
Tested and reproduced on these devices:
VLNQA00149, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00124, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00263, Google Pixel 3 (Pixel 3), Android 9, CPU: Snapdragon 845, GPU: Adreno (TM) 630
VLNQA00052, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00009, Samsung Galaxy Note8 (SM-N950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
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
- Camera.current returns null when Camera.targetTexture is set to null in OnPostRender
- Crash on BaseHierarchyProperty::Next when opening a specific project
- 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
This is a duplicate of issue #1152859