Search Issue Tracker
By Design
Votes
7
Found in
2018.3
2018.4
2019.1
2019.1.3f1
2019.2
Issue ID
1159050
Regression
No
[iOS] Unity snaps to every second VBlank via WaitForTargetFPS with Application.targetFrameRate = 60
How to reproduce:
1. Open the attached project (look for "ugsdata-glo-p01.hq" in Edits)
2. Go to the Project Settings-> Quality-> VSync Count set to "Don’t Sync"
3. Build for iOS and deploy the Xcode project to the iOS device
4. In the Player set the slider to e.g. 4 (might need to increase it more to reproduce)
5. Open the Profiler Window in the Unity Editor and select your running Player (from step 2) to profile it.
Expected: Frames get shown on every VBlank, if possible, the time between frames will be ~16 ms
Actual: Frames that should be shown closely before the first VBlank at 16 ms instead rush past that first VBlank into the second VBlank with 33ms instead, the time between frames will be 33ms, a lot of time will be spent on WaitForTargetFPS
Reproducible with: 2018.3.14f1, 2018.4.3f1, 2019.1.7f1, 2019.2.0b8, 2019.3.13f1, 2020.1.0b9, 2020.2.0a10
Devices tested:
Reproducible with:
iPad 7th gen (iOS 13.2.2)
iPad Air 2 (iOS 11.0.3)
iPad 9.7 6th gen (iOS 12.1)
iPad Pro 12.9 1st gen (iOS 13.4.1)
Not reproducible with:
iPhone 11 (iOS 13.5.1)
iPhone 8+ (iOS 12.0)
iPhone XR (iOS 13.4.1)
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
Notes:
- step 2 might be unnecessary as iOS supposedly just entirely ignores that setting
-
roberto_sc
Jul 24, 2019 02:39
The original bug request also questioned whether running WaitForTargetFPS to take 33.33ms when drawing at 16.66ms is not possible is the expected behaviour.
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (2020.2.X):
After investigating this case, it appears to be by design.