Reproduction steps:
1. Open the attached “BugReporting” project
2. Build and run the Player (File > Build And Run)
3. In the Player, enter the value 59 into the text box or adjust the slider to the same value
4. In the Player, observe the “FPS:” text below the slider
Expected result: The FPS is an integer fraction of the screen Hz that is close to Application.targetFrameRate, in this case, 60
Actual result: The FPS is not close to the Application.targetFrameRate, in this case, 30
Reproducible with: 2022.3.25f1, 2023.2.19f1, 6000.0.0b15
Could not test with: 2021.3.37f1 (“error CS1061: 'Resolution' does not contain a definition for 'refreshRateRatio” compilation error)
Reproducible on: MacOS Sonoma 14.4.1 (Intel), Windows 10 (user’s)
Not reproducible on: No other environment tested
Reproducible with these devices:
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00372, Samsung SM-G991U (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Could not test with these devices:
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 6.0, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00146, Htc 10 (HTC 10), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
(Performance was lower than 10fps regardless of any settings)
VLNQA00375, iPhone 12 mini (Targeted frame rate could only be set to -1 or 0)
Notes:
- Not reproducible on MacOS Sonoma 14.4.1 (Intel) Buildtime, Standalone Runtime
- The frame rate for other targeted frame rates depends on the device and its refresh rate
- The user reported that disabling Optimized Frame Pacing yields the expected behavior