Buttons Crossing in MAME

[DillonFoulds]

Hey guys, wiring up a (USB) GPWiz40 to use with MAME .133

I've got all the controls working fine, except when i push player 3 left, it does nothing.
More interesting, Player 4 right controls both player 4 right and player 3 left...

I checked in windows, control panel, game controllers, and the buttons do not cross over. P3 left in windows is Button 17, and p4 right in windows is 16.

Curiously, when i push P3 left while configuring, it sets it to Joy 1 Button 16 (mame lists all buttons as one value less than what windows reports?), but when i reload mame or load any game, it always switches "Joy 1 Button 16" back to "Joy 1 Button 15".

The buttons do not interfere with each other in either Joy2Key in notepad, or in any other emulators...


Edit:
Just checked mame's \cfg\default.cfg, in it, both P3 Left and P4 Right are mapped to JOYCODE_1_BUTTON16, but all the controls in a close number range (14-20) are in use...

Edit2:
I think I've found the problem. Mame starts counting at 0, while windows control panel and mame\cfg\defaults.cfg both start counting at 1.
This wouldn't be an issue, but when default.cfg reaches 16, for some reason it counts it twice, making the numbers stop lining up with the control panel, and start lining up with mame (counting from 0) resulting in a duplicate of JOYCODE_1_BUTTON16, which on my particular setup reflects P3 left and P4 right.

Am I the only one in the world having this problem?


Edit3: Tried a new computer, never ran mame on it before, got the latest mame, problem persists. It can't be a wiring problem, as in control panel it still shows up correctly, and nothing is hitting 2 buttons (mainly P4 right).

Any suggestions? I'm wondering if there's a ctrlr file or something i should be using?

[u_rebelscum]

Ah, sound very much like back to the old button numbering issues.*

Mame has 16 buttons per device with internal names and numbering from 1-16.  Anything above that uses the OS's numbering and naming.  Microsoft's DirectInput numbers from 0 to 127, and mame uses whatever windows calls buttons 17-128 (which windows calls 16-127).  It's just our luck that windows calls button 17 "button 16", and mame calls button 16 "button 16"

With the same name, I'm guessing mame can't tells the different when reading the cfg file.  It should work the first time you change it I think.
(Hmm, but you're having problems with buttons 15 & 16, not 16 & 17...  )


*FWIW, mame had simular issues back when it only counted up to 10 buttons per device.  I haven't heard this problem for a long time, and thought it was fixed.

[DillonFoulds]

well i am jamming a start button, 4 play buttons, and an 8-way for each player on to my GPwiz40. Pretty much filling up every pin available...

In mame, it's buttons 15 and 16 (15 keeps remapping to 16 iirc), and mame starts counting from zero, so really it is buttons 16 and 17 in windows control panel.

[u_rebelscum]

In mame, it's buttons 15 and 16 (15 keeps remapping to 16 iirc), and mame starts counting from zero, so really it is buttons 16 and 17 in windows control panel.

I think we need to sort which starts at 0, and which starts at 1:

Starts at 1:
windows control panel,
mame's UI remap menu
mame's internal names

Starts at 0:
mame's internal indexing numbers
directX directInput api numbering
mame's non-internally-named buttons (since it ges the numbers for directInput numbering)

I'm not sure (will test at home):
mame cfg/ctrlr file format

So, you can see, 2 of the "in mame" numbering starts at 1, and the other two start at 0.  Do you mean the cfg file format when you say "in mame"?

[DillonFoulds]

By "in mame" i mean launch mame, and go into the config menu in the mame ui when you can select a rom, and this one starts at 0.

The default.cfg starts at one on mine.

Windows control panel starts at 1.

That's where my technical knowledge ends. I don't know anything about the inner workings of directX.