XOutput Setup Guide — How to Configure Any PC Controller (2026)

Legacy DirectInput controllers and generic USB pads are frequently ignored by modern PC titles designed exclusively for Microsoft XInput. XOutput solves this compatibility gap at the kernel driver level: it intercepts your raw DirectInput hardware signals, translates them in real time, and feeds them into the ViGEmBus driver to spawn an authentic virtual Xbox 360 controller.

Unlike older injectors such as x360ce that require pasting DLL files into individual game folders, XOutput operates as a global system-wide virtual gamepad. In this comprehensive walkthrough, you will set up clean controller mapping, tune analog stick deadzones to prevent drift, and eliminate double-input conflicts in modern games.

Step 1 — Download Verified Software and Required System Drivers

XOutput relies on two foundational system components to emulate virtual Xbox 360 hardware. Originally created as an open-source project by csutorasa on GitHub, it relies on the kernel-mode bus driver maintained by Nefarius on GitHub to interface directly with the Windows driver stack. Installing these prerequisites in the proper order prevents common setup bottlenecks such as instant launch crashes or a greyed-out Start button.

To verify that ViGEmBus has properly registered with your Windows kernel, open Device Manager (press Windows Key + R, type devmgmt.msc, and hit Enter). Expand the System devices branch and locate Virtual Gamepad Emulation Bus. If it displays with no yellow exclamation warning icons, your driver subsystem is operating normally.

Step 2 — Connect Gamepad and Verify Initial Windows Recognition

Before configuring emulation, confirm that your physical controller is detected by the Windows DirectInput subsystem:

1. Connect your gamepad to your PC via a direct USB port (avoid unpowered USB hubs during initial configuration to ensure sufficient bus power).
2. Press Windows Key + R, type joy.cpl, and press Enter to open the native Game Controllers window.
3. Verify that your physical controller appears in the list (typically labeled as “Generic USB Joystick”, “Twin USB Gamepad”, “PS3/PC Gamepad”, or the manufacturer name).
4. Select your controller and click Properties. Move the analog sticks and press each button to verify that the raw input lights illuminate in the test matrix.

If your gamepad does not show up in joy.cpl, Windows has not recognized the physical connection or missing a hardware vendor driver. Once verified in joy.cpl, extract your XOutput zip archive into a dedicated folder (e.g., C:\Tools\XOutput\) and launch XOutput.exe as Administrator.

Step 3 — Create and Map Your Virtual Xbox 360 Controller

When XOutput launches, your physical hardware will be listed under the Game Controllers tab. Follow these steps to map each control to its Xbox 360 counterpart:

1. Click the Add controller button. A new entry labeled Controller 1 will appear with an Edit button.
2. Click Edit next to Controller 1. This opens the mapping matrix window where you pair DirectInput signals to the standard Xbox 360 layout.
3. Click Configure All to start the automated sequential mapping wizard, or click Configure next to individual buttons.
4. When prompted on screen, press the physical button or tilt the analog stick in the indicated direction.

DirectInput to Xbox 360 Target Input Translation Reference

Use this standardized reference table if you are manually mapping buttons or configuring non-standard controllers:

Step 4 — Calibrate Analog Sticks and Tune Deadzones to Eliminate Drift

Generic controllers and worn potentiometer joysticks frequently suffer from input drift or uncentered resting values. Left uncalibrated, this causes unintended character creeping, spinning third-person cameras, or erratic menu scrolling.

XOutput provides real-time per-axis deadzone compensation directly in the mapping window:

• Calibrate Rest Position: In the mapping configuration window, observe the live visual position of your analog sticks while your hands are off the controller. The indicator should rest precisely at 0.00.
• Set Deadzone Percentage: Under each analog axis, adjust the Deadzone slider:
  • 5% to 8% (Recommended for most controllers): Eliminates micro-jitters without sacrificing fine aim precision in shooters or steering granularity in racing games.
  • 10% to 15% (For loose or worn sticks): Necessary for older controllers where sticks do not reliably return to center.
• Invert Axes if Necessary: If pushing forward makes your in-game character move backward or look at the floor, check the Invert checkbox on the Y-Axis.
• Click Save at the bottom of the window to store your calibration profile.

