the old XInputDotNetPure GamePad.SetVibration reliably takes less than 0.1 millisecond. Looking through a profiler it seems that the culprit is this windows-side SwapContext… Either way， has anyone else encountered this problem? We have considered calling it from another thread， but it’s still quite problematic whenever we have to call it. For comparison， it takes between 2 and 5 milliseconds， Hello! We are on version 1.7.0 of the new input system，。
Unity version 2022.3.17f. Calling Gampad.SetMotorSpeeds is extremely slow， would that be viable or is it main thread only? 9597667--1360501--stack.png 1095×543 36.2 KB Thanks for your help! ， currently representing almost half of our game’s entire CPU-time. We have managed to mitigate it somewhat by calling it less often。