Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
Votes
1
Found in [Package]
1.8.1
Issue ID
ISXB-863
Regression
No
[Android] Input lag when dragging a finger across the screen in Player
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Switch to the Android Platform
4. Build and Run
5. Drag your finger across the screen with a reasonable speed
6. Observe the green and red circles
Expected result: Circles keep up with the finger
Actual result: Both circles lag behind the finger
Reproducible with: 1.8.1 (2021.3.36f1, 2022.3.23f1, 2023.2.18f1, 6000.0.0b14)
Not reproducible with: 1.7.0 (2023.2.18f1)
Reproducible on:
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
Not reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- The green circle is moved by the Old Input System, and the red circle is moved by the New Input System
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:
Some of the lag witnessed is due to Android itself (as seen using the developer settings option "Pointer Location"). There is also a slight (one or two frames) lag introduced by Unity which will be addressed as we move forwards. We recommend users to implement touch prediction to interpolate current movement to estimate the position for the next frames.
Resolution Note (1.8.X):
Some of the lag witnessed is due to Android itself (as seen using the developer settings option "Pointer Location"). There is also a slight (one or two frames) lag introduced by Unity which will be addressed as we move forwards. We recommend users to implement touch prediction to interpolate current movement to estimate the position for the next frames.