XOutput v0.11 is available immediately for Windows 10/11.
"Xoutput" typically refers to the software, a Windows application that converts DirectInput (older controllers like PS3 or generic PC gamepads) into XInput (Xbox 360 controller emulation). This allows older or non-Xbox controllers to work with modern games. The specific version
is a legacy release of this software. Key content and features associated with this version include: Controller Emulation
: Its primary function is mapping DirectInput buttons and axes to a virtual Xbox 360 controller. ViGEm Integration
: Later versions transitioned to the ViGEm framework, but v0.11-era releases often relied on the older ScpToolkit or specific virtual bus drivers for emulation. User Interface
: A simple GUI for mapping buttons, setting deadzones, and calibrating analog sticks. Portability
: It is generally distributed as a portable executable, requiring no formal installation other than the necessary drivers (like the DirectX runtime and Xbox 360 controller drivers). Khronos Registry Comparison with Modern Versions
While v0.11 was functional, modern users typically use version or higher, which offers: Automatic controller detection.
Support for specialized hardware like flight sticks or steering wheels. Enhanced stability on Windows 10 and 11. Xoutput.v0.11
a specific controller with Xoutput, or are you looking for a download link for this particular version? Specification - The OpenVX - Khronos Registry
Depending on whether you're a developer sharing this version or a gamer recommending it to the community, here are a few options for a post about XOutput v0.11 Option 1: The "Problem Solver" (Best for Reddit/Discord)
Tired of your old controller not working with modern PC games? 🎮
If you’re struggling to get your DirectInput controllers (PS2 adapters, older Joysticks, or generic gamepads) recognized by games that only support Xbox controllers, XOutput v0.11 is a lifesaver. What it does:
It wraps your DirectInput device into a virtual XInput (Xbox 360) controller. Why v0.11?:
This version is a classic, stable build for those who need a lightweight solution without the bloat of newer wrappers. Quick Tip:
Make sure you have the ScpDriver installed first so Windows can "see" the virtual Xbox device!
Anyone else still using this for their legacy setups? Let’s hear your mapping tips below. 👇 XOutput v0
Option 2: The Technical/Dev Update (Best for GitHub/Tech Blogs)
Release Notes: XOutput v0.11 – Stability & Mapping Improvements We’ve just pushed
of XOutput! This release focuses on refining the input wrapper to provide a smoother experience for legacy controller users. Key Updates in v0.11: Improved Axis Mapping:
Fixed issues where "ghost" inputs caused infinite scrolling in game menus. Vibration Support: Enhanced feedback for compatible DirectInput devices. UI Tweaks:
Made the configuration gear icon more accessible for per-button mapping. Check out the latest build on and stop letting your old hardware collect dust. Option 3: The Short & Punchy (Best for X/Twitter) Old controller? New games? No problem. 🕹️💻 XOutput v0.11
is the bridge between your legacy DirectInput gamepads and XInput-only titles. Simple setup, low latency, and zero cost. Install ScpDriver Map your buttons in XOutput Hit "Start" and play. #PCGaming #RetroGaming #XOutput #GamingSetup Key Reminders for your Post: Installation: Remind users they often need the for the virtual controller to function. Mention that mapping the
(sticks) is the most important part to avoid "infinite scrolling" bugs.
Highlight that it’s specifically for making Windows think a "normal" gamepad is an Xbox 360 controller. Are you looking to write this for a specific platform (like a technical README vs. a casual social media post)? "Xoutput" typically refers to the software, a Windows
Xoutput v0.11 is the latest stable release of the open-source tool that emulates an Xbox 360 controller while giving you granular control over audio output and rumble. If you’ve ever wanted to use a non-Xbox controller (e.g., Nintendo Switch Pro, PlayStation, or generic USB gamepads) with games that only recognize XInput—but also need to route audio from the controller’s headphone jack to a separate device—this is your solution.
Version 0.11 replaces linear mapping with a fully customizable Bezier Curve Editor for all analog axes (Triggers and Sticks).
When switching between controller profiles (e.g., switching from a "Driving" profile to a "FPS" profile on the fly), v0.11 now interpolates the change.
To appreciate version 0.11, let's compare it to other popular solutions:
| Feature | Xoutput.v0.11 | x360ce (64-bit) | Steam Input | DS4Windows | | :--- | :--- | :--- | :--- | :--- | | System-wide | Yes | No (per-game DLL) | No (requires Steam) | Yes (for Sony only) | | Non-Steam Games | Perfect | Good | Requires adding as non-Steam | Limited | | Switch Pro Support | Full (v0.11) | Poor/Laggy | Good | None | | Rumble Mapping | Advanced | Basic | Strong | Moderate | | Latency | Very Low | Moderate | Low (only in Steam) | Moderate |
The Verdict: If you only play games through Steam, use Steam Input. But if you play Game Pass titles, Epic Games Store games, or stand-alone emulators, Xoutput.v0.11 is the superior choice because it works globally without launcher interference.
âś… You use a non-Xbox controller in a game that only supports Xbox controllers (e.g., older titles, some emulators)
✅ You want game audio from your controller’s headphone jack to go to your PC speakers or wireless headset instead
✅ You need to split audio – e.g., game sounds over speakers, voice chat over controller headset
âś… You want to test controller vibration without launching a game