14.0 broke controller

[Stashdragon]

I updated to 14 today and now my Dualshock controller works terribly. It takes a few presses or holding down the button for a moment before it registers a button press. It behaves this way both in LB and BB. It worked just fine before the update. 

Edited Saturday at 04:11 PM by Stashdragon

[MysterNybble]

3 hours ago, Stashdragon said:

I updated to 14 today and now my Dualshock controller works terribly. It takes a few presses or holding down the button for a moment before it registers a button press. It behaves this way both in LB and BB. It worked just fine before the update. 

How is your controller connected? Direct to windows, Steam Input, DS4Windows, etc.? USB or Bluetooth?

[Stashdragon]

On 8/15/2026 at 2:16 PM, MysterNybble said:

How is your controller connected? Direct to windows, Steam Input, DS4Windows, etc.? USB or Bluetooth?

It's connected through Bluetooth. It was connected the same before the update as well and it had no problems. 

[zombiesruuun]

Same here, it seems to stutter every 2 seconds or so on my DualShock4 pads on 14.0. Also misses inputs.

 

Tried restarting computer, turning pads off and on etc. Connected direct to windows by Bluetooth, no ds4windows nor steam running.

 

Selecting the "use all controllers" option helps decrease stutters, but the problem is still there.

[ricktn1]

I'll chime in on this. Same is happening here since the update.

Dualsense - usb. Extremely unresponsive in Bigbox mode, borderline unusable. I thought it was Launchbox itself but using keyboard is swift and responsive.

As above, selecting "use all controllers" kind of helps, but the issue is still there - you get around 3-4 seconds of use then 2 seconds of unresponsiveness, rinse and repeat.

Edited 3 hours ago by ricktn1

[ricktn1]

Update.

This appears to be an issue with dinput controllers. After testing, same thing was happening with a Dualshock 4 and Nintendo Pro controller.

However, when using my xbox controller, no such issue at all.

[AstroBob]

Hi Folks,

Thanks for the reports, just to let you know we've identified and fixed this up internally and are aiming to get a hotfix out for this. I'll let you know soon as that is ready.

Thanks for bearing with us there