Jump to content
LaunchBox Community Forums
Klamp

RA mame2014 core button weirdness

Recommended Posts

I am getting a weird behavior when trying to map my xbox 360 wireless controller in the mame2014 core.

I hit tab to map the controls in the mame overlay but here is my problem:

-I cant map the Y button of my controller (JOYCODE_1_BUTTON3), its not picked up by mame.  Did a test outside of mame and it is functional.

-When I map button 1 in mame to any controller button, mame adds the Y button to it.

Here is an example of a config file xml with the problem.  I tried to edit the file manually but JOYCODE_1_BUTTON3 does not do anything in game.


<?xml version="1.0"?>

<!-- This file is autogenerated; comments and unknown tags will be stripped -->

<mameconfig version="10">

    <system name="default">

        <input>

            <port type="P1_BUTTON1">

                <newseq type="standard">

                    JOYCODE_1_BUTTON2 JOYCODE_1_BUTTON3

                </newseq>

            </port>

            <port type="P1_BUTTON2">

                <newseq type="standard">

                    JOYCODE_1_BUTTON1

                </newseq>

            </port>

            <port type="P1_BUTTON3">

                <newseq type="standard">

                    JOYCODE_1_BUTTON4

                </newseq>

            </port>

            <port type="P1_BUTTON4">

                <newseq type="standard">

                    JOYCODE_1_BUTTON6

                </newseq>

            </port>

Any help or hints would be appreciated.  Thanks!

Share this post


Link to post
Share on other sites

I'm confused, you mention "MAME 2014", which is a very out dated MAME Core in RetroArch, but talk like it's regular MAME? I am ... lost. It's worth noting that on MAME now, at least that I've noticed within the last few versions, certain controller types (like In RetroArch) will get automatically assigned keys, for the most part. So what version / flavor of MAME are you on...?

Share this post


Link to post
Share on other sites

I have the same problem with both versions.  Just tested with both cores and same input problem.  Really weird.  

Figured it out.  I had both A and Y buttons configured to the A button in RA's input binds for some reason.  

Thanks for the reply.

  

Edited by Klamp

Share this post


Link to post
Share on other sites

Retroarch Mame controls suck because you got the Retroarch controller config and then you got the Mame controller config fighting each other. This is another one of the reasons I really dislike Retroarchs Mame over the stand alone.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...