Search Issue Tracker

Fixed in 2021.2.X

Votes

4

Found in

2019.4

2020.1.16f1

Issue ID

1297546

Regression

No

Input in Standalone player is one or few frames behind when vSynch mode set to "On"

Windows

-

Steps to reproduce:
1. Open user's attached project "VsyncBugRepro.zip"
2. Build a Standalone build
3. Press "Down" arrow key (This sets vSynch mode to "Simulated")
4. Press space "Space" few times
5. Notice the Cube appear instantly after pressing "Space"
6. Press "Up" arrow key(This sets vSynch mode to "On")
7. Press Space again and see that a cube appears after small delay
8. Press "Right" arrow key 3 times to set the target frame rate to 15 and vSynch count to 4(This will help see the problem better)
9. Repeat the steps from 3 to 7 to see better results

Expected results: Input is instantly registered with vSynch set to "On"
Actual results: Input is registered after delay with vSynch set to "On"

Reproducible with: 2019.4.27f1
Not reproducible: 2020.3.13f1
Unable to test with: 2018.4 due to project breaking

Windows player with Vsync implementation is always one frame behind

  1. Resolution Note (fix version 2021.2):

    Fixed in 2019.4.35f1, 2020.3.28f1f, 2021.2.11f1, 2022.1.0b7, 2022.2.0a4

Log in to vote on this issue

Comments (1)

  1. evbo_au

    May 27, 2021 04:40

    To be clear, this affects Windows Standalone builds where VSync is enabled, i.e. when QualitySettings.vSyncCount is 1 or greater (with 1 being the default). The vast majority of games will be built with VSync enabled and played at 60 FPS, in which case the image displayed on screen is 16.67ms behind where it should be at all times. This issue does not affect the Windows Editor.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues