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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
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