XInput vs DirectInput

If you've ever flicked a switch on a third-party controller labelled X and D, wondered why your pad appears twice in Windows, or found a game that flatly refuses to see a controller that works everywhere else, you've run into the XInput/DirectInput split.

It's the single most common cause of "my controller works in some games but not others," and once you understand it, most of those problems become five-second fixes.

XInput vs DirectInput: the short explanation

XInput is Microsoft's modern controller standard, built around the Xbox controller layout with a fixed, predictable button order. DirectInput is the older, more permissive standard that lets manufacturers define their own button arrangement. Most modern games speak XInput; older games and specialist hardware use DirectInput. Neither is universally better — they solve different problems.

The practical difference comes down to standardisation.

XInput has a fixed layout. Button 0 is always A, the triggers are always analog and always in the same place, and rumble works the same way on every device. A game can assume that structure and show correct button prompts without knowing anything about your specific controller.

DirectInput has no fixed layout. Manufacturers assign button numbers however they like, so button 0 on one pad might be button 2 on another. That flexibility is why DirectInput still exists — flight sticks, racing wheels, fight sticks and devices with unusual axis counts don't fit the Xbox mould.

The trade-off is that DirectInput's flexibility means games can't assume anything, which is why a DirectInput device in an XInput-only game often registers as nothing at all.

XInput mode: what it means in practice

XInput mode makes your controller present itself to Windows as an Xbox controller, which means any game expecting standard Xbox input will recognise it immediately with correct button prompts. This is why Xbox controllers "just work" on PC and why third-party pads ship with an XInput switch.

What you get in XInput mode: automatic recognition in modern games, correct on-screen button prompts, working rumble, and analog triggers reported properly as analog.

What you lose: XInput supports a maximum of four controllers; it caps trigger and axis counts to the Xbox layout, and any buttons your controller has beyond that layout — extra paddles, mode buttons, additional axes — may not be exposed.

For the vast majority of players and the vast majority of modern games, XInput is the correct default. If you're not sure which mode to use, use this one.

DirectInput controller: when you actually need it

DirectInput is the right choice when your device doesn't fit the Xbox layout or when a game predates XInput entirely. Racing wheels with separate pedal axes, flight sticks with dozens of buttons, fight sticks, and older PC titles all fall into this category.

Specific cases where DirectInput is correct:

Older games, particularly anything from before roughly 2006, which won't recognise XInput at all.

Devices with more inputs than the Xbox layout allows — a wheel-and-pedal set with a separate clutch axis, or a HOTAS with forty buttons, simply can't be expressed through XInput.

Emulators and specialist software, some of which prefer DirectInput for its per-device flexibility.

Multiple controllers beyond four, since XInput caps at four connected devices.

If you use a racing wheel, our racing wheel calibration guide covers the pedal axis handling that DirectInput exists to support.

Switch controller to XInput: how to change modes

Most third-party controllers switch modes with a physical switch or a button combination held during connection. Check your specific controller's documentation, since the exact combination varies by brand, but the pattern is consistent across the market.

8BitDo pads typically use a button combination held while powering on, with different combinations selecting Xbox, Switch, or DirectInput modes.

GameSir, Flydigi, and similar brands commonly ship either a physical X/D switch on the controller body or a mode toggle in their companion app.

Racing wheels often have a mode switch on the wheel base itself.

Two practical notes. Changing mode usually requires reconnecting the controller for Windows to re-enumerate it — the change rarely takes effect live. And Windows may install a different driver for each mode, so the first connection in a new mode can take a few seconds longer.

If you can't find the combination, the manufacturer's support page is more reliable than forum guesses, since these differ even between models from the same brand.

Controller not detected in Windows: diagnosing the mode problem

If a controller works in some games but not others, the mode mismatch is the most likely cause, and you can confirm it in about a minute. Test the controller outside any game to see how it's presenting itself, then match that against what the failing game expects.

Step 1: See what Windows sees. Open a browser button test and press each button, watching the index numbers that light up.

Step 2: Read the pattern. If the indices follow the standard order — 0–3 face buttons, 4–5 bumpers, 6–7 triggers, 12–15 D-pad — you're in XInput or an XInput-compatible standard mapping. If the numbers are scattered unpredictably, or the D-pad appears as axes rather than buttons, you're likely in DirectInput. Our guide on what gamepad tester numbers mean explains the full standard mapping.

Step 3: Match the mode to the game. Modern game not seeing your pad? Switch to XInput. Older game not seeing it? Switch to DirectInput.

This single diagnostic resolves a large share of "controller not detected" reports, and it's much faster than reinstalling drivers.

Why your controller shows up twice in Windows

Seeing your controller listed twice is normal in specific situations, and it usually means something is presenting a second, virtual copy of it rather than indicating a fault. The two common causes are dual-mode devices and controller emulation software.

Emulation software. DS4Windows and similar tools work by creating a virtual Xbox controller while your physical PlayStation or Switch pad remains connected. Windows correctly reports both: the real device and the emulated one. That's the intended behaviour, not a bug.

The problem arises when a game reads both, producing double inputs where every press registers twice. The fix is to hide the physical controller so only the virtual one reaches games — DS4Windows has a hide toggle, and the free HidHide utility does it more persistently. Our DS4Windows setup guide covers this properly.

Dual-mode devices. Some controllers expose themselves through more than one interface simultaneously, appearing as separate entries.

Stale entries. Windows sometimes retains ghost entries for previously connected controllers. These are harmless but can confuse device enumeration, and clearing them in Device Manager occasionally resolves odd behaviour.

Which mode should you use?

A simple decision path.

Use XInput if you play modern games, you want correct button prompts and working rumble without configuration, and your controller fits the standard Xbox layout. This covers most people.

Use DirectInput if you're playing games from before roughly 2006, you're using a wheel, flight stick, or fight stick with more inputs than XInput supports, you need more than four controllers connected, or a specific emulator requires it.

If a game refuses your controller, switch modes and reconnect before troubleshooting anything else. It takes ten seconds and it's the answer more often than driver reinstalls are.

One last note for PlayStation and Switch controller owners on PC: those pads aren't XInput-native, which is exactly why Steam Input and DS4Windows exist — they translate your controller into something XInput-only games understand. If a game takes an Xbox pad but ignores your DualSense, you've found an XInput-only title, and translation rather than a mode switch is your fix.

The short version

XInput is Microsoft's modern standard with a fixed Xbox-style button layout that modern games assume; DirectInput is the older, flexible standard that lets manufacturers arrange inputs freely, which is why wheels, flight sticks and older games still rely on it. Most third-party controllers switch between them with a physical switch or a button combination held at power-on, and you need to reconnect for the change to register. If a controller works in some games but not others, test it in a browser to see which mapping it's presenting and match the mode to what the game expects. And a controller appearing twice in Windows usually means emulation software is running, which is normal — hide the physical device if you're getting double inputs.