If you have an older or not supported game controller (gamepad, wheel, joystick, etc.), but XBox 360 controllers are supported you can use this software and enjoy gaming with your controller.
XOutput is a software that can convert DirectInput into XInput. DirectInput data is read and sent to a virtual XInput (Xbox 360 Controller) device. XInput is the new standard game controller input on windows, and DirectInput can no longer be used with Universal Windows Platform software, but with this tool you can use DirectInput devices as well.
Problem visualisation
graph TD
subgraph XInput
X1(Xbox controller 1) -->|Read hardware input| XD[Xbox controller driver - xusb22.sys]
X2(Xbox controller 2) -->|Read hardware input| XD
XD -->|Read input| XR[XInput handler - xinput1_3.dll]
end
subgraph DirectInput
D1(fa:fa-gamepad Older controller) -->|Read hardware input| D1D[Controller driver]
D2(Joystick) -->|Read hardware input| D2D[Joystick driver]
D3(Gaming wheel) -->|Read hardware input| D3D[Gaming wheel driver]
D1D -->|Read input| DR[Direct input handler - dinput8.dll]
D2D -->|Read input| DR
D3D -->|Read input| DR
end
subgraph Games
XR -->|Read XInput| NG[Newer games]
XR -->|Read XInput| CG[Compatible games]
DR -->|Read DInput| CG[Compatible games]
DR -->|Read DInput| OG[Older games]
end
Offered solution
graph TD
subgraph XInput
X1(Xbox controller 1) -->|Read hardware input| XD[Xbox controller driver - xusb22.sys]
X2(Xbox controller 2) -->|Read hardware input| XD
XD -->|Read input| XR[XInput handler - xinput1_3.dll]
end
subgraph DirectInput
D1(fa:fa-gamepad Older controller) -->|Read hardware input| D1D[Controller driver]
D2(Joystick) -->|Read hardware input| D2D[Joystick driver]
D3(Gaming wheel) -->|Read hardware input| D3D[Gaming wheel driver]
D1D -->|Read input| DR[Direct input handler - dinput8.dll]
D2D -->|Read input| DR
D3D -->|Read input| DR
end
DR -->|Read DInput| XO[XOutput]
subgraph Solution
XO -->|Control emulation| V[ViGEm]
end
V -->|Emulate controller| XD
subgraph Games
XR -->|Read XInput| NG[Newer games]
XR -->|Read XInput| CG[Compatible games]
DR -->|Read DInput| CG[Compatible games]
DR -->|Read DInput| OG[Older games]
end
If you have any questions or feature requests feel free to create Github Issue.
Any contribution is welcome, open your Pull request.
To join the discussion or just say hi in the discord channel.
This version is the stable version.
Version | State | Support |
---|---|---|
4.x | Under development (no releases yet) | Active development with new features |
3.x | Stable | Bugfixes only |
2.x | Old version (superseeded by 3.x) | Expired at Mar 7 2018 |
1.x | Old version (superseeded by 3.x) | Expired at Mar 7 2018 |
Install one of the two libraries. ViGEm (preferred) or SCPToolkit (unsupported, legacy)
a) Install VIGEm framework (recommended)
b) Install ScpToolkit and all of its dependencies described here
Install:
- DirectX
- Visual C++ Redistributable for Visual Studio 2015 32-bit
- Visual C++ Redistributable for Visual Studio 2015 64-bit
- all the drivers for your controllers
- .Net Framework 4.5.2 if you do not have Windows 10 or newer
- if you have issues, install the official XBox 360 controller drivers.
- Download the latest stable release
- Unzip to any directory
Download the application:
- Download the latest stable release
- Unzip to the same directory as before
- Delete the old
settings.json
file before starting the application and configure the controllers again
If all the requirements are installed, the software should start up without any error messages.
Input devices can be checked and configured individually. Input values can be seen in the input fields. Force feedback can be disabled for each device.
The available input devices are shown in the Game Controllers section. Choose a device and click Edit
.
On the configuration screen there are 3 blocks. The left block shows the input, the right one shows the emulated output and in the middle is where the mapping can be set. For each output axis or button, you can choose from the input axes and buttons.
- Press
Configure All
to set the mapping all at once, or pressConfigure
on each field to set them individually. - Press the button or move the axis from one end to the other.
- Check your mapping comparing the input and output blocks.
- If needed, you can apply deadzone values to axes. (more info below)
- Close the configuration window
- Save the settings using the
File->Save
menu or the button located at the bottom right of the main window. - Select
Start
on the device.
You can check if it is working in the Windows settings, or just select File->Game controllers
, that opens the Windows calibration for you. An Xbox gamepad should have appeared in the list.
- Install HidGuardian.
Affected devices and whitelist can be managed by the application, but it needs administrator priviledges.
- Enable HidGuardian initialization in the settings.
- Restart the application as administrator.
- Add device to affected devices in the input settings.
- Reconnect device or reboot PC
Add affected device manually (use this method only, if you want to hide non recognized HID devices):
- Run
regedit
and go toHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidGuardian\Parameters
- Create
multi-string
value with the nameAffectedDevices
- Open Device Manager, find your input device and open properties
- Go to details, select
Hardware ID
and copy string that looks likeHID\VID_046D&PID_C219&REV_0200
andHID\VID_046D&PID_C219
- Paste the values into
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidGuardian\Parameters
- Reconnect devices or reboot PC
Manage process whitelist manually (use this method only, if you want to use HidGuardian for other applications):
- Start XOutput (or any other application)
- Open Task Manager, find your application, then go to details.
- Remember the value of the PID column.
- Run
regedit
and go toHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidGuardian\Parameters\Whitelist
- Create subkey with the PID you found before.
--minimized
- starts the application minimized to tray
If your analogue stick isn't in perfect condition, you may have what is called a deadzone, which means that a part of the axis isn't working right, usually it's the center part, syndromes of this are: wrong center position and unwanted movement of the camera, character, etc. To solve apply a bit of deadzone in the mapping settings, how much depends on the device in question.
XOutput has a diagnostics screen. A few tests are run to check if the application is working correctly.
Image | Meaning |
---|---|
green circle with a tick | Everything is optimal. |
yellow triangle with an exclamation mark | The experience may be sub-optimal. Some functions may not work, but the application is functional. |
red circle with a minus sign | Something is not working, the application cannot function properly. Some core features may be unusable. |