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
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
- Editor hangs when opening Asset picker window for AssetReference and a lot of addresable assets are present in the project
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