Mame .cfg schema question

[arzoo]

Hey all -
I've been working with a LEDBlinky user who's having problems when he remaps controls. Here's his asteroid.cfg file:

Code: [Select]

<?xml version="1.0"?>
<!-- This file is autogenerated; comments and unknown tags will be stripped -->
<mameconfig version="10">
    <system name="asteroid">
        <input>
            <port tag="IN0" type="P1_BUTTON5" mask="8" defvalue="0">
                <newseq type="standard">
                    DEFAULT
                </newseq>
            </port>
            <port tag="IN0" type="P1_BUTTON3" mask="16" defvalue="0">
                <newseq type="standard">
                    DEFAULT
                </newseq>
            </port>
            <port tag="IN1" type="P1_BUTTON4" mask="32" defvalue="0">
                <newseq type="standard">
                    DEFAULT
                </newseq>
            </port>
            <port tag="IN1" type="P1_BUTTON2" mask="64" defvalue="0">
                <newseq type="standard">
                    KEYCODE_LCONTROL
                </newseq>
            </port>
            <port tag="IN1" type="P1_BUTTON1" mask="128" defvalue="0">
                <newseq type="standard">
                    KEYCODE_LALT
                </newseq>
            </port>
        </input>
    </system>
</mameconfig>

The reason LEDBlinky is not working correctly is because the code is not expecting "DEFAULT" as a keycode. I've never seen this value before and I don't think any version of mame I've used can generate this value.

<port tag="IN0" type="P1_BUTTON5" mask="8" defvalue="0">
   <newseq type="standard">
      DEFAULT
   </newseq>
</port>

Does that value indicate that the button should use the keycode from the default.cfg file? How does that value get set? Any help or elaboration would be greatly appreciated.

Thanks,
arzoo

[u_rebelscum]

Does that value indicate that the button should use the keycode from the default.cfg file? How does that value get set? Any help or elaboration would be greatly appreciated.

Sort answer: Yes, it tells mame to use the default.cfg, sort of.

Long answer: Mame saves three* input maps: internal global defaults, global "remaps", and game specific "remaps".  The default.cfg file effects the second, and game specific.cfg the last.  (the first is set in the source.)  Normally, both the default.cfg and gamespecific.cfg are completely set to "DEFAULT", which means mame looks at the next higher level.  Since mame doesn't save in either default.cfg or gamespecific.cfg the defaults, you don't see it.  There is one exception.  If the game driver remaps in source the buttons, that game's default isn't "DEFAULT", but whatever is hardcoded in the source.*  (Such as asteroids.)  So if you remap mame to use the global "DEFAULT", mame has to save it.

So "DEFAULT" means "check the next higher up list


BTW, what mame version is he using?  This was broken a couple times, and I thought currently was.  (I need to retest at home.)


*TMI answer: Technically, mame has another input map: game specific defaults.  This list is only used to see if mame needs to if the input were changed, and if not don't save that input.  It is out of the check the higher hierarchy.


If I'm not clear, sorry.  Let me know where I went into left field.

[mark6437]

u_rebelscum, It is me he is helping. Me again, same guy that you answered the U-Trak mouse button question for   

I am using .133u3 mame.exe but I am using .134 roms, and thre is a reason for this.

Short reason is because I couldnt figure out how to compile on my own, ever tried headkazes program. I got frustrated.

So I was on the highscore page and they have a download able mame.exe 133u3 that MKCHAMP compiled that has highscore in it:
http://highscore.mameworld.info/download.htm

So I figured I would use that since its already done. And it is working

arzoo is helpig me with Asteroids because after I remap the controls in mame to what i want, I go back into the game and the speak and blink is off. Even though in controls editor its right. So he had me send him the debug. Thats where we are at 

THX!
Mark

[arzoo]

Sort answer: Yes, it tells mame to use the default.cfg, sort of.

Long answer: Mame saves three* input maps: internal global defaults, global "remaps", and game specific "remaps".  The default.cfg file effects the second, and game specific.cfg the last.  (the first is set in the source.)  Normally, both the default.cfg and gamespecific.cfg are completely set to "DEFAULT", which means mame looks at the next higher level.  Since mame doesn't save in either default.cfg or gamespecific.cfg the defaults, you don't see it.  There is one exception.  If the game driver remaps in source the buttons, that game's default isn't "DEFAULT", but whatever is hardcoded in the source.*  (Such as asteroids.)  So if you remap mame to use the global "DEFAULT", mame has to save it.

So "DEFAULT" means "check the next higher up list


BTW, what mame version is he using?  This was broken a couple times, and I thought currently was.  (I need to retest at home.)


*TMI answer: Technically, mame has another input map: game specific defaults.  This list is only used to see if mame needs to if the input were changed, and if not don't save that input.  It is out of the check the higher hierarchy.


If I'm not clear, sorry.  Let me know where I went into left field.

Thanks rebel for the info - makes perfect sense. I have a pretty good handle on how the source/default.cfg/game.cfg hierarchy works - but I did not know about the game drivers that remap in source. And I guess it doesn't work in the versions of mame I've used because I've never seen this before. So now I'll update LEDBlinky to handle this case.

Thanks for the help!!!