It would be really, really bad if your use of a 360 controller started tanking framerates ahead of Dark Souls 3 coming out in just a few days. That’s exactly what’s happening on certain beta builds of Windows 10, even in older games that shouldn’t be an issue for modern computers. Tagging themselves in, handy Reddit posters have already found workarounds to the bug.
For other questions on PC quality, here’s our Dark Souls 3 PC port review.
The issue is present in the latest Windows Insider beta updates, and seems to affect lots of different games. The poster in question tested it on Dark Souls 2’s Scholar of the First Sin HD update, but given Dark Souls 3 is the next game you’re likely to play on a controller (Tuesday. TUESDAY.), better get it fixed. It also affects programs like Joy2Key that emulate the 360 driver for use with DualShock or other controllers.
There’s a couple of solutions. The easiest is to stop getting Windows Insider beta updates, by navigating to Windows Update on Win10 and turning off the Insider Preview Builds option. If that’s not possible - or you just love betas, I ain’t gonna judge - you can instead go to your device manager and start messing around with the 360 controller drivers:
- Find Xbox controller in Device manager, right click and "Update driver software"
- Select "Browse computer for driver software"
- Select "Let me select from a list of device drivers on my computer
- Choose the top version 22.214.171.1249 [8/13/2009]
- Reboot and play
That’s taken directly from this thread and there’s multiple reports of it fixing the issue. It’s possible Microsoft will have cleared the problems up - considering both halves of the problem are their software/hardware - by release but, hey, just in case. We’ll update this post with more issues and workarounds as they’re inevitably found next week.