Search Issue Tracker
Won't Fix
Won't Fix in 1.4.X
Votes
2
Found in [Package]
1.4.3
Issue ID
ISXB-345
Regression
No
CPU usage spikes in the Input System when a gamepad and another input method are used at the same time
How to reproduce:
1. Open the attached “InputSystem_PlayerInputTest“ project
2. Open the “TestScene“ Scene
3. Connect a gamepad
4. Enter the Play mode
5. Open the Profiler window and profile the Scene
6. Press the keyboard's and gamepad's buttons at the same time
7. Observe the Profiler
Expected results: There are no CPU usage spikes in the Input System
Actual result: CPU usage spikes in the Input System
Reproducible with: 1.4.3 (2022.1.23f1, 2022.2.0b15), 1.4.3, 1.4.4 (2020.3.41f1, 2021.3.13f1, 2023.1.0a18)
Reproducible with: Windows Standalone Player, Android Player
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
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.4.X):
There are no fixes planned for this Bug