Interactive Troubleshooter

Published: Oct 19, 2026

Game Controller Detected But Not Working in Game - XInput vs DirectInput Tree

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Exhaustive root-cause troubleshooting decision tree to diagnose gamepads detected by Windows or Game Controllers (joy.cpl) that fail to respond inside games due to XInput vs DirectInput API mismatches, Steam Input overrides, virtual HID device priority conflicts, and Bluetooth input reports.

Full Diagnostic Tree & Step-by-Step Overview

How does your controller behave across Windows control panels and in-game environments?

Controller tests perfectly in Windows joy.cpl, but modern games (Xbox Play Anywhere, Steam, PC Game Pass) ignore all button inputs
Controller works inside Steam Big Picture mode, but in-game inputs are unresponsive or mapped incorrectly
Controller buttons work, but analog sticks, triggers, or motion controls respond erratically or conflict with mouse/keyboard input
Multiple controllers or virtual input devices are connected, and the game listens to the wrong input device ID

What type of controller hardware and physical connection interface are you using?

Legacy DirectInput gamepad or DualShock 3/4 connected to a modern XInput-only game (e.g., Unreal Engine / Unity titles)
Gamepad equipped with a physical hardware toggle switch (X/D mode switch) on the back or bottom shell
PlayStation DualSense or DualShock 4 connected over Bluetooth without native Windows XInput emulation
Nintendo Switch Pro Controller or generic Bluetooth gamepad failing HID report parsing in non-Steam games

How is the game launched and what launcher input abstraction software is active?

Game launched via Steam, but Steam Input override settings conflict with native game controller support
Non-Steam game (Epic Games, EA App, Ubisoft Connect, PC Game Pass) launched without Steam Input translation
Third-party input mapping software (DS4Windows, x360ce, ReWASD) creating double-input or unhidden physical HID conflicts

What specific input axis or button mapping anomaly are you experiencing?

Triggers (LT/RT) behave as digital buttons or share a single combined axis instead of independent analog axes
Game rapidly toggles UI between Keyboard/Mouse prompts and Controller prompts, freezing inputs
Right analog stick camera movement maps incorrectly or triggers button presses inside DirectInput games

What additional input devices or virtual controller drivers are active in Windows Device Manager?

Virtual joystick drivers (vJoy, vXbox, ViGEmBus) or flight sticks occupy the primary Player 1 device slot
Keyboards or mice with embedded virtual HID gamepads (e.g., Razer Tartarus, Wooting keyboards) taking input priority

Bridging DirectInput Controllers to Modern XInput Games with x360ce or XInput Wrappers

Solution:

Root Cause: API Architecture Mismatch Between DirectInput and XInput

DirectInput is a legacy DirectX API introduced in Windows 95 that supports up to 8 axes, 128 buttons, and multiple joysticks per device. Modern PC games built on XInput (introduced with the Xbox 360) expect a rigid 4-axis, 10-button, 2-trigger layout mapped via specific kernel-mode drivers (xusb21.sys). When a DirectInput gamepad connects to a modern XInput-only game, the game engine bypasses DirectInput enumeration entirely, leaving the controller completely unresponsive despite being recognized by Windows.

Diagnostic Verification:

1Press Win + R, type joy.cpl, and hit Enter.

2Select your controller and click Properties.

3If button tests show numbered buttons (e.g., Button 1, Button 2) and combined Z-axis triggers rather than standard Xbox button names (A, B, X, Y, LT, RT), your device operates exclusively in DirectInput mode.

Step-by-Step Fix:

1Download XInput Translation Wrapper:

Download the latest release of x360ce (Xbox 360 Controller Emulator) or XOutPut.

2Place Wrapper Files in Game Directory:

Extract x360ce.exe directly into the game's root executable directory containing the main .exe file.

3Map Axes and Buttons:

Run x360ce.exe as Administrator.

Allow the utility to search online for matching controller profiles or manually map your DInput axes to standard XInput controls.

Ensure xinput1_3.dll or xinput1_4.dll is generated in the game folder.

4Save and Launch Game:

