Can't get controls to work in Mame4All on my RetroflagGPI

che_don_john

Pi Model or other hardware: Pi Zero W
Power Supply used: RetroFlag GPI power cord
RetroPie Version Used: 4.7
Built From: Official RetroPie Zero (i.e. not pre-made)
USB Devices connected:
Controller used: GPI built-in controller
Error messages received: None that I can see
Guide used: https://sinisterspatula.github.io/RetroFlagGPUGuides/Controls_Updater_Menu
File: N/A
Emulator: Mame4All
How to replicate the problem: Loading any Arcade ROM with Mame4All

Hi all,

I've built my own image for my RetroFlag GPI from scratch, and I can't for the life of me get the controls to work in Mame4All. I know it isn't an issue with the ROMs because I tested them on pre-made images (Supreme, RetroBoy).

I've managed to get the controls (Adavanced Controls Framework) working for PiFBA by deleting the relevant cfg file and running the GPI's Controls Updater Menu, but can't replicate for Mame4All.

I've tried deleting the default.cfg file for Mame4All and running that same controls updater, but to no avail.

Also, in the run command menu before the ROM launches, I've tried setting the 'User Input' to both 'Microsoft x-Box 360 pad #1' and 'Xbox Gamepad (userspace drive)', neither has worked.

Any help/advice would be much appreciated!

rbaker

@che_don_john Mame4all requires you to press TAB to access the menu and once in there you can configure your controls manually. See the docs here:
https://retropie.org.uk/docs/MAME/#mame4all-pi

che_don_john

@rbaker How can I do that with the Retroflag GPI case? Is there a way to connect a keyboard?

EDIT: Just seen that USB port on the back; maybe with a micro USB adapter I might be able to do it

simpleethat

@che_don_john The website lists the USB port on the back for "Firmware Upgrade" so possibly but also possibly not.

There is a way to revert the setup of the GPI case (it's on the retroflag site or comes with the script download, I can't remember which right now) but that won't really help here as you need to use the buttons to make the control scheme changes.

The Zero W does have Bluetooth capability so could you connect a Bluetooth keyboard to get it done? I don't have a Bluetooth keyboard to experiment for you but it was a thought I had whilst checking out the forums.

che_don_john

@simpleethat said in Can't get controls to work in Mame4All on my RetroflagGPI:

@che_don_john The website lists the USB port on the back for "Firmware Upgrade" so possibly but also possibly not.

There is a way to revert the setup of the GPI case (it's on the retroflag site or comes with the script download, I can't remember which right now) but that won't really help here as you need to use the buttons to make the control scheme changes.

The Zero W does have Bluetooth capability so could you connect a Bluetooth keyboard to get it done? I don't have a Bluetooth keyboard to experiment for you but it was a thought I had whilst checking out the forums.

I was going to trying connecting my keyboard via a micro usb adaptor cable into the back, but the hole leding to the port is tiny and the chunky cable wouldn't fit through!

So, yes, I think Bluetooth is the way to go here. Thanks for your help!

simpleethat

@che_don_john I wish I could be more help but I haven't tried to play around with Bluetooth on my GPi and it's the only running Zero build I have. I did all of my configurations for my GPi build on a regular screen out of the handheld before finally setting it up for the case itself.

che_don_john

@simpleethat said in Can't get controls to work in Mame4All on my RetroflagGPI:

@che_don_john I wish I could be more help but I haven't tried to play around with Bluetooth on my GPi and it's the only running Zero build I have. I did all of my configurations for my GPi build on a regular screen out of the handheld before finally setting it up for the case itself.

Oh, so you were able to configure Mame4All for the GPI before you put the PZ into the case (i.e. by connecting it to a TV)? I thought about doing that but then I'm not sure how to connect the GPI controller to the Pi in order to configure/map it (if that makes sense?!).

che_don_john

OK, so I was able to solve it; a couple of steps I think were necessary, the others I did as precautions.

Basically, the main issue was that my runcommand-onstart.sh and runcommand-onend.sh files were empty; these need lines to trigger xboxdrvstart.sh, which in turn should allow the GPI controls to be recognised by Mame4All. Here's what I did:

In /opt/retropie/configs/all/runcommand-onstart.sh I added the following:

#!/bin/sh

source /opt/retropie/configs/all/xboxdrvstart.sh > /dev/null 2>&1
sudo pkill -STOP mpg123 > /dev/null 2>&1
fbset -g 320 240 640 480 16

In /opt/retropie/configs/all/runcommand-onend.sh I added the following:

#!/bin/sh

source /opt/retropie/configs/all/xboxdrvend.sh > /dev/null 2>&1
sudo pkill -CONT mpg123 > /dev/null 2>&1
fbset -g 320 240 320 240 8
fbset -g 320 240 320 240 32

(the lines about mpg123 are, I think, related to background music or something like that; probably not needed, but I borrowed these from a pre-made GPI image so thought safer just to copy everything.)

Then, after a restart/reboot, I switched the GPi's D-Pad to axis mode by by pressing START+DPAD LEFT for 5 seconds, until the purple light flashed.
I deleted default.cfg in /opt/retropie/configs/mame-mame4all/cfg
Finally, I the went to GPI's 'Controls Updater Menu' and ran that script, just in case.