Game and Watch ‘Game B’ button mapping

dewiele

Re: Tutorial: Handheld and Plug & Play systems with MAME

Hi All, I have got gamandwatch roms working well using lr-mess and performance seems to be alright. My remaining issue is I have no idea how to map the ‘Game B’ button. Has anyway dealt with this? All other buttons are working fine.

Folly

@dewiele

Welcome to the forum.

Just a few tips :

You might want to check this topic when starting to post :
https://retropie.org.uk/forum/topic/3/read-this-first
The best section for this question is : Help and Support
Try to post to a relevant poster, in this case @DTEAM or me (@Folly)

About lr-mess / lr-mame / mame standalone :
You can access the main "mame UI" with the TAB key.
Go to -> Input setting -> input asignments (this machine).
Here you will see that the "2" key is used for "Game B".
Hope this is your answer to the question.

Happy posting ;-)

DTEAM

@dewiele

If you switch to MAME standalone version, here's how to set you gamepad. See post 1

https://retropie.org.uk/forum/topic/28462/tutorial-handheld-and-plug-play-systems-with-mame?_=1745236804243

dewiele

@DTEAM thanks for your reply.

I knew I posted message too soon, I’m using a PSPi to run retropie and was struggling to find the rom menu to set Game A/Game B mappings. Found it now.

dewiele

@DTEAM I tried MAME standalone originally and got the game and watch ROMs running however by default the TAB menu was inaccessible as the PSPi controller mappings were not set up. So couldn’t map any buttons. Was hoping MAME standalone would perform better but had to switch to lr-mess for which retroarch config worked.

Folly

@dewiele said in Game and Watch ‘Game B’ button mapping:

I tried MAME standalone originally and got the game and watch ROMs running however by default the TAB menu was inaccessible as the PSPi controller mappings were not set up.

You should use a keyboard first.
I you somehow use the standard runcommand :
mame = "/opt/retropie/emulators/mame/mame %BASENAME%"
and it still doesn't work with the keyboard then you could try to add "-ui_active" to the runcommand.