Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.3.X
Votes
4
Found in
2018.4
2020.1.6f1
2020.2
Issue ID
1282463
Regression
No
Noticable mouse and keyboard input delay on a Vulkan standalone build when VSync is enabled
How to reproduce:
1. Open the user attached project (VulkanInputLag.zip)
2. Press Ctrl+B, select a build location and build the project
3. In the build, move the mouse in a circle around the screen
4. Notice the red dot's location in relation to the mouse pointer
Expected result: the red dot is almost always under the mouse pointer
Actual result: the red dot trails behind the mouse cursor
Reproducible with: 2018.4.28f1, 2019.4.12f1, 2020.1.8f1, 2020.2.0b6
Notes:
1. Reproducible on Ubuntu 18.04 and Windows 10, only using the Vulkan graphics API
2. Both the old and new Input Systems have this issue
3. Not reproducible on the Editor
-
florianhaenel-lge
Mar 04, 2022 10:16
I am seeing this on 2020.3.25f1 on linux 5.13.0-30-lowlatency with nvidia-dkms 510.47.03-0ubuntu0.21.10.1
The lag is 1-2 seconds (!) -
Alverik
May 29, 2021 13:59
Wish I had seen this before, spent hours trying to figure out why I had input lag in my build. Luckily I remembered I had switched to Vulkan the day before and decided to changed it just in case...
-
liamdawe
Nov 07, 2020 17:48
This is affecting Superliminal on Linux with Vulkan -> https://steamcommunity.com/app/1049410/discussions/0/3005551013340762110/
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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
Resolution Note (fix version 2020.2):
Fixed in 2021.2.0a10
Resolution Note (fix version 2020.3):
Fixed in 2020.3.17f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.35f1