Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.0-preview.1
Issue ID
1230991
Regression
No
Huge Performance slowdown when using New Input System with Android and iOS
Steps to reproduce:
1. Open and Build User-supplied project ("JoystickTest.zip")
2. Move the Joystick and inspect the Profiler.
Expected: The input system does not take a large chunk of CPU usage.
Actual: The input system takes a large chunk of CPU usage.
Reproduced in: 2019.3.9f1, 2020.1.0b5, 2020.2.0b2 (Input System 1.1.0-preview.1)
Not reproduced in: 2018.4.21f1 ( Can't build )
Devices tested:
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00021, Samsung Galaxy S7 (SM-G930F), Android 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00125, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
iPhone 6S (OS version 13.3.1)
Build crashes:
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
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
- Extended component titles exceed the window's display boundaries
- Light is not applied properly to Terrain Details when using Light Layers
- Opening reference for XR component redirects to a missing page
- [Android]Crash on PersistentManager::GlobalToLocalSerializedFileIndex(SerializedObjectIdentifier const&) when building the Android Player
- [Android] The Video Player stops playing at different points when Skip On Drop is enabled
Resolution Note:
As stated here - https://docs.unity3d.com/Manual/ProfilerWindow.html#deep-profiling
"Deep Profiling is resource-intensive and uses a lot of memory. As a result, your application runs significantly slower while it is profiling."
This especially visible on slower Android devices, please disable Deep Profiling to fix this.