Search Issue Tracker
Won't Fix
Won't Fix in 1.14.X
Votes
0
Found in [Package]
1.14.0
Issue ID
ISXB-1518
Regression
No
Input Events are dropped when using a high polling rate mouse and fast key repeat settings
Reproduction steps:
1. Open the Ubuntu settings
2. Open Accessibility/Typing settings
3. Set "Repeat Keys Speed" value to maximum (or just below it)
4. Open the attached “IN-97436” project
5. Open the “FPS/Scenes/MainScene” Scene
6. Enter the Play Mode
7. While holding movement key (WASD) move the mouse
8. Observe the Game View
Expected result: Camera rotates smoothly
Actual result: Camera rotates sluggishly and inconsistently
Reproducible with: 1.11.2 (2022.3.60f1), 1.14.0 (6000.0.46f1, 6000.1.0b14, 6000.2.0a9)
Reproducible on: Ubuntu 24.04
Not reproducible on: No other environment tested
Notes:
- Reproduction needs a high polling rate mouse (1000+ Hz)
- Windows doesn’t allow such high RepeatSpeed value as Linux does, therefore preventing this bug’s reproduction
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
- Warning icon is cut off and misplaced in Inspector when selecting a Shader with a compiler warning
- AI Navigation Sample Scenes do not work and throws “InvalidOperationException”, “Curl error3”, “CrashReporter”, and “NullReferenceException” errors when using the new Input System Package (default) on a new project
- Bottom of Build Size window in Project Auditor becomes inaccessible when a monitor has a high display scaling
- AI Assistant fails to load account information when AI assistant is opened
- [Linux] Improve "GPUResidentDrawer" warning message to include actionable guidance when creating a new Unity project using Universal 3D Template
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.14.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.