Search Issue Tracker
Won't Fix
Votes
7
Found in
2020.3.48f1
2021.3.25f1
2022.2.18f1
2023.1.0b15
2023.2.0a13
2023.3.0a3
Issue ID
UUM-35443
Regression
No
[Android] Player Loop in Profiler is not steady when empty Scene is open in Player
Reproduction steps:
1. Open the attached project “PlayerLoopNotSmoothProject”
2. Select Android in Build Settings
3. Make sure "Development Build" is enabled in Build Settings
4. Enable Autoconnect Profiler
5. Build and Run on an Android device
6. Inspect PlayerLoop in the Profiler
Expected result: The PlayerLoop in the Profiler should be smooth/flat at 16.67 ms
Actual result: The PlayerLoop as shown in the Profiler is very jaggy
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.18f1, 2023.1.0b15, 2023.2.0a13
Reproducible with these devices:
Samsung Galaxy S10 (Mali-G76 MP12)
Huawei P30 Lite (MAR-LX1A) (Chip: Kirin 710, Gpu: Mali-G51, Android 10)
Samsung Galaxy S6 edge+ (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
Samsung Galaxy S9 (SM-G960F), CPU: Exynos 9 Series 9810, GPU: Mali-G72, OS: 10.0.0
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:
After testing, we can confirm that the fluctuations seen around the time taken for the PlayerLoop and the median loop time are within the expected range. There are no abnormalities when checking CPU usage or logs.
The small variations seen per loop are normal and can be caused by many factors, such as time taken by the app when migrating between CPU cores or performance change due to CPU frequency scaling, etc.
Ensure the "Optimize Frame Pacing" setting is ticked if it isn't yet, as this option can reduce the fluctuation on Android. Closing as no fix is needed.