Search Issue Tracker

In Progress

In Progress in 1.8.X



Found in [Package]


Issue ID




GamePad.SetMotorSpeeds CPU usage is 3 times higher when the controller is connected via Bluetooth

Package: Input System


Reproduction steps:
1. Open the attached ““ project
2. Connect Xbox One controller via Bluetooth
3. Enter Play mode and open the Profiler window (Window > Analysis > Profiler)
4. Observe the “SetMotorSpeeds” frame in the Timeline section of the Profiler window

Expected result: CPU usage for “SetMotorSpeeds” frame is 0.015-0.040ms
Actual result: CPU usage for “SetMotorSpeeds” frame is 0.970-1.50ms

Reproducible with: 1.7.0 (2023.2.9f1), 1.8.0-pre.2 (2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6)

Reproduced on: Windows 11 Pro, Windows 10 (By reporter)
Not reproduced on: No other environment tested

- Couldn’t test on DualShock and DualSense as controllers didn’t rumble or rumbled inconsistently
- User reported that the issue is also reproducible in the Player

Comments (3)

  1. anthony_sloth

    May 16, 2024 06:55

    A Correction,
    We did some tests and it appears to be an issue with Xbox controllers (both Xbox One + Xbox Series controllers). We didn't see the same values for PS4, PS5 or Nintendo Switch Pro Controllers

  2. anthony_sloth

    May 16, 2024 04:44

    We see large CPU for wired controllers as well.

  3. neon8100

    Feb 20, 2024 22:28

    Just experienced this issue yesterday. Present in 1.7. Basically a blocker for using the Input System/Rumble with a controller in a shippable PC build as most users will have Xbox gamepad. The workaround is to use less rumble for now, but really not ideal... Please fix this.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.