Adafruit GPIO Arcade Controller not Working in MAME

MRInfected101

This post is deleted!

MRInfected101

@caver01 Okay, so for emulators I've tried using Lr-mame2003 and Lr-mame2010, still no response from the GPIO controls, the ROM sets I'm using, I assume they are merged, are Robo Roto and Star Fire (set1).

markyh444

@mrinfected101 you really can't assume anything when dealing with romsets and arcade emulation mate. I'd advise reading the many guides on this forum and the official docs properly, as well as getting hold of the correct roms (Google!!). I have and they're sufficient enough to get you up and running.

MRInfected101

I have read the docs and forums many times, and still do not have a solution, I looked through where I got the rom sets and can say they are merged files, so any suggestions with whats wrong with the Joystick would be much appreciated.

rbaker

@mrinfected101 said in Adafruit GPIO Arcade Controller not Working in MAME:

and can say they are merged files

yes but is it the correct romset? 0.78? for lr-mame2003?

MRInfected101

That is where I'm confused, I've checked the excel compatibility list and only found starfire on the list, is there somewhere in the zip file it will tell me if it's 0.78? Or can you provide me a link for further reading into 0.78 compatibility?

mitu

@mrinfected101 The RetroPie docs have an Arcade dedicated section that explains which romset is used by every emulator and a compatibility list - see https://retropie.org.uk/docs/Arcade/ for a start.

caver01

@mrinfected101 said in Adafruit GPIO Arcade Controller not Working in MAME:

is there somewhere in the zip file it will tell me if it's 0.78?

There is nothing in a single rom file that I am aware of that will identify it as coming from any set. However, a tool like CLRMAMEPRO can examine a rom and its contents inside the .zip and compare hash values to known working files from a particular set using a .dat file as a reference. It is effectively a validation program that can also rebuild specific sets out of other sets provided you have all of the pieces.

If you simply download a "merged set" labeled 0.78 in the description of the download, you are basically trusting whomever put the file together that it is indeed what they claim it to be. The only way to be sure is to prove it with CLRMAMEPRO. I wish I could help more with that part, but I have never been successful using it, although others have. It may not be your problem, but having a known good rom from a set that matches the emulator you are using is an important troubleshooting step.

MRInfected101

@mitu Okay I've found the page with validating, rebuilding, etc. one of the romsets I am using I have found on the Lr-mame2003 compatibility list, should I go through validating it still?

caver01

@mrinfected101 The compatibility list merely describes what works on the Pi given you have a valid rom from the correct set. It does not validate your rom.

MRInfected101

@caver01 okay thanks, I'll have to work on the validation later, as I don't have access to download CLRMAMEPRO at the moment, I will make another post when I have successfully verified the romsets. Thank you very much.

rbaker

@mrinfected101 The best thing to do is acquire a full "reference" set for 0.78. That way, you do not need to use clrmame.

caver01

@rbaker I agree, and this is what I have done. But it can be a catch22--how do you know for certain that what is described as a reference set is what it claims to be? Testing the ROMs is one way I guess.

rbaker

@caver01 you can never be 100% but generally I find the ref sets are reliable. I guess my message is that hunting single roms from random places is the path to madness and frustration where the full set can sit somewhere and can be dipped into to find roms when needed. My early experince was launching a rom in mame and tab wouldn't do anything. I sat for ages then tried another rom and then another then another mame and so on. I then discovered this project and read the docs and became born again :)

caver01

@rbaker SO true.

MRInfected101

Well I did the validation and physically look at my ROMS there has been no change so does that mean my ROMsets were perfect or did I do something wrong?

alexraffa

Hallo everyone!

I just complete the build of an arcade style control panel, using retrogame and mech. joystick and buttons. (1 joystik + 6 buttons) as follows:
1 button 1UP coin (retrogame set to send value "5")
1 button 1UP start(retrogame set to send value "1")
up, down, left, right joystick
A
B
X
Y
buttons
Configured in emulation station as
1 button select
1 button start
up, down, left, right joystick
A
B
X
Y
As may main focus will be mame lr-mame2003 I want to assign 8in mame only) select to coin 1 and start as 1P start

Everything seems to work, except that 1coin and 1p start do not seem to have any effect in mame.
In emustation I can use them to navigate the menus etc.. just fine...
I tried to do a core map in retroarch config, but I may be missing something as it has no effect.
How to troubleshoot?
I have a ps3 style usb controller, and with it I con control mame coin and 1p start, but have not found a way to replicate the behaviour

Hints more than welcome!

caver01

@alexraffa Your post has nothing to do with Adafruit arcade controller. Please do not hijack this thread with your question.

Post a new thread, but READ THIS FIRST.

caver01

@mrinfected101 I am at a loss about why you joystick does not work. It sounds like you are confident you have the right roms for the emulator you are trying. I guess the joystick could be wired incorrectly, or perhaps it is a configuration problem with the Adafruit setup. I wonder if maybe there was a misleading suggestion in online guide on Lynda.com. Sorry. I am out of ideas.

MRInfected101

Well last night I was testing other things with retropie, and ended up plugging in my X-box one control in through USB, configured the controls in emulation station, launched one of my ROMs (roboroto) and it was working just fine, and the joystick works fine in emulation station before launching a ROM and it doesn't when it launches so that is where I'm at.