Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
3
Found in
2023.1.0a6
Issue ID
UUM-1585
Regression
No
Mouse input becomes choppy or slow when the framerate is limited by Application.targetFrameRate
How to reproduce:
1. Open the user attached project (TestMouseInput.zip) and make sure the "TestMouseInputCamera" scene is open
2. Enter Playmode
3. Hold down the left mouse button and move the cursor in a circle around the cubes in the scene
4. Press the space key and observe the movement and change in the graphs
Expected result: There is no change in the mouse movements or the graph behavior
Actual result: The movement becomes slower or choppy as if mouse input is registered at a lower framerate than the game is running in with the graph showing gaps between actual mouse inputs
Reprocucible with: 2019.4.30f1, 2020.3.18f1, 2021.1.22f1, 2021.2.0b12, 2022.1.0a7
Notes:
1. Reproducible on Ubuntu 20.04
2. Not reproducible on Windows 10
3. Issue isn't present in builds, only on the Editor
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Unable to repro this issue in trunk 2023.1.oa15, 513aa546b2a7
Resolution Note (2023.1.X):
Unable to repro this issue in trunk 2023.1.oa15, 513aa546b2a7