You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My CyberPower uninterruptible power supply, connected to my PC by USB and managed with HID interface, is showing up as 5-axis controller 1 when I press a button on my gamepad. My Xbox Series gamepad is connected by USB and shows up as controller 2. My Xbox apparently attaches fake "contoller 1" to the running session and ignores actual controller 2.
To Reproduce
Boot the system with UPS attached by USB.
Plug in Xbox controller by USB.
Launch Greenlight
Go to Settings, Input
Controllers Detected is empty
Press button on gamepad
Expected behavior
Should ignore generic HID devices and only map actual game controllers.
An alternative would be some UI to disable or manually map controllers to numbers.
Environment
- OS: Windows 10 10.0.19045 Build 19045
- Device: PC
- Greenlight version: 2.3.1
Anything else?
New issue
I confirm that this is a new issue and not a duplicate
The text was updated successfully, but these errors were encountered:
Workaround: While Greenlight is running, disable "CyberPower Battery Backup" in Device Manager. Disconnect, reconnect controller. Press button on controller, re-detects as controller 1. Re-enable UPS in Device manager; now that is detected as controller 2.
Describe the bug
My CyberPower uninterruptible power supply, connected to my PC by USB and managed with HID interface, is showing up as 5-axis controller 1 when I press a button on my gamepad. My Xbox Series gamepad is connected by USB and shows up as controller 2. My Xbox apparently attaches fake "contoller 1" to the running session and ignores actual controller 2.
To Reproduce
Expected behavior
Should ignore generic HID devices and only map actual game controllers.
An alternative would be some UI to disable or manually map controllers to numbers.
Environment
Anything else?
New issue
The text was updated successfully, but these errors were encountered: