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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
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