Your pad works everywhere except this one game. I promise it isn't broken — its configuration is off (or overreacting), basically every single time. Here's how to prove that in ten seconds, then fix it.

Step 1: Prove the controller works

Before changing any settings, confirm that your pad reports correctly.

  1. Connect it to your computer (use Bluetooth or cable).
  2. Visit our tester page and press any button to activate and start testing.
  3. Press every button and move both the sticks.

If everything registers on this page, your controller and drivers are fine and the problem is entirely game-side.

That single check saves hours of pointless driver reinstalls.

Step 2: Check the input standard

Games generally expect XInput (the Xbox standard). Which is why, pads reporting the older DirectInput standard are often ignored completely.

Many third-party controllers ship in the wrong mode and have a hidden switch — usually Home + A or Home + X, or a physical slider.

See our generic controller guide for the details.

Step 3: Let Steam translate

Steam Input can present almost any controller to a game as a standard Xbox pad- including the non-Steam games added to your library.

When in Steam, open Settings → Controller and enable the support option matching your pad (PlayStation, Nintendo, or Generic Gamepad). This will probably fix the problem you are facing.

Step 4: Watch for conflicts

Only one thing should own the controller at a time. Common culprits:

  • Steam Input running alongside a game's own controller support
  • DS4Windows or similar wrappers left running
  • Vendor software (Xbox Accessories, vendor RGB tools)
  • A second controller connected and claiming Player 1

Close everything else and try again with only one pad connected.

Step 5: Launch order

Some games only detect controllers present at startup. Connect the pad first, then launch the game.

Step 6: In-game settings

Check if the game hasn't defaulted to keyboard input, and look for a "controller" or "input device" option. Some titles need it set explicitly rather than auto-detecting.

If the pad passes the test here but still fails in one specific game after all this, it's a bug in that game's input handling — check its forums rather than replacing hardware- yes, till this point, only try a new controller, if you have one lying around (lol, you might have done that already- all the best and welcome!)