Emulator

Game Name?

F-ZERO Gamecube
Also SSB Brawl, but I could not obtain properties; see below

Game ID? (right click the game in the game list, properties, info tab)

GFZE01 (F-ZERO).

Attempting to open Properties for SSB Brawl caused emulator to crash with "*** Caught unhandled unknown exception; terminating".

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

b3e4932731c63b98f0617e6764cc364d

Again, couldn't obtain hash for SSB Brawl as per above. If it's really necessary, I could try in 4.0 but I'd have to reinstall, and also restore an older config. For now I'm assuming it's enough that I have one game reported, though I do cite additional behaviours specific to SSB Brawl below. Let me know if I should do the extra work to add to this report.

What's the problem? Describe what went wrong.

The GC controller axes are "stuck" when starting the game, causing continuous scrolling through menu options until the last one is reached and rendering game unusable.

What steps will reproduce the problem?

Turn on or plugin in controllers (I have three; two wireless logitech rumblepad 2 and one wired logitech dual shock).

Start any game using GC controllers.

Press buttons until start menu reached. All axes appear to be stuck (e.g. in SSB Brawl, in addition to scrolling, the screen is tilted; you can try tilting it back by moving the stick to the right, but when you release the stick it tilts again).

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

5.0-rc33 (Debian 'experimental' package 5.0~rc33+dfsg-1)
5.0 git stable, gitref 355df60abdfa
5.0 git master, gitref bd20dd39620c
4.0.2 (Debian's 'unstable' package 4.0.2+dfsg2-1+b1)

No version of 5.0 works, neither on the stable nor master branches. Only 4.0.2 works.

What are your PC specifications? (CPU, GPU, Operating System, more)

Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
NVIDIA GPU GeForce 9800 GT (G92)
Debian "sid" unstable, up to date as of date of last build/test of the issue (today)

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

I know of three different workarounds to the issue. After each test, I unplugged/replugged or turned off/on each controller.

1. Start jstest-gtk, open each controller, wiggle a single axis (any one; doesn't matter which). Initially all of the first four axes show -32767 and the moment you touch one axis, the value jumps to 0. After this, starting a GC-using game in dolphin-emu does not have stuck axes.

OR

1. Start a GC-using game, wiggle a single axis of each controller. Quit the game. Start the game again and now the problem is resolved.

OR

1. In Dolphin, open the GC configuration for each controller. Observe the dead-zone display for each analog pair of axes has no red dot. Wiggle any axis and immediately red dots appear in the center of both. Repeat, per controller. Start the game and again, the problem is resolved.