• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
RetroPie forum home
  • Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Are These Mame Controls Misbehaving?

Scheduled Pinned Locked Moved Help and Support
mame controls
7 Posts 3 Posters 619 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    AlphaBetaPie
    last edited by 15 Jun 2022, 04:15

    I recently did some research on the proper way to map the best Mame control layout to a six-button controller. I found the Y, X, L / B, A, R method from another post. This seems to work really well for many games. Both Street Fighter and Mortal Kombat are perfect, except for one small issue.

    The start button, even though it's programmed to start on my control pad in Retroarch, does not work. The B button is almost always start for every game, and makes things difficult when selecting certain menus.

    For instance, when I hit B at the "Insert Coins" screen for Mortal Kombat, it enters into the character select screen and auto selects the first character (like it's a doule tap of the button).

    This B = Start is like this for tons of titles, like Donkey Kong, Galaga and others. What's going on there?

    B 1 Reply Last reply 15 Jun 2022, 07:56 Reply Quote 0
    • B
      barbudreadmon @AlphaBetaPie
      last edited by 15 Jun 2022, 07:56

      @AlphaBetaPie You should be more precise about the core you are using.

      Mame libretro cores can be weird when it comes to input mapping, due to the fact they have 2 layers for it (mapping in retroarch + mapping in mame osd). You might be able to get around this by deleting any custom config (on both layers) you did for that core and reconfiguring only the mame osd layer from scratch.

      FBNeo developer - github - forum

      A 1 Reply Last reply 15 Jun 2022, 16:55 Reply Quote 0
      • A
        AlphaBetaPie @barbudreadmon
        last edited by 15 Jun 2022, 16:55

        @barbudreadmon said in Are These Mame Controls Misbehaving?:

        @AlphaBetaPie You should be more precise about the core you are using.

        Mame libretro cores can be weird when it comes to input mapping, due to the fact they have 2 layers for it (mapping in retroarch + mapping in mame osd). You might be able to get around this by deleting any custom config (on both layers) you did for that core and reconfiguring only the mame osd layer from scratch.

        Thanks. You are correct I'm dealing in Mame 2003. The default emulator that comes with my Retropie image. I have tried deleting the core remapping file, and just letting it revert back to the default, but there seems to be no change.

        What I'm not understanding is this.

        If I go into the controls section of Retroarch, and assign Start = Start and have every button accounted for, why is it negating this and defaulting to where Start does nothing and B doubles as a Start/Action button? Even after I have assigned it.

        Unless I'm in the wrong menu? The other inputs all deal with keyboard commands, which don't seem relevant when using a six-button controller.

        M B 2 Replies Last reply 16 Jun 2022, 00:06 Reply Quote 0
        • M
          mahoneyt944 @AlphaBetaPie
          last edited by 16 Jun 2022, 00:06

          @AlphaBetaPie there is likely conflicts with mame's internal input mappings with RetroArch's input mappings. Have you altered any of the preset inputs in the mame menu?

          Alternatively, mame2003-plus is an emulator installable from the optional section. This version has the ability to change controller layouts within RA (retropad, fight stick, 6-button, and 8-button)

          A 1 Reply Last reply 16 Jun 2022, 13:50 Reply Quote 0
          • A
            AlphaBetaPie @mahoneyt944
            last edited by 16 Jun 2022, 13:50

            @mahoneyt944 said in Are These Mame Controls Misbehaving?:

            @AlphaBetaPie there is likely conflicts with mame's internal input mappings with RetroArch's input mappings. Have you altered any of the preset inputs in the mame menu?

            Alternatively, mame2003-plus is an emulator installable from the optional section. This version has the ability to change controller layouts within RA (retropad, fight stick, 6-button, and 8-button)

            Thanks. I plan to uninstall/reinstall these emulators and see if that changes anything. Maybe if there is a conflict somewhere, it'll remove it. Will touch base if more info is needed. Thanks as always!

            1 Reply Last reply Reply Quote 0
            • B
              barbudreadmon @AlphaBetaPie
              last edited by 16 Jun 2022, 15:00

              @AlphaBetaPie said in Are These Mame Controls Misbehaving?:

              B doubles as a Start/Action button

              It's not unusual for B (which i assume is the first action button in mame2003 ?) to be used as a start button in an arcade game.

              FBNeo developer - github - forum

              1 Reply Last reply Reply Quote 0
              • M
                mahoneyt944
                last edited by mahoneyt944 17 Jun 2022, 07:08

                These configs will not be defaulted by reinstalling the emulator. These will be stored in the default.cfg and game.cfg files. These should be located in a "mame2003/cfg/" directory in the location you load your mame roms from.

                1 Reply Last reply Reply Quote 0
                7 out of 7
                • First post
                  7/7
                  Last post

                Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.

                  This community forum collects and processes your personal information.
                  consent.not_received