Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: cica on April 13, 2004, 09:31:50 am
-
Hi
I have literally spent hours researching and trying to figure this one out myself and I hate that I have to even ask this one, but I'm at my wit's end.
I have been trying to remap keys to control the Mame GUI. All I wanted to do was remap Player1 Start to select the game.
I go into c:\mame32\mame32ui.ini and add the line:
IU_SELECT "KEYCODE_1"
I then save it and run Mame32. As soon as I do, Mame32 rewrites the mame32ui.ini back to the default and my change is gone!
I even went so far as to make the file read-only after I edited it. Then Mame32 didn't rewrite the file, but it didn't accept my remap either.
To answer a few questions in advance:
1) I am running Mame32 on Windows XP.
2) I tried deleting c:\mame32\mame32ui.ini and c:\mame32\ini\mame32.ini. Mame32 recreates the files upon startup and the problem persists.
3) I selected the c:\mame32 folder, and the c:\mame32\ini folder and made sure the read-only flag was clear for them and all subfolders.
Any help would really be appreciated.
Thanks
-Tom
-
I use commandline MAME, not MAME32, so don't know if this will help, but
is
keyboard_in_interface 1
set in MAME32ui.ini ?
Also, try running MAME32 and selecting "Options - Interface Options - Allow game selection by custom key sequences"
Hope it helps!
-
is keyboard_in_interface 1 set in MAME32ui.ini ?
Also, try running MAME32 and selecting "Options - Interface Options - Allow game selection by custom key sequences"
Yes, keyboard_in_interface is 1 and I have the "Allow game selection by custom key sequences" selected.
What could cause the Mame32ui.ini to reset every time mame32 is run?
-Tom
-
I just tried doing the same thing you are trying to and it worked first try.
The first thing that comes to mind is are you using "|" and "!" correctly?
It should read ui_key_start "KEYCODE_ENTER | KEYCODE_1 ! KEYCODE_LALT". Notice the | means "or" and the ! means "not". So, enter or 1 not left alt is what the gui sees.
-
The first thing that comes to mind is are you using "|" and "!" correctly?
It should read ui_key_start "KEYCODE_ENTER | KEYCODE_1 ! KEYCODE_LALT". Notice the | means "or" and the ! means "not". So, enter or 1 not left alt is what the gui sees.
Thanks, I'll give that a try tonight. I've been using UI_Select, not ui_key_start. Most likely, Mame is barfing on that line and recreating the file because it doesn't like what it sees.
BTW, Why do I need to tell Mame not to use the left ALT key?
-
why not to use alt key... I have no idea, it came that way so I kept it that way. Not sure what kind of ill effects might be let loose by changing it, so do that at your own risk!!! :P J/k
-
BTW, Why do I need to tell Mame not to use the left ALT key?
I believe the ALT-ENTER combination toggles fullscreen in most windows apps, just tested, in MAME32, ALT-ENTER brings up the properties screen. I think maybe if you didn't exclude it, then you could never get the properties screen to come up with that combination because MAME32 would always see the ENTER as a start game command.