Skip to content

8Bitdo_M30_24G doesn't seem to work correctly in udev or sdl2 modes #1291

@armyofda12mnkeys

Description

@armyofda12mnkeys

Im also having issues with 8bitdo's M30 2.4g wireless controller too.
It acts very strange.
1st i try when under "udev" drivers it recognizes as "Sega Mini MD 6B Controller"...

i remap in the Settings->Input->RetroPadBinds->Port1Controls to what people say they should be in the forums. (mapping below)
But they seem wrong. I try to fix them in-game and they still seem wrong. (some weird issue occurs where im controller both Player1 and 2 at the same time (in the SegaGenesis X-men game where you select your player).

Image

and here is how it acts:
https://youtu.be/njGXJCqz2ZI
and here is another weird way how it acts:
https://youtu.be/bjS6bmPVA9s

I am willing to do whatever you'd like for me to try and fix this ( @hizzlekizzle maybe was aware of my issue from a reddit post i made a few days ago).
He said:

"So, it seems the actual 6B controller and the M30 report the same IDs but have different layouts:

# The controller presents the same IDs as
That's probably what's happening here.
You might try changing your gamepad driver to SDL2 and see if it picks it up any better. You might also try different pairing modes, if that's the bluetooth version."

(Note: I am using the 2.4g controller not the BlueTooth one, so can't use a different pairing mode i think?.)

So i changed to SDL2, but and it gets recognized as the "8BitDo M30 2.4G" in the Settings->Input->RetroPadBinds->Port1Controls area. and the key mappings also look good. But it still acts in the same way that the videos show.

If i delete the ./config/retroarch/autoconfig directory (whether in udev or sdl2 driver mode), it resets recognizing the gamepad as "6B Controller" (and same issues.. maybe worse, the keyboard can't control the menu now [think the keyboard at least worked be4, very wonky]). if i redownload the Controller Profiles, it acts the same strange way it was working (keyboard works, but gamepad controls dont get mapped and also control both P1 and P2).

Anyway, let me know what to do to help debug this and get the M30 working for Sega games. Im mostly testing this on Ubuntu Linux (and Windows11). and using the popular BlastEm SegaGenesis Core.

Note: there is another issue opened with this controller but seems like they saying its a "dinput" issue. Not sure if my issue is related to that... but on Linux i dont think there is a dinput option in the Settings->Drivers->Controller area anyway.

Also another person said they had the same issue with this controller and RetroArch when i posted about it in another forum, so the issue isn't limited to me.

UPDATE: I have another M30 controller that i bought (with the same firmware versions on the controller+receiver) and it acts wonky similarly in Linux (but on Windows it recognizes as 'XBOX 360' controller and seems to act normal... well for now... i think it may change as my other M30 originally acting normal in the beginning as well).
UPDATE#2: so i deleted retroarch and its .config/retroarch folder and reinstalled from scratch.
This 2nd/new M30 controller gets setup as the 'XBOX 360' controller, i map in Controls->Input then remap and save to that core or folder via the in-game menu, and now its working for that 1 new M30 controller (that weird issue where it controls 2nd player also is fixed).
Im going to replace the 1st/original M30 controller and see if i can get that working as well (i bought that in "Like New" condition off amazon so maybe it has issues?). Ill update this in a day if fixed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions