Emulator

I’m sorry, that’s a bad title: “not” should read “no longer”.

Also, note that rumble does work for, say, the Mayflash 4-port Wii U adapter (Mayflash W012). It broke specifically for the 2-port adapter after 5.0-5522.

This is a big deal for my family for some games, because the 4-port adapter doesn’t allow the remapping of controls in “GameCube Adapter for Wii U” mode, whereas the 2-port adapter does allow it in “Standard Controller” mode—and for accessibility reasons we use the standard DirectInput controller mode to play with remapped controls on a number of titles.

Here’s one on eBay:

https://www.ebay.com/itm/Mayflash-GameCube-Controller-Adapter-for-PC-2-Ports/273554122539

It's on Amazon.de as it was when I got the 4-port one couple of years ago.

https://www.amazon.de/MAYFLASH-Gamecube-Controller-Adapter-Zwei-Ports-Schwarz/dp/B00YH2TGYS/ref=sr_1_6

That one on Amazon.de is also on U.S. eBay and Amazon, but it’s not the older version I’m experiencing this problem with; it’s one with a Wii U/PC switch in the back (such as is in the back of the newer 4-port ones that are working fine).

I’m not sure whether that makes a difference, but I’m inclined to think it might. This issue seems to be affecting older DirectInput adapters specifically.

huggin, that eBay listing has sold and I'm not finding any more listings. :/

That bisect makes me suspicious. 5.0-5522 is just changes to expression handling, which makes me think the issue is not the device itself, but a configuration parsing issue. Could you provide your controller config file?

Also for what it's worth, the Mayflash 4-port adapter has a switch for Wii U and PC modes, which will allow you to use it like a normal DirectInput controller.

Okay, I set the newer (4-port) Mayflash controller to DInput (PC) mode, and it is experiencing the same problem: rumble works up through 5.0-5509 but stops from 5.0-5522 on.

So @Billiard26, I guess it doesn’t much matter which Mayflash adapter you get so long as you can run it in DInput mode?

Also, as a preliminary check of the configuration file issue myself, I cleared all DInput mappings and mapped them from scratch using the newest build of Dolphin. Rumble didn’t work.

I then dropped build 5509 directly onto that installation and tried again without making any other changes (using the config file generated by from-scratch mapping in the newest build of Dolphin). Rumble worked.

When I dropped 5522 directly onto the 5509 installation, rumble broke again.

Is it possible that changes to the expression handling failed to update some routine that is called when Dolphin sends rumble instructions to the controller?

Regardless, thank you all those who are even taking a look at this issue. For now my family can just stick with 5509 (we have an accessibility issue that requires controller remapping), but it would be great, for long-term compatibility and a million other obvious reasons, to be able to stay current with the update track.

So I’m very grateful for anything you can do.

Should I get

https://www.amazon.com/dp/B00RSXRLUE/ref=cm_sw_r_cp_apa_i_gjPdCbP0GT5B5

or

https://www.amazon.com/dp/B00YH2TGYS/ref=cm_sw_r_cp_apa_i_qkPdCbE3M15G2

?

Probably either would work, but I was able to replicate it just now using B00RSXRLUE (the 4-port).

I don’t want people to be out money on my issue, though. I would be happy to reimburse you for the expense of purchasing an adapter you yourself don’t even need—let me know and if so I can give you an e-mail address you can contact me at so I can PayPal you enough to cover the purchase of the adapter.

You would need a GameCube controller as well, though. I’m assuming you already have one? If so, then do you already have a different adapter that works?

Anyway, let me know and I’ll be happy to pitch in.

For reference, using the 4-port adapter on Windows requires installation of Mayflash’s driver (http://www.mayflash.com/File.asp?Id=89) and possibly (I have) updating to the latest (years old now) firmware (http://www.mayflash.com/File.asp?Id=106).

To use the adapter in DInput mode, the switch in the back should be set to “PC”.

The 4-port adapter is on order to fix this. (ETA Dec 27) :)

Your PR 7640 (preview build linked by you in https://bugs.dolphin-emu.org/issues/10736) fixes this problem for me entirely.

From everyone at my house (and on behalf of all the other Dolphin users experiencing one of these nagging rumble-related issues that have persisted for so long), thank you for devoting your time and energy (and money) to overhauling Dolphin’s rumble capabilities. I’m very, very grateful. I owe you one, man.

Cool—I didn’t know things worked like that.

Thanks, Dolphin Foundation!