Search Issue Tracker
Fixed in 1.0.0
Votes
0
Found in [Package]
preview - 0.9.0
Issue ID
1183985
Regression
No
[Input Systems] [Android] delta/x [Touchscreen] always returns the same negative value when being used on Android device
To reproduce:
1. Open attached project
2. Build and run Sample scene to Android device
3. Move with the finger on the mobile device left and right
4. Check profiler in Editor
Actual result: delta X returns the same negative value all the time
Expected result: delta x should return a different value
Reproduced on: 2019.2.7f2; 2019.3.0b4; 2020.1.0a4
Can not test on lower versions due to errors.
Can not reproduce on lower than preview - 0.9.0 due to errors.
Tested with:
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00282, Samsung Galaxy S10e (SM-G970U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00166, Huawei P20 (EML-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
No repro: iPad Pro 12'9 (2nd gen) iOS 11.2.1; Editor
Note: logcat attached
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment