Search Issue Tracker
By Design
Votes
1
Found in
2021.3.27f1
2022.3.2f1
2023.1.0f1
2023.2.0a20
Issue ID
UUM-40634
Regression
No
[Android] FrameTiming.gpuFrameTime returns 0 when Development Build is enabled
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Build And Run on an Android
4. Observe the text on the right top corner of the Player
Expected result: Max Gpu Frame Time shows the correct value
Actual result: Max Gpu Frame Time is 0
Reproducible with: 2021.3.27f1, 2022.3.2f1, 2023.1.0f1, 2023.2.0a20
Reproducible with devices:
GalaxyS9+ (user’s device)
Not reproducible with the devices:
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76 (Not supported)
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830 (only when built with 2021.3.27f1 shows 0 in both release and development builds)
Samsung Galaxy S9 (SM-G960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
Samsung Galaxy Note9 (SM-N9600), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Galaxy S22 (user’s device)
Windows Standalone Player
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Notes:
- Max Gpu Frame Time shows 0 on HUAWEI Mate 20 Pro because it's not supported
- The user mentioned that Max Gpu Frame Time shows non-zero on GalaxyS9+ when built for Release
- Does not reproduce on Windows Standalone Player
- Shows 0 in both Development and Release on Samsung Galaxy A5 built with 2021.3.27f1
- Does not reproduce in Play Mode
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Could not reproduce the issue on any of the devices