I am not sure why, but after taking time holding random button combos, holding the start + select (or + with -) it reconnected as an xinput gamepad and works now for me. Previously it always said it was a ps4 gamepad. Hope this helps you.
I am not sure why, but after taking time holding random button combos, holding the start + select (or + with -) it reconnected as an xinput gamepad and works now for me. Previously it always said it was a ps4 gamepad. Hope this helps you.
You can press the two menu button that cycles through modes between PS , Nintendo and Xbox but xinput mode does the above.
What does work is a hidden button combo , holding m + logo button (on/off) while in xinput will change the PID and it works but its not persistent.
Wanted to share a finding that might help others hitting this issue.
On Windows, the documented shortcut to switch the Cyclone 2 into Xinput mode is Game + X. On Linux, that combo doesn't behave the same way — instead, it seems to fall into whatever default mode-cycling behavior the controller has.
What actually works reliably for me on Linux is:
Hold Select + Start for ~1 second or 2, it blinks and then this cycles the controller through Xinput → Nintendo → PS4 (repeat to cycle back to Xinput).
the setting persists after turning off and on, it is still on xinput.
Environment: Arch Linux, dongle connection. Might be worth others confirming whether Select+Start works the same way on their distro/setup, since Game+X clearly isn't being read correctly on Linux for some reason.
Nothing extracted yet.
Your system information
*Steam Logs: attached
Please describe your issue in as much detail as possible:
Expected Behavior:
When connecting a GameSir Cyclone 2 wireless controller in its native
steam-logs.tar.gz
mode (Home LED glows Green) via the wireless USB dongle , the Steam Client should recognize the device as a native Xbox 360 or Xbox One Controller. Steam Input should seamlessly map the standard Microsoft layout and pass native Xbox A/B/X/Y glyph prompts to games.
Actual Behavior:
The Steam Client completely bypasses the underlying system kernel configuration (where the
xpadorxonedriver handles the inputs perfectly) and misidentifies the controller's hardware ID as a "Generic Gamepad."Hardware ID (
lsusb):Bus 007 Device 004: ID 3537:100b Xbox 360 Controller for Windows
Steps for reproducing this issue:
####Extra information
This works on windows with no issues.
The other Controller modes for PlayStation and Nintendo work.
Disabling steam input allows Games to work with the Controller.