Close x360ce.exe and launch the game directly.

Prevention & Long-Term Monitoring:

When buying third-party controllers, ensure product specifications explicitly list native XInput or PC/Xbox compatibility.

Toggling Physical Hardware XInput / DirectInput (X/D) Switches

Solution:

Root Cause: Controller Hardware Mode Selector Set to Legacy DirectInput (D) Mode

Many third-party PC controllers (e.g., Logitech F310/F710, 8BitDo gamepads, GameSir controllers) feature a physical slider switch on the chassis marked 'X' (XInput) and 'D' (DirectInput). If the switch is bumped to 'D' mode, the controller changes its USB Vendor/Product ID (VID/PID) descriptor and drops native Xbox controller driver binding in Windows, causing modern games to ignore input reports.

Diagnostic Verification:

1Open Device Manager (devmgmt.msc).

2Expand Human Interface Devices and Xbox Peripherals.

3If the controller appears as a generic 'HID-compliant game controller' instead of 'Xbox 360 Controller for Windows' or 'XInput Device', the physical mode switch is incorrectly positioned.

Step-by-Step Fix:

1Unplug Controller:

Disconnect the USB cable or wireless dongle from the PC.

2Locate Physical Mode Switch:

Find the 'X / D' slider switch on the top edge, bottom, or rear faceplate of the gamepad.

3Slide Switch to 'X' Mode:

Move the switch firmly to the X (XInput) position.

4Reconnect Controller:

Re-plug the controller into a USB 3.0/2.0 port.

Confirm Windows plays the device insertion chime and binds the xusb21.sys driver.

Prevention & Long-Term Monitoring:

Check the hardware mode switch whenever moving the controller between legacy consoles, Android devices, and modern Windows PCs.

Configuring PlayStation DualSense and DualShock 4 Drivers via DS4Windows / ViGEmBus

Solution:

Root Cause: Lack of Native Sony DualShock/DualSense HID Driver Support in Windows

Sony PlayStation controllers (DS4 and DualSense) transmit raw HID input reports over Bluetooth/USB using proprietary vendor feature reports. While modern Steam games include built-in API parsers for Sony controllers, non-Steam games and older titles rely strictly on Windows XInput APIs. Without an active translation driver, Windows recognizes the controller as a generic Bluetooth device but games cannot process its input stream.

Diagnostic Verification:

1Connect the PlayStation controller via Bluetooth.

2Open joy.cpl. If the controller appears as 'Wireless Controller' but inputs fail to register inside non-Steam games, a driver translation layer is missing.

Step-by-Step Fix:

1Install ViGEmBus Driver:

Download and install the ViGEmBus (Virtual Gameplay Input Emulator) driver package.

2Install DS4Windows:

Download the latest build of DS4Windows.

Extract and launch DS4Windows.exe.

3Create XInput Emulation Profile:

Under the Profiles tab, set target controller emulation to Xbox 360.

4Enable 'Hide DS4 Controller' / HideHide:

In DS4Windows Settings, check Hide DS4 Controller or install the HideHide driver to suppress the native Sony HID device and prevent 'double input' glitches in games.

Prevention & Long-Term Monitoring:

Keep DS4Windows and ViGEmBus drivers updated to maintain compatibility with new Windows cumulative updates.

Resolving Nintendo Switch Pro Controller and Generic Bluetooth HID Parsing

Solution:

Root Cause: Non-Standard Bluetooth HID Report Mapping on Nintendo Hardware

The Nintendo Switch Pro Controller uses encrypted/non-standard Bluetooth HID reports to transmit button state changes and analog stick calibration data. Windows pairs the controller via standard Bluetooth HID profiles, but raw axis values arrive uncalibrated or encrypted, causing games outside Steam to report frozen sticks or unmapped buttons.

Diagnostic Verification:

1Connect Switch Pro Controller via Bluetooth.

2Open joy.cpl, select the controller, and view calibration properties. Observe if analog stick indicators sit stuck in corners or fail to respond to physical movement.

Step-by-Step Fix:

1Enable Steam Switch Pro Support:

