Here's how it looks after disconnecting and reconnecting the mayflash: Input device name: "Nintendo POKKEN CONTROLLER" Input device ID: bus 0x3 vendor 0xf0d product 0x92 version 0x111 dev/input/event21: Microsoft Microsoft® Nano Transceiver v2.0 System Control dev/input/event20: Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control dev/input/event18: Microsoft Microsoft® Nano Transceiver v2.0 Mouse dev/input/event17: Microsoft Microsoft® Nano Transceiver v2.0 dev/input/event16: Nintendo POKKEN CONTROLLER Would be happy to do a live session on Discord, are there any times in particular that work best for you? The testing output looks fine as well, I haven't included it here because there is quite a bit of output, but it appears to be working. Input device name: "Nintendo GameCube Controller Adapter" Input device ID: bus 0x3 vendor 0x79 product 0x1846 version 0x110
dev/input/event24: Nintendo GameCube Controller Adapter dev/input/event23: Nintendo GameCube Controller Adapter dev/input/event22: Nintendo GameCube Controller Adapter
dev/input/event21: Nintendo GameCube Controller Adapter dev/input/event20: Microsoft Microsoft® Nano Transceiver v2.0 System Control dev/input/event19: Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control dev/input/event18: Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control dev/input/event17: Microsoft Microsoft® Nano Transceiver v2.0 Mouse dev/input/event16: Microsoft Microsoft® Nano Transceiver v2.0 dev/input/event15: HDA Intel PCH HDMI/DP,pcm=16 dev/input/event14: HDA Intel PCH HDMI/DP,pcm=15 dev/input/event13: HDA Intel PCH HDMI/DP,pcm=14 dev/input/event12: HDA Intel PCH HDMI/DP,pcm=13 dev/input/event11: HDA Intel PCH HDMI/DP,pcm=12 dev/input/event10: HDA Intel PCH HDMI/DP,pcm=11 dev/input/event9: HDA Intel PCH HDMI/DP,pcm=10 dev/input/event8: HDA Intel PCH HDMI/DP,pcm=9 dev/input/event7: HDA Intel PCH HDMI/DP,pcm=8 dev/input/event6: HDA Intel PCH HDMI/DP,pcm=7 dev/input/event5: HDA Intel PCH HDMI/DP,pcm=3 dev/input/event4: HDA Intel PCH Front Headphone No device specified, trying to scan all of /dev/input/event* PM me and we can work out the details if you are interested. I will happily buy one of these adapters for any Batocera developer who thinks they can fix this and they just need the actual hardware to troubleshoot it. There are other similarly-shaped GameCube controller adapters on Amazon, but I suspect they all use the same chipset as these two. This adapter also appears as "evdev/0/Nintendo GameCube Controller Adapter" so I suspect that it is the same chipset as the Y Team adapter. On Dolphin on Windows, the Y Team adapter behaves like the Mayflash adapter, showing four devices in Dolphin controller config:Īnd on the off-chance that there was a problem specific to the Y Team adapter, I bought this one on Amazon to test it as well: With a Mayflash adapter, you see four devices: If you launch Dolphin directly and open the controller config panel, under device you only see one device: However, unlike the Mayflash adapter, if you launch a GameCube game using this adapter then all four virtual controllers are controlled by the GameCube controller in port 1 on the adapter: RyKTU2b.-.Imgur.mp4 When you flip the switch on this adapter to "PC" and plug it into Batocera (latest v31 beta) you see four controllers in the upper left hand corner of EmulationStation, just like you do with the Mayflash adapter: Using this adapter, which is spaced correctly, I've encountered a rather frustrating bug: While the Mayflash adapter works OK, the ports on the Mayflash adapter are spaced differently than on an actual GameCube front panel, which means I can't build the adapter into the actual GameCube. On my continuing quest to build a Batocera-powered machine into an actual GameCube chassis, I've tried a few different GameCube controller adapters and have discovered a bug with the non-Mayflash adapters.