Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0
Issue ID
1214363
Regression
No
[Android]New input system - Touch input performance
Repro Steps:
1. Deploy the project to Android player as developer build.
2. Attach the build to the Profiler
3. Compare the performance between the current implementation of the Input system and 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
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
Resolution Note:
The time it takes for touch event to reach Unity script is quite significant, and varies between 3ms up 15ms, one of the reason is because touch event is received on UI thread and scripts are running on main thread, not to mention we have vsync which can also delay the touch event response time.
Nothing to fix at this moment, since there's no regression here, and there's actually an improvement when comparing old input vs new input