If my gamepad worked everywhere except for this one game, I too would be worried and frustrated. Honestly, I remember this happening to me as a kid, playing a TV game with my cousin and uncle. Later I figured out my little brother had simply disconnected my cabled controller.

Anyway, the history of goofiness goes back a long way, and that's not what you're here for, so let's cut to the chase. Your controller works fine everywhere else but not in one particular game- annoying, I know. But I've got you covered, and relax: in most cases this does not mean your controller is broken. So before you panic, follow these steps.

Step 1: Test your gamepad controller's function

Before changing anything, confirm your pad actually reports correctly.

  1. Connect your controller to your computer, phone or tablet (Bluetooth or cable).
  2. Visit our tester page and press any button to activate and start testing.
  3. Once connected, press every single button on your controller and check that the tester records each input and shows feedback on screen.

If every button you press produces a matching change on the tester screen, your controller is 100% fine and the problem is entirely game-side. If a physical press does nothing on screen, you may have a different, hardware-side issue instead.

This single check will save you hours of aimless troubleshooting.

In the All Buttons grid each input lights up with its index- the same numbering the Gamepad API reports.

Step 2: Let Steam translate

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

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

Step 3: 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 a similar wrapper 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 4: Launch order

Some games only detect controllers that were present at startup. If your controller isn't responding in a specific game, switch the game off, connect the controller, then switch the game back on.

Step 5: In-game settings

8 times out of 10, when a controller refuses to respond inside one specific game, the game has defaulted to keyboard input. Launch the game and look for the "controller", "controls" or "input device" options. Inside those menus you'll often find a toggle that switches on gamepad input, or a prompt to start detecting your pad. Older titles such as Counter-Strike 2 are common offenders.

Step 6: Check the input standard

Games generally expect XInput (the Xbox standard), which is why pads reporting the older DirectInput standard can be ignored completely by the software.

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.

If that still doesn't solve your problem, it's worth reaching out to your controller's maker- their website, YouTube channel, or a customer support helpline. We keep a comprehensive list of controller manufacturer customer support contacts to make that quick.

If your controller still refuses to work inside that one game even after these methods and a chat with support, the issue may be in the game's own input handling. Dig through the game's forum discussions, subreddits and YouTube videos, and if you have another controller lying around, try that too. Goodbye and good luck!