Search Issue Tracker
Active
Under Consideration for 1.8.X
Votes
13
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-777
Regression
No
GamePad.SetMotorSpeeds CPU usage is 3 times higher when the controller is connected via Bluetooth
Reproduction steps:
1. Open the attached “Rumble.zip“ 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
Note:
- 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
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.