Boss fights in Elden Ring don’t leave room for mushy input or delayed dodges. A DualSense feels good in the hand for a game like this, but getting one working cleanly on PC takes a bit of setup, FromSoftware’s port leans heavily on Microsoft’s XInput API, and a DualSense connected natively often shows broken prompts, laggy input, or doesn’t register at all.
DS5Windows (DSX) solves this by presenting your DualSense to the game as a virtual Xbox 360 or DualShock 4 controller.
What Goes Wrong Without It
A few issues show up repeatedly for players running Elden Ring through Steam or mod loaders like Seamless Co-op:
- The controller works in Steam’s Big Picture overlay but the game itself ignores it
- Elden Ring grabs the first XInput device it finds, so a flight stick, virtual driver, or second gamepad can steal priority over your DualSense
- Double input, the game reading both your physical controller and DSX’s virtual one, causing menus to skip two items per press
Building Your Profile
Open DSX, create a new profile (naming it “Elden Ring” keeps things organized if you build profiles for other games too), and set the emulated controller to Xbox 360. This matters specifically because Elden Ring expects XInput natively, and that holds true whether you’re on standard Steam play or a modded setup like Seamless Co-op. Save the profile and select it on your main Controllers tab.
You’ll need ViGEmBus and HidHide installed for any of this to work, grab DSX itself from its official Steam page. If you haven’t set these up before, our Drivers page walks through the install process for both, and covers configuring HidHide’s device-hiding and app whitelist in detail, the short version is: hide your physical DualSense under HidHide’s Devices tab, whitelist DSX under Applications, then enable hiding.
Deadzones That Actually Matter for Dodging
Since dodge timing is everything in this game, it’s worth spending a few minutes on stick tuning rather than leaving defaults in place. Keep the left stick’s deadzone tight enough that small directional inputs register quickly, and give the right stick just enough deadzone to stop camera drift without dulling how responsive lock-on feels. A linear output curve keeps camera movement tracking your input directly rather than smoothing it out. None of these have one universal correct value, your specific controller and your own feel both matter, so treat any number here as a starting point rather than a rule.
For trigger-bound actions like heavy attacks or Ashes of War, lowering the activation threshold so it fires earlier in the pull tends to make combat feel noticeably snappier, the same goes for parry timing if you’ve got it bound to a trigger. Test changes in a low-stakes fight before committing to them for a real boss attempt.
Skip the “1ms Polling Rate” Advice
Some older guides suggest a setting inside DSX to manually override Bluetooth polling rate for lower latency. That setting doesn’t exist, DSX’s developer has said directly that the app reads controller input as fast as the connection allows, with no manual override. If Bluetooth lag genuinely bothers you in a game this demanding, switching to wired USB is the actual fix.
Dealing with Steam Input
Playing through Steam, right-click Elden Ring in your Library, open Properties, go to Controller, and set the override to Disable Steam Input, this hands full control to DSX and clears up the double-input problem. If you’re running the Seamless Co-op mod instead, Steam Input typically doesn’t hook into its custom launcher anyway, so Xbox 360 emulation through DSX tends to just work without needing Steam’s overlay running at all.
When Something Still Feels Off
A controller that drops after alt-tabbing usually means DSX needs a setting enabled to keep controllers connected when the app loses focus. Menu selections skipping two items points back to HidHide not being active or DSX not being properly whitelisted. Seeing Xbox prompts instead of PlayStation icons is just how Xbox 360 emulation displays on screen, not a bug, though NexusMods has UI mods if that bothers you. And if triggers feel sluggish, revisit the activation threshold settings covered above.
Still stuck? Our Troubleshooting guide covers the broader connection issues that sometimes turn out to be the real cause here.