Many modern games (especially those ported from consoles) only recognize , the standard used by Xbox 360 and Xbox One controllers. If you are using an older joystick, steering wheel, or a generic USB controller that uses the DirectInput standard, XOutput tricks the game into thinking you are using a genuine Xbox controller by mapping your device's buttons and axes to a virtual XInput device. Key Features of v0.11

Xoutput.v0.11 is out — a small, focused release that sharpens output formatting and fixes a few user-reported issues.

Previously, low-level device inputs were often filtered through DirectInput, causing latency or loss of specific feature sets. v0.11 introduces .

This is typically a corrupted profile file from an earlier version. Delete the config.json file inside the Xoutput folder and restart. Recreate your mappings from scratch.

fills a very specific niche: audio routing from an XInput controller’s jack . If you don’t need that feature, DS4Windows or x360ce may be simpler. But for streamers, speedrunners, or anyone using an Xbox One controller wirelessly with a headset plugged in—and wanting that audio on their PC speakers simultaneously—this is the only free, lightweight solution.

: Fixed a bug where Windows would randomly swap the player positions (e.g., changing Player 1 to Player 2) during a session.

Deploying XOutput v0.11 requires a specific configuration sequence to ensure that the virtual bus driver attaches correctly to your system. Step 1: Extract and Initialize Drivers

While XOutput.v0.11 is generally a reliable software, you may encounter some issues. Here are some common issues and troubleshooting tips:

This process was well-documented by the community. A Brazilian gaming forum post from 2016, for instance, provides a step-by-step guide for using XOutput v0.11 to play Rise of the Tomb Raider with a generic gamepad, including direct download links to the v0.11 archive. This grassroots support was vital to XOutput's success.

Setting up XOutput is straightforward. Follow these steps to get your controller working: 1. Pre-requisites

Once opened, click on to create a new virtual device. Click Configure to open the mapping screen. The configuration screen consists of three main blocks: Left: Shows your physical input (DirectInput). Right: Shows the virtual output (XInput). Middle: Where you map the buttons and axes. Map your buttons, save the profile, and click Start . Pro-Tip: Using HidHide

Run it and click . Close the window once it finishes. Map Your Controller