steam-for-linux icon indicating copy to clipboard operation
steam-for-linux copied to clipboard

Original Gamecube controller input issues

Open VirtualScallop opened this issue 3 weeks ago • 0 comments

System Information:

  • Steam client version: 1763795278
  • Distribution: Linux Mint 22.2 (Cinnamon 6.4.8)
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: (I'm a little unclear on the extent of what's being requested; will offer what's needed as clarified)
  • GPU: Nvidia GeForce RTX 3070

Please describe your issue in as much detail as possible:

Amongst things I've been setting up on Linux, I've been wanting to see if I can get my Gamecube controller to work with Steam. After some fiddling around, I was able to get Steam to properly recognize the controller...

However, when I went to actually use the controller, it's effectively nonoperational. Any input it tries to send cannot be held. If you hold the A button, it parses it as a flurry of small A presses. If you press a direction on an analogue stick, it rapidly flicks between said direction, and neutral. Every input on the device behaves like this.

Additionally, when viewing through device input tests, it shows the analogue triggers as having rapidly fluctuating values, as well as minor jitters on the analogue sticks. Were it just this issue, I would write it off as a deadzone problem... but in conjunction with everything else...

This is an original wired Gamecube controller. Not the 2025 NSO one, or a third party variant. If it's a bootleg, I wouldn't know. It's run through a 3rd party Mayflash adapter.

I do not think the controller or adapter is at fault, as there are other use cases it's been through:

  • I was previously a Windows 10 user up until a couple months ago. It worked with Steam as expected there.
  • The controller still works as expected in Dolphin, albeit with the adapter set to Wii U mode.

Nor do I think this is an issue with Steam reading my controllers in general. I've used a Switch Pro Controller and 2015 Steam Controller just fine... on Windows 10, and on Linux Mint. I've also tried this with and without my Steam Pro Controller connected at the same time. It makes no difference.

Steps for reproducing this issue:

  1. Have Gamecube controller plugged into a Mayflash adapter, and have that plugged into USB
  2. Set mode to PC
  3. Enable input for generic controllers (Though the same result is achieved with this toggled off)
  4. Go to controller settings in Steam
  5. Amongst the listed Mayflash instances, discover the one that's offering input
  6. Go into input setup, and proceed as requested
  7. Steam should now recognize the controller as Gamecube one (Albeit with a graphic of the modern NSO one) (Additionally, duplicate Mayflash instances should be gone)
  8. Try to play a game, or test device inputs... notice that they're being incorrectly read

VirtualScallop avatar Dec 02 '25 17:12 VirtualScallop