Launch Steam > Settings > Controller.

Enable Switch Pro Controller Configuration Support and Use Nintendo Button Layout.

2Use BetterJoy for Non-Steam Games:

If playing non-Steam games, download and run BetterJoy (BetterJoyForCemu).

Install the included ViGEmBus driver.

BetterJoy will parse raw Switch Bluetooth reports and map them to a virtual Xbox 360 XInput controller.

3Calibrate Analog Sticks:

Perform axis calibration inside the BetterJoy GUI or Steam Controller configuration tab.

Prevention & Long-Term Monitoring:

Connect the Switch Pro controller via USB-C cable during competitive play to minimize Bluetooth packet loss and input latency.

Configuring Per-Game Steam Input Overrides and Native Gamepad Support

Solution:

Root Cause: Steam Input Virtual Controller Interception Conflicts

Steam Input acts as an abstraction layer that intercepts raw gamepad hardware and presents a virtual Steam Controller to the game. When a game already features native support for Xbox or PlayStation controllers, Steam Input's virtual wrapper can conflict with native game engine inputs, resulting in completely dead controls or missing force feedback/vibration.

Diagnostic Verification:

1Launch game via Steam.

2Press Shift + Tab to open the Steam Overlay.

3If the overlay shows a active Steam Input configuration, Steam is overriding native game input handlers.

Step-by-Step Fix:

1Adjust Global Steam Input Settings:

Open Steam > Settings > Controller.

Ensure your specific controller type (Xbox, PlayStation, Switch, Generic) is enabled under controller driver settings.

2Configure Per-Game Override:

Right-click the problem game in your Steam Library and select Properties.

Click the Controller tab on the left menu.

Change the dropdown override from 'Use default settings' to Disable Steam Input (if the game has native support) or Enable Steam Input (if the game lacks native support for your controller).

3Relaunch Game:

Restart the game to allow the engine to bind directly to the hardware.

Prevention & Long-Term Monitoring:

Disable Steam Input for modern AAA titles that feature native DualSense/Xbox controller integration.

Passing Non-Steam Games (Epic / EA / Ubisoft) Through Steam or GlosSI

Solution:

Root Cause: Missing Input Abstraction Layers in Non-Steam Launchers

Launchers such as the Epic Games Store, EA App, Ubisoft Connect, and PC Game Pass do not include built-in input translation wrappers like Steam Input. When playing games on these platforms with non-XInput gamepads (DualShock 4, DualSense, Switch Pro, or generic DirectInput gamepads), the games receive raw unparsed HID signals and ignore input.

Diagnostic Verification:

1Launch a non-Steam game with a PS4/PS5 or DirectInput controller connected.

2Game ignores inputs entirely while Steam games work flawlessly.

Step-by-Step Fix:

1Add Non-Steam Game to Steam:

Open Steam > Games menu (top bar) > Add a Non-Steam Game to My Library...

Browse to the .exe binary of the non-Steam game and add it.

2Configure Steam Input for the Non-Steam Shortcut:

Right-click the newly added shortcut in Steam > Properties > Controller.

Select Enable Steam Input.

3Launch Game via Steam:

Always launch the non-Steam title directly from your Steam library so Steam's input injection hook loads into the game process.

4Use GlosSI for UWP / Game Pass Titles:

For Windows Store / PC Game Pass titles that restrict .exe access, download and install GlosSI (Global Steam Input) to inject XInput hooks system-wide.

Prevention & Long-Term Monitoring:

Keep GlosSI updated when upgrading Windows 11 build releases.

Eliminating Double-Input and Virtual Controller Conflicts via HideHide

Solution:

Root Cause: Dual Enumeration (Double Input) from ReWASD, DS4Windows, or x360ce

When using controller remapping software (DS4Windows, ReWASD, x360ce), the software creates a virtual Xbox 360 controller while leaving the physical physical controller active in Windows. Certain games detect *both* devices simultaneously. When a button is pressed, the game receives two input signals concurrently, causing double menu scrolls, button skips, or complete input lockups.

Diagnostic Verification:

1Open joy.cpl while your remapper software is running.

