=== Environment ===
OS: Windows 11, build 10.0.26100.9818 (also observed on 26300), x64
reWASD: 9.4.1.11268 (latest at the time of writing)
Controller: Betop BTP-KP70A wireless dongle, XInput mode (USB\VID_20BC&PID_5130)
Physical device state: OK, problem code 0
Affected game: ArcheAge Chronicles, Steam AppID 3218230, build 26609794
=== Steps to reproduce ===
1. Connect the controller in XInput mode. It enumerates as one "Xbox 360 Controller for Windows".
2. In reWASD, select the controller slot and associate Keyboard (and Mouse) with the gamepad, i.e. use the combined / combo device mode, then click Apply.
3. Poll XInput with XInputGetState(0..3) (script at the end), or launch a game that only reads XInput user index 0.
=== Observed behaviour ===
Two software-enumerated devices appear in Device Manager:
USB\VID_045E&PID_028E\1&79F5D87&1&00000001 parent = ROOT\SYSTEM\0001
USB\VID_045E&PID_028E\1&79F5D87&1&00000002 parent = ROOT\SYSTEM\0001
Both are named "Xbox 360 Controller for Windows". Polling XInput gives:
slot 0 : connected, dwPacketNumber = 2 <-- never changes, device is idle
slot 1 : connected, dwPacketNumber = 2 <-- idle in one run
slot 2 : connected, dwPacketNumber 69523 -> 72647 -> ... <-- increments with real input
So the active virtual controller lands on user index 1 or 2, while user index 0 is occupied by a second, permanently idle virtual controller. The physical controller correctly disappears from XInput while reWASD is running (expected hiding behaviour).
Result in the affected game: no controller input at all, because the game only polls XInputGetState(0).
=== Expected behaviour ===
Either:
1. the combo mode should expose one virtual gamepad, or
2. the active virtual gamepad should claim the lowest free XInput user index (0), instead of an idle extra device taking it.
=== Impact / scope ===
- Games that scan all four XInput slots work fine: My Time at Sandrock and Crimson Desert both respond normally with the same combo configuration.
- Only games that hard-read user index 0 are broken. ArcheAge Chronicles is confirmed; its failure started right after a game update on 2026-11-16 (build 26609794).
- Verifying that it is the virtual-device arrangement and not the hardware: fully stopping reWASD (Engine, jlserv, reWASDUI), removing the two virtual controllers and re-plugging the receiver makes the game work again - the physical controller then occupies XInput slot 0.
=== Requests ===
1. Please check why the combo device creates two virtual Xbox 360 controllers, and why the active one does not take the lowest free XInput user index.
2. If that is by design, please add an option / behaviour to force the active virtual controller to XInput user index 0.
3. Confirm whether this is a known regression after recent Windows 11 driver-stack updates (the Xbox/XUSB/HID input drivers were refreshed system-wide on 2026-11-13 on this machine).
=== Minimal verification script (PowerShell 5.1, no admin needed) ===
$code = @'
using System;
using System.Runtime.InteropServices;
[StructLayout(LayoutKind.Sequential)] public struct XS {
public uint p; public short b; public byte lt; public byte rt;
public short lx; public short ly; public short rx; public short ry; }
public static class XI {
[DllImport("xinput1_4.dll")] public static extern int XInputGetState(int i, ref XS s); }
'@
Add-Type -TypeDefinition $code
1..2 | ForEach-Object {
for ($i = 0; $i -lt 4; $i++) {
$s = New-Object XS
$r = [XI]::XInputGetState($i, [ref]$s)
if ($r -eq 0) { "slot $i : connected, packet=$($s.p), Btn=0x$('{0:X}' -f $s.b)" }
else { "slot $i : not connected" }
}
Start-Sleep -Seconds 2
}
Run it while pressing buttons on the controller: the slot whose packet value increases is the active one. In the failing configuration that is never slot 0.?
