Search Issue Tracker
Fixed in 2019.1.X
Votes
1
Found in
2018.1.0b8
2018.1.0b13
Issue ID
1023587
Regression
Yes
[Linux] Strong Input lag when locking cursor and using mouse with 1000hz polling rate
How to reproduce:
1. Open attached project "repo_1023587"
2. Enter the Game mode
3. Move the mouse around for 5s and suddenly stop
4. Spectate Game View for the movement delay
Expected result: camera moves without an input lag
Actual result: camera moves with an input lag
Reproducible with: 2018.1.0b8, 2018.1.0b13
Not Reproducible with: 5.6.3f1, 2017.1.2f1, 2017.2.1f1, 2017.4.0f1
Note: Happens when using Cursor.lockState = CursorLockMode.Locked. Not reproducible with a mouse with 500hz polling rate (tested with 500hz, 1000hz), dpi does not matter (tested with 600, 800, 1800, 12000), also worth noting that one out of ten times it is hard to reproduce, in that case just resize Game View and try again.
Tested using: Ubuntu 16.04
Workaround: if you have an option, lowering your mouse polling rate to 500hz
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
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- [Vulkan] Release memory after deleting image
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Crash on internalABP::BoxManager::prepareData when entering Play Mode
Resolution Note (fix version 2019.1):
Fixed framerate drops caused by repainting on excessive mouse input events.