2If two distinct controllers appear listed (e.g., 'Wireless Controller' AND 'Xbox 360 Controller for Windows') and respond to physical button presses at the same time, double-input is active.

Step-by-Step Fix:

1Install Nefarius HideHide Cloaking Driver:

Download and install HideHide from the official Nefarius repository.

2Configure Device Cloaking:

Open the HideHide Configuration Client.

Under the Devices tab, locate your physical controller (e.g., Sony Interactive Entertainment Wireless Controller).

Check the lock icon next to the physical controller to hide it from all processes.

3Whitelist Remapper Application:

Under the Applications tab, add your remapper executable (DS4Windows.exe or reWASD.exe) to the whitelist so only the remapper can read physical inputs.

4Verify in joy.cpl:

Confirm that only the virtual Xbox 360 controller appears listed.

Prevention & Long-Term Monitoring:

Ensure remapper apps are configured to automatically cloak physical controllers on startup.

Fixing Shared Trigger Axis Split (Z-Axis / Z-Rotation) in Legacy DirectInput Titles

Solution:

Root Cause: DirectInput Combined Z-Axis Trigger Architecture

In DirectInput specifications, analog triggers (LT and RT) are mapped to a single combined Z-axis, where rest position is 0, pulling LT moves the axis to +100%, and pulling RT moves it to -100%. Pressing both triggers simultaneously cancels out the signal back to 0. Modern games expect independent 8-bit analog trigger axes (Z-axis and Z-rotation).

Diagnostic Verification:

1Open joy.cpl > Properties.

2Move the left and right triggers. If both triggers move a single bar slider in opposite directions, the controller is operating under a combined DirectInput axis model.

Step-by-Step Fix:

1Install x360ce (32-bit or 64-bit depending on game binary):

Copy x360ce into the game directory.

2Split Trigger Axes in x360ce GUI:

Under Controller Settings > Triggers, map Left Trigger to Axis 3 and Right Trigger to Axis 6 (or distinct analog channels recognized by your device driver).

Enable Anti-Deadzone adjustments to eliminate trigger response delays.

3Save Configuration File:

Save settings to generate x360ce.ini and launch the game.

Prevention & Long-Term Monitoring:

Use native XInput controllers for racing games and flight simulators requiring independent dual-trigger control.

Stopping Rapid KBM / Controller Input Switching and UI Flicker

Solution:

Root Cause: Micro-Movement Drift on Mouse Sensors or Virtual Input Emulation

Many modern game engines auto-switch control schemes instantly upon detecting input from mouse or keyboard devices. If an optical mouse sensor detects sub-pixel vibration, or if background software (e.g., Discord overlay, Razer Synapse, joy2key) sends continuous micro-keyboard reports, the game engine constantly toggles between Keyboard/Mouse and Gamepad modes, causing frozen inputs and flashing button prompts.

Diagnostic Verification:

1Launch the game and leave the controller idle.

2Observe if button prompt icons repeatedly flash between Xbox/PlayStation icons and PC key prompts (e.g., 'Press A' switching rapidly to 'Press E').

Step-by-Step Fix:

1Flip Mouse Upside Down / Disconnect Secondary Input Devices:

Turn off wireless mouse or flip optical mouse upside down to eliminate sensor noise.

2Increase Controller Deadzones:

Open game settings or Steam Controller settings and slightly increase stick and trigger deadzones to suppress baseline signal noise.

3Disable In-Game Overlays:

Disable Discord, GeForce Experience, and Overwolf overlays, which can send background virtual keyboard events.

4Lock Input Method in Game Settings:

In games that support it (e.g., Call of Duty, Cyberpunk 2077), explicitly lock the Input Device option to 'Gamepad' instead of 'Auto-Detect'.

Prevention & Long-Term Monitoring:

Keep optical mouse surfaces clean and maintain analog stick deadzones above 5%.

Remapping Right Stick and Button Layouts in DirectInput Controllers

Solution:

Root Cause: Non-Standard DirectInput Axis Index Mapping