Step 5 — Start Emulation and Verify in Windows Game Controllers

With your buttons mapped and sticks calibrated, you can activate the virtual controller:

1. In the main XOutput dashboard, locate Controller 1 and click the green Start button.
2. A Windows notification sound will chime, indicating new hardware has been connected.
3. Open joy.cpl again. You will now see two active devices:
   • Your original hardware (e.g., “Generic USB Controller”);
   • A newly created “Controller (XBOX 360 For Windows)”.
4. Select the virtual Xbox 360 controller, click Properties, and test all inputs. When you move your physical stick, the virtual Xbox controller will respond with zero perceptible latency.

Step 6 — Fix Double Input and Ghost Controllers with HidHide

Many modern PC games — notably EA Sports FC (FIFA), Rocket League, Forza Horizon, and Dark Souls — query both DirectInput and XInput APIs simultaneously.

When XOutput is active, these games detect both your original physical gamepad and the virtual Xbox 360 gamepad at the same time. This triggers the infamous “Double Input” bug, where every button press registers twice (e.g., skipping menu items, jumping two steps, or assigning you to Player 2).

The standard, official solution is Nefarius HidHide, an open-source kernel filter driver hosted on GitHub that conceals your physical gamepad from all applications while whitelisting XOutput:

1. Download and install the driver following our step-by-step HidHide Double Input Setup Guide, then reboot your computer if prompted.
2. Open HidHide Configuration Client from your Start menu.
3. Under the Applications tab, click the + button, browse to your XOutput directory, and select XOutput.exe to add it to the whitelist.
4. Under the Devices tab, locate your physical DirectInput gamepad, check the box next to it, and check “Enable device hiding” at the bottom.

Now, only XOutput can read your physical hardware. Every game on your PC will only see the clean virtual Xbox 360 controller, permanently solving double inputs.

Troubleshooting Common XOutput Setup Errors and Boundary Cases

If you encounter unexpected behavior during setup, check these verified solutions for common boundary issues:

Common Beginner Setup Mistakes & Quick Fixes

Most setup failures stem from a few common oversights during initial unzipping and driver configuration. Review this quick reference matrix before diving into advanced diagnostics:

Issue 1 — “Start” Button Is Greyed Out and Unclickable

Root Cause: XOutput cannot establish communication with the ViGEmBus driver. Either the driver is not installed, or the background Windows service (ViGEmBus) has stopped.
Fix: Close XOutput, run ViGEmBusSetup_x64.msi to complete or repair the installation, open services.msc, verify that the Virtual Gamepad Emulation Bus service is running, and restart XOutput. See our dedicated XOutput Not Working Guide for in-depth driver diagnostics.

Issue 2 — XOutput Crashes Instantly Upon Launching

Root Cause: Missing .NET 7.0 Desktop Runtime x64. Windows Event Viewer will report a CLR20r3 or KERNELBASE.dll fault.
Fix: Download and install the official Microsoft .NET 7.0 Desktop Runtime specifically for x64 architectures. Note that the x86 (32-bit) runtime will not resolve the dependency on 64-bit Windows.

Issue 3 — Triggers Act as On/Off Digital Buttons Instead of Analog Axes

Root Cause: Many older DirectInput gamepads (and PS2-to-USB adapters) do not possess true analog pressure potentiometers under L2/R2, transmitting them as simple digital switches.
Fix: In XOutput’s button configuration window, map LT and RT under the Buttons category rather than the Axes category. XOutput will transmit a digital 0% or 100% signal, allowing triggers to operate cleanly in all modern PC games.

Issue 4 — Steam Controller Conflicts and Overlapping Mappings

Root Cause: Steam Input can automatically hook onto both the raw DirectInput controller and the virtual Xbox 360 controller simultaneously.
Fix: Open Steam > Settings > Controller. Under “External Gamepad Settings”, ensure “Enable Steam Input for Xbox controllers” is checked, while disabling generic controller support to allow XOutput full passthrough.

Frequently Asked Questions About XOutput Configuration