feat(windows): add user-mode Xbox 360 XInput support - #139
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #139 +/- ##
==========================================
+ Coverage 73.56% 73.94% +0.38%
==========================================
Files 34 34
Lines 9317 9470 +153
Branches 3480 3536 +56
==========================================
+ Hits 6854 7003 +149
- Misses 1799 2136 +337
+ Partials 664 331 -333
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 10 files with indirect coverage changes Continue to review full report in Codecov by Harness.
|
ReenigneArcher
force-pushed
the
fix/xbox360
branch
2 times, most recently
from
September 12, 2026 00:39
834f2aa to
457b3f5
Compare
ReenigneArcher
changed the title
Create broker-owned software devices backed by a dedicated UMDF2 XUSB companion while retaining a correlated VHF HID child for DirectInput compatibility. Route token-authenticated native XInput state and rumble through the Windows backend, extend the driver package and wire protocols, and add installed-consumer coverage and documentation for the XUSB compatibility boundary.
Use ROOT-style PnP hardware IDs for SwDevice-created Xbox 360 instances so the INF selects the companion driver and publishes XUSB. Include Configuration Manager status in interface startup failures.
Use bare hardware IDs for SwDevice-created Xbox 360 companions and add matching INF model entries so PnP installs the UMDF driver instead of leaving a Code 1 devnode. Preserve the ROOT provisioning alias and align installed-driver validation and documentation with the software-device identity.
Match the default first-reported Xbox 360 VID/PID identity in both Windows model sections so PnP selects the UMDF package at rank zero instead of relying on the lower-ranked generic fallback. Exercise the x360 profile during installed-driver smoke validation and document the ranked default and custom-identity fallback behavior.
Skip the HID child assertion for the native Xbox 360 profile and verify its software-device XUSB companion directly. This allows installed-package smoke testing to exercise the intended Windows device path.
Select server-specific INF models that omit the client-only xinputhid classifier while preserving the XUSB interface and VHF child. Let WDF tear down device-owned queues so cleanup cannot terminate the UMDF host on a failed synchronous purge.
ReenigneArcher
force-pushed
the
fix/xbox360
branch
from
September 12, 2026 03:27
09ef5e5 to
ca11977
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Create broker-owned Xbox 360 software devices backed by a dedicated UMDF2
XUSB companion, with a correlated VHF child for HID and DirectInput
compatibility.
Route token-authenticated XUSB state and rumble through the Windows backend.
Extend the INF and driver package for client and server Windows SKUs, harden
device teardown, and add installed-driver lifecycle coverage.
Advance the private broker and control protocols to version 5 for the new
per-device transport. The public C++ API and existing xbox_360 profile remain
unchanged, but applications must use a matching library, broker, and driver
package.
Screenshot
Issues Fixed or Closed
Roadmap Issues
Type of Change
Checklist
AI Usage
See our AI usage policy.