Unlike XInput, which enforces strict byte offsets for thumbsticks and face buttons, DirectInput allows hardware manufacturers to assign stick axes arbitrarily. A generic controller might assign the Right Analog Stick horizontal movement to Rx (Axis 4) and vertical movement to Slider 1 (Axis 7), causing the game engine to read right-stick movement as trigger presses or camera spins.

Diagnostic Verification:

1Open joy.cpl > Properties.

2Move the Right Analog Stick. Observe if movement activates button indicators or moves trigger bars instead of the X/Y rotation point.

Step-by-Step Fix:

1Calibrate Controller in Windows:

In joy.cpl, click Settings tab > Calibrate... and follow the wizard to register stick axes.

2Override Axis Maps in Steam Input or x360ce:

In Steam Controller Configuration, select Edit Layout > Right Stick > set Output to Right Joystick.

Rebind X/Y axes manually by pushing the stick in the prompted direction during setup.

3Use Registry Axis Remapping (Advanced):

Navigate to HKCU\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput in regedit to adjust custom OEM axis mapping keys.

Prevention & Long-Term Monitoring:

Prefer XInput-compatible hardware to avoid manual registry and axis mapping for individual game releases.

Disabling Virtual Joystick Drivers (vJoy/vXbox) and Reordering Preferred Devices

Solution:

Root Cause: Primary Input Slot Occupied by Virtual HID Adapters

Legacy games and engines that support only one active controller bind exclusively to the device listed in Preferred Device position 1 in Windows DirectInput registry. If software like vJoy, Headtracking tools (TrackIR), or flight simulation throttles install virtual joystick drivers, Windows places the virtual adapter in Slot 1, ignoring your physical gamepad in Slot 2.

Diagnostic Verification:

1Press Win + R, type joy.cpl, and hit Enter.

2Click Advanced....

3Check the device listed under Preferred device.

Step-by-Step Fix:

1Set Preferred Device in joy.cpl:

In joy.cpl > Advanced..., select your physical gamepad (e.g., 'Xbox Controller') from the drop-down list and click OK.

2Disable Virtual Joystick Adapters in Device Manager:

Open Device Manager (devmgmt.msc).

Expand Human Interface Devices.

Right-click vJoy Device, vXbox Device, or extraneous virtual gamepads and select Disable device.

3Unplug Flight Sticks / Steering Wheels:

Disconnect secondary flight throttles, pedals, or racing wheels while playing gamepad-focused titles.

Prevention & Long-Term Monitoring:

Disable virtual joystick software in Device Manager when not actively flying or driving in simulators.

Removing Conflict-Prone Keyboard/Mouse Virtual HID Controller Drivers

Solution:

Root Cause: Embedded Virtual Controller Drivers in Gaming Keyboards and Mice

High-end mechanical gaming keyboards (such as Wooting analog keyboards, Razer Tartarus keypads, and Corsair gaming mice) install secondary HID-compliant game controller drivers into Windows to support analog keystrokes. Games detect these peripherals as connected Xbox gamepads on boot, locking out physical controllers.

Diagnostic Verification:

1Open joy.cpl with your physical controller disconnected.

2If one or more game controllers (e.g., 'Wooting One', 'Razer Virtual Gamepad') remain listed, your keyboard/mouse is exposing a virtual controller endpoint.

Step-by-Step Fix:

1Disable Virtual Controller Endpoint in Keyboard Software:

Open keyboard companion software (e.g., Razer Synapse, Wootility, Corsair iCUE).

Locate controller emulation settings and toggle Disable Virtual Controller / Xbox Emulation.

2Disable Virtual HID Device in Windows:

Open Device Manager (devmgmt.msc).

Expand Human Interface Devices.

Locate the virtual game controller entry associated with the keyboard/mouse hardware ID and select Disable device.

3Restart Game:

Reconnect physical controller and launch game.

Prevention & Long-Term Monitoring:

Keep analog keyboard software set to standard typing mode unless playing specific titles designed for analog key inputs.

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Clipboard History Not Working Windows 11: Sync Service Tree

Subscribe to StepDiag

Embed Guide on Your Website