Cyborg Thumbstick Issues

[fauxjake]

Hi All, I've been having an issue with my Cyborg gamepad that I purchased back in March of '23.

Suddenly, the thumbstick seems to be getting 'stuck' (as in the input it sends, not mechanically) in the upper-left position (W+A if you have the default WASD bindings). When this happens (frequently, around every minute or so) the software stops detecting the gamepad. If I unplug / replug in the gamepad when this happens, it can be seen that the thumbstick is stuck in the top-left.

Interestingly, the gamepad continues to function otherwise (albeit with a stuck thumbstick input), and sometimes eventually stops the stuck input (if it does, the software still doesn't pick up on the gamepad anymore).

I've tried a few things such as changing cables / USB ports, updating the software / firmware to latest, re-calibrating the thumbstick, and testing with both on-board profiles and software-handled profiles (restarting the computer itself). No luck.

I'm attaching the logs (with thumbstick logging enabled). Anyone have any ideas? Is my gamepad just too old and getting toasted?

 

[Im this guy]

Hi All, I've been having an issue with my Cyborg gamepad that I purchased back in March of '23.

Suddenly, the thumbstick seems to be getting 'stuck' (as in the input it sends, not mechanically) in the upper-left position (W+A if you have the default WASD bindings). When this happens (frequently, around every minute or so) the software stops detecting the gamepad. If I unplug / replug in the gamepad when this happens, it can be seen that the thumbstick is stuck in the top-left.

Interestingly, the gamepad continues to function otherwise (albeit with a stuck thumbstick input), and sometimes eventually stops the stuck input (if it does, the software still doesn't pick up on the gamepad anymore).

I've tried a few things such as changing cables / USB ports, updating the software / firmware to latest, re-calibrating the thumbstick, and testing with both on-board profiles and software-handled profiles (restarting the computer itself). No luck.

I'm attaching the logs (with thumbstick logging enabled). Anyone have any ideas? Is my gamepad just too old and getting toasted?

Sounds more like a disconnect rather than thumbstick issue.
Try plugging directly in the motherboard usb port, if you haven't already.
See if the issue occurs whilst the thumbstick is on idle, without touching it.
Have you changed anything in your setup ?

Screenshot the joy.cpl controller menu with azeron connected.

 

[fauxjake]

Update after some more troubleshooting last night, and I agree it is acting like a disconnect issue, though I think it might be a driver or software issue (probably windows 11 ).

To answer your q's:
It does not appear happen while idle, and it does not seem to occur when not using the thumbstick but pressing buttons. I switched to plugging into the motherboard directly as part of troubleshooting. The only thing I can think of that has changed is I re-installed Destiny2 again, along with it's anti-cheat. It was derping-around in Destiny2 that the problem first occurred - though I immediately tested a different game with no Battle-eye (warframe) and had the same behavior occur in around the same timeframe.

I proceeded to test with https://hardwaretester.com/gamepad based on an older thread I found in these forums, but the azeron only showed up there after I also plugged in and used an Xbox controller. It seemed like it wasn't recognized until HTML5 gamepad API also saw the xbox controller. It showed up as various "players" during my testing.

I ended up resetting everything I could on the gamepad through the azeron application, then removing the gamepad through window 11's Bluetooth / Devices settings and letting window's re-add it. After doing this, I was able to use the gamepad with onboard profiles without experiencing the disconnect issue for around an hour before I had to turn in for the night.

The attached screenshots show joy.cpl this morning. There are 4 direct input devices, two of which show just buttons, and two of which include joystick calibration options when properties are opened. Does that look right to you?

No inputs highlight in any of the properties windows when actuating buttons or the thumbstick on the gamepad with that window open - not sure if that's a thing or not, been a long time since I had to calibrate a joystick on windows lol.

 

[Im this guy]

Update after some more troubleshooting last night, and I agree it is acting like a disconnect issue, though I think it might be a driver or software issue (probably windows 11 ).

To answer your q's:
It does not appear happen while idle, and it does not seem to occur when not using the thumbstick but pressing buttons. I switched to plugging into the motherboard directly as part of troubleshooting. The only thing I can think of that has changed is I re-installed Destiny2 again, along with it's anti-cheat. It was derping-around in Destiny2 that the problem first occurred - though I immediately tested a different game with no Battle-eye (warframe) and had the same behavior occur in around the same timeframe.

I proceeded to test with https://hardwaretester.com/gamepad based on an older thread I found in these forums, but the azeron only showed up there after I also plugged in and used an Xbox controller. It seemed like it wasn't recognized until HTML5 gamepad API also saw the xbox controller. It showed up as various "players" during my testing.

I ended up resetting everything I could on the gamepad through the azeron application, then removing the gamepad through window 11's Bluetooth / Devices settings and letting window's re-add it. After doing this, I was able to use the gamepad with onboard profiles without experiencing the disconnect issue for around an hour before I had to turn in for the night.

The attached screenshots show joy.cpl this morning. There are 4 direct input devices, two of which show just buttons, and two of which include joystick calibration options when properties are opened. Does that look right to you?

No inputs highlight in any of the properties windows when actuating buttons or the thumbstick on the gamepad with that window open - not sure if that's a thing or not, been a long time since I had to calibrate a joystick on windows lol.

It should show only two inputs in joy.cpl, that might be the problem
email us on info@azeron.eu, include the link from the forum

 

[fauxjake]

Sent - thank you for your troubleshooting help!