@GongStar the output of dmesg might be useful after the build fails. You are right there is nothing else in the log - I thought there might be something. Not sure of the issue if you have plenty of free space on card, and no overclock.
I confirm the same issue. Also, controls appear unasigned under the retroarch quick menu option, unlike other mame versions (2003, 2010). The only way to remap controls is via the tab menu, but secondary mouse buttons do not work
I just tested with 1944.
Mame2010 saves the hiscore.
Mame2016 doesn't.
Unfortunately mame2010 only recognizes 1 joystick.
So it must be due to the mame2016 configuration (?).
Hello everyone, so all of the sudden I am getting —- in the control input slots in MAME2016 and MAME2003. These are also uneditable. I would really like to get some game controls configured, so any help would be extremely appreciated! Thank you
This is on Retroarch 1.8.5, and I did not see any error messages. I am just unable to change any of my controls suddenly. I also tried re-installing (assuming that I did something) from binary and it did not help. I did not update the system during this.
Here are my
Details:
Raspberry Pi 4B w/4GB ram, 64bit processor
Power Supply used: MODEL DCAR-RSP-3A5C, INPUT 100-240V AC, OUTPUT: 5.1V 3.5A
RetroPie version: Raspbian GNU/Linux 10 (buster) - Linux retropie 4.19.97-v7l+
Built From: RetroPie-Setup version: 4.6.1 (4464b474)
USB Devices connected: SNES controller, USB keyboard
Controller used: SNES controller, USB keyboard
Please note: I did switch to a PS2 USB controller during the process of going through my arcade games & configuring the emulators. It did let me change the controls at first and I did not update anything so I cannot understand why I am suddenly getting three dashes in the input slots - - -
Also note: Mame2003 works up I cannot go up down left or right.
SOLVED, a MAME 2016.rmp file was generated in
configs/arcade/mame2016 and over wrote my controls. I deleted the .rmp file and now I have my controls working again.
lr-mame2016 worked OK for me when playing games. I can't tell from your message whether it's working for you but throwing an error which you are investigating or not working at all due to the error. I did the standard Pi 4 build instructions. I couldn't get bbhcotw to run though so I'll be interested if you solve the error for this particular game.
Out of curiosity, I tested a dkong.zip from an unofficial "MAME 2016 Reference Set" which didn't come with any samples for dkong in an extra file. Seems like the 2016 version (aka MAME 0.174) of the dkong rom has its samples included, since – as far as I can tell – it sounds exactly as the MAME 2003-Plus version with an external samples file in my Retropie.
So, if you don't have sampled sound, are you sure you have the right dkong rom file for MAME 2016 / 0.174?
Ok, I read other messages, and I'm currently compiling again, but this time I'm using the git URL with the version fixed by another user from this forum. I'll keep you informed. I'll do some tests and will report.
I have sent the PR. The patch is a kind of "quick and dirty" I am not sure how much can fit into a good libretro baseline (please see the commits comments)
Well i decided to try out on my Pi 3 first to install the files needed and then swap the card over to my 3B+ cause there is some roms i want to test out to see if they work better on the newer Pi.
Ok tried it out on my Pi 3 and still getting the same errors on getting it which is strange cause when i was on 4.2 i was able to download it but now i keep getting that error message after 17 minutes.
