key mapping lost in newer version of mame 120 and up -GPWiz Eco

[xmenxmen]

Here's what I have:

Gpwiz eco usb.

Recently I have been playing with the newer mame version, mainly 119, 120 and 121.  I like the adidtional core2 support as well as minor speed increase.

So I go backup my old version (110 and 117) and replace with like say 120.  1st thing I notice is that my mapping are totally screwed up and half my keys don't work anymore.  So as usual, hit tab in mame and redefine them.  Exit that and went on and everything is good.

Now here's the real problem, each time I exit mame and launch it again, I notice that I cannot move back on my 2nd joystick (mapped to button 16).  Hit tab again and notice it's mapped to button 15 (strange).  Okay, map it a 2nd time.  Back in game, looks good again.  Exit mame amd come back in, problem back.

To make thing worst, looked at the default.cfg file and it's indeed the right mapping. 

And just to test, I start going back in version to see when it started happening.  Anything 117 and below doesn't have this problem.

Anyone got a clue what's up or how to fix as I am unable to use any of the newer version.

[u_rebelscum]

...
And just to test, I start going back in version to see when it started happening.  Anything 117 and below doesn't have this problem.

Hmm... if you're saying the problem started between 0.117 & 0.118, whatsnew.txt says:

Removed underscores from some keycode token names. Thus,
KEYCODE_0_PAD now becomes KEYCODE_0PAD. This is to prevent confusion
when parsing multiple keyboard items. Due to this change, also removed
imperfect backward compatibility with older configs; some mappings
will still work, but some won't. Note that this change will also
break some existing ctrlr files; new ones will be provided.
[Aaron Giles]

But this only explains the one time remap, and not what's going on with your button 16.   There shouldn't be any problems with just button 16, as mame is designed to handle 16 buttons per gamepad.  (There were other input changes with 0.117u1, but they shouldn't break button 16.)

Questions: are they any differences between the cfg file after mapping so it works but before you exit mame, after you exit mame but before you start again, and after you start and look at the UI mappings?  (Mame rewrites the file in between each of these 3 points even if there are no changes.)  Could you post at least the part that button 16 is mapped to?  (I'd have to dig up circuits and rewire to be able to test button 16 myself, and I'm at work not able to get to the circuits ATM.)  And is the only repeating problem button 16?  (I'm assuming you're remapping the general inputs.)

[xmenxmen]

...
And just to test, I start going back in version to see when it started happening.  Anything 117 and below doesn't have this problem.

Hmm... if you're saying the problem started between 0.117 & 0.118, whatsnew.txt says:

Removed underscores from some keycode token names. Thus,
KEYCODE_0_PAD now becomes KEYCODE_0PAD. This is to prevent confusion
when parsing multiple keyboard items. Due to this change, also removed
imperfect backward compatibility with older configs; some mappings
will still work, but some won't. Note that this change will also
break some existing ctrlr files; new ones will be provided.
[Aaron Giles]

But this only explains the one time remap, and not what's going on with your button 16.   There shouldn't be any problems with just button 16, as mame is designed to handle 16 buttons per gamepad.  (There were other input changes with 0.117u1, but they shouldn't break button 16.)

Questions: are they any differences between the cfg file after mapping so it works but before you exit mame, after you exit mame but before you start again, and after you start and look at the UI mappings?  (Mame rewrites the file in between each of these 3 points even if there are no changes.)  Could you post at least the part that button 16 is mapped to?  (I'd have to dig up circuits and rewire to be able to test button 16 myself, and I'm at work not able to get to the circuits ATM.)  And is the only repeating problem button 16?  (I'm assuming you're remapping the general inputs.)

I actually tried blowing away the existing cfg file and got the same result.  Not sure if they are different before and after the mapping, but I can certainly check.  Like I said before, under the config file, it shows the right mapping, but when mame loads, it shows something different in the tab screen.  weirld, right? 

Mame support still goes beyong 16 button as the gpwiz has for x/y and 28 buttons.  Everything else works, except that.  Yes, it's only button 16 and I am using the general inputs.  Even goes as far as deleting all the game control files..  Same result.

I'll post my config file once I get out of 'work'. 

[madcap]

which build of mame are you using?  i know mameui is working again but there is one build that i can confirm isn't working......

google this groovygamegear 16 button limit
(no i am NOT say it isn't ggg's fault cuz it isn't, these things work great)