Search Issue Tracker
Active
Fixed in 1.12.0
Under Consideration for 7000.0.X
Votes
7
Found in [Package]
1.7.0
1.8.1
Issue ID
ISXB-819
Regression
No
[New Input System] Input reports EnhancedTouch delta Position(0,0) when the screen refresh rate is set to 60 or higher FPS
How to reproduce:
1. Open the “IN_71593” project
2. In the Build Settings select the Android Platform
3. In the “Run Device” dropdown, select the desired device
4. Press Build And Run
5. In the Player select 60 FPS or higher
6. Touch the screen and make circles with your finger to print the values
7. Observe Red frames reporting touch.deltaPosition (0,0)
Expected result: Input does not skip frames and Touch.deltaPosition(0,0) is not outputted depending on selected Screen Refresh Rate and Application.targetFrameRate
Actual result: Input reports Touch.deltaPosition(0,0) and skips frames
Reproducible with: 1.7.0, 1.8.1 (2021.3.36f1, 2022.3.22f1, 2023.2.16f1, 6000.0.0b13)
Reproducible on these devices:
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76
VLNQA00611, Samsung Galaxy S24 Ultra (SM-S928B), Android 14, CPU: Qualcomm SM8650-AB Snapdragon 8 Gen 3, GPU: Adreno (TM) 750
VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Dell XPS 15 9510, Windows 10 Pro (not always reliable reproduction)
Not reproducible on these devices:
VLNQA00410, Samsung Galaxy Z Fold3 5G (SM-F926U), Android 11, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Reproducible with: Windows 10
Not reproducible on: No other environment tested
Notes:
- Reproducible in the Play Mode
- On Windows Standalone Player the issue occurs when 120 FPS is selected (keeping steps for Android since it’s easier and more reliable to reproduce)
- Can’t test on iOS (“Undefined symbols” error)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
JesOb
Mar 20, 2024 13:20
This is thread for this
https://forum.unity.com/threads/input-jitter-regression-from-unity-2021-3-19f1.1437934/