Black-Seraph
commented
1 week ago This is most likely linked to the way Duo jails input devices.
There's two parts to it, one that uses a timing-glitch in ViGEmBus to jail virtual devices into the remote sessions they belong into by setting the session ID device attribute right as the device spawns, which works fairly well, and a second piece that that does the same for console session devices (aka. physical devices), which is much less reliable due to the fact that the arrival of said devices can't be predicted.
If I had to explain it in layman's terms...
- Duo knows when a new virtual gamepad device is going to spawn because its preceeded by Moonlight sending at least one gamepad input event which allows us to employ the ViGEmBus timing-glitch in combination with the session ID device attribute to essentially jail the input device into the session it should be in rather than being host-global
- Physical devices on the other hand have no plug-in precursor event Duo could attach to to set its session ID device attribute before the device initializes fully, which means we have no choice but to operate a polling loop and hope for the best, which, often, isn't enough to get the device configured properly in time causing the issue you describe
The proper solution to all of this would be to implement a HID filter driver, but I lack the required access to Microsoft's hardware developer dashboard to double-sign my own drivers, which means I can't actually deploy such a driver to regular users without first forcing them into test-signing mode and letting the driver run unsigned.
But running unsigned drivers isn't an option either, as that will trigger almost all Anti-Cheat systems out there.
Hello, i am using Patreon DUO version 1.4.4. When my XBOX controller is connected to the host and DUO starts then instantly my XBOX controller stops working. It is still showing up as a connected. I`ve tried from Troubleshooting guide but nothings works. Any ideas?