thegamesdb,net API is offline. Use a different scraper or just wait. How many times is this issue going to be posted? Oh, just checked their site, it's all new and fancy.

@casadero said in How do I add scanlines to MAME in retropie 4.2?:

@caver01 : correction to my recent post: I put the ROMs to the MAME-MAME4ALL folder and, later, to the ARCADE folder. there is no folder like "lr-mame2003" folder on my USB stick, but a "mame-libreto". I still do not know the difference between all these MAME Emulators, but I will start some research about that issue the coming weekend.

Please read this.

Emulators come in two basic flavors in RetroPie--standalone or libretro core. The standalone are just that--they run independently of other frameworks. They are configured independently. They might have their own way of generating display effects (advancemame for instance has some RGB effects that can be turned on). The libretro cores are all emulators that run inside of the RetroArch framework. These can share common settings for controls, video, etc. The CRT-PI shader is for RetroArch, so it won't apply to the standalone emulators, whether they are MAME or something else.

Given the two kinds of emulators, there are several different versions of MAME. Some are standalone, some libretro cores. Each requires their own ROM versions. Generally speaking, you should only use ROMs that come from a set with a version matching that version of MAME. If the location of your ROMs allows you to choose more than one emulator, you do that using the RUNCOMMAND function (which you should also click and read).

@stephan311280 Thank you mate.

@r3d007so i decidedto solve the mystery of why you had to put the bios' in the roms folder. if the retroarch.cfg in /opt/retropie/configs/all/ does not have the line:

system_directory = "/home/pi/RetroPie/BIOS"

or it is #hashtagged out, or you edited the retroarch.cfg for those systems either manually or through the retroarch gui, that made major config changes then you need to put them in the roms folder. to fix this open up /opt/retropie/configs/all/retroarch.cfg and see if that system directory line is in there. if it is #hashtagged out, remove the hashtag and save.if it is not in there, then add it. if it is correct open up the retroarch.cfg in the individual systems config folders and find the issue and delete or correct it. the rgui can mess things up when you are using it, hence why i never use it to configure anything other than core-options.

@rascas doesn't work OOTB unfortunately, well for me anyway. Literally no buttons work in Kodi at the minute. Having to use my wired keyboard

I didn't even know about RGUI until I looked it up... Now I understand what was going on....Emulation is on point, the controller doesn't work until you turn the analog button on.

@chipsnblip I've also tried with my iPad charger (5.1 volts at 2100 mA) and the same issue occurs with exactly the same repro steps.

This morning I tried a different distro (batocera-linux -- derived from Recalbox). Everything works without any issues on my PiZero W (NES, SEGA GENESIS, SNES). The only difference in my setup with batocra-linux is that my controller needs to be on the "D" switch instead of the "X" (my controller was not working in "D" mode with RetroPie). Maybe that's another clue to investigate. For the time being, I'll stick with batocera-linux since It Just Works™.

I will still be monitoring this thread as I am curious if anybody else is able to reproduce. I can't be the only one having this issue.

I'm working to change the video settings in retroarch to best fit to the bezelproject artwork. I have about 400 games in MAME 2010 and had them all working fine then something happened and now, like others, I get the "Failed saving config to "/opt/retropie/configs/mame-libretro/retroarch.cfg" error message.

I've tried deleting the retroarch.cfg file
I've checked permissions and they're pi:pi

I've tried the suggestions listed here and it seems like most of the suggestions here, and over at the retroarch discord are just "try this and cross your fingers."

Surely someone knows what's going on and how to fix it.

pi model: 3b+, 128gb micro sd
power supply: 5.1v 3a
RetroPie version: 4.8
Built from: scratch
USB devices connected: Ultimarc I-PAC Ultimate I/O
Controller used: Ultimarc I-PAC set to keyboard emulation
Error messages received: Failed saving config to "/opt/retropie/configs/mame-libretro/retroarch.cfg
File: retroarch
Emulator: mame 2010

I know this post is a couple months old, but I've just set up moonlight today on my Retro-Pie setup, using the same controller, and ran into a similar (if not the same) issue... But I managed to come up with a solution which (I think) will hopefully help others.

Long story short, I replaced the line matching the controller's ID (030000005e040000dd02000003020000) in /usr/share/moonlight/gamecontrollerdb.txt with this:

030000005e040000dd02000003020000,Microsoft X-Box One pad (Firmware 2015),platform:Linux,x:b2,a:b0,b:b1,y:b3,back:b8,guide:b10,start:b9,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,dpup:h0.1,leftshoulder:b4,lefttrigger:b6,rightshoulder:b5,righttrigger:b7,leftstick:b11,rightstick:b12,leftx:a0,lefty:a1,rightx:a2,righty:a3,

When I start moonlight it outputs an error about the config not being correct now, but it actually works (button mappings matched what Steam/games wanted, with no manual config necessary within steam or games).

I came up with this mapping by running the SDL "controllermap" utility. I compiled it using the steps laid out here

Now it's very possible I did something wrong, but when I ran controllermap, all I got was a blank screen (apparently you're supposed to see prompts asking you to assign/map buttons, but I never saw this). The first time I ran it I just mashed buttons until it exited. What this accomplished was it allowed me to get an idea of what order it took the inputs (based on the order it output them in the configuration string that was output when controllermap exited. Then, using this order as a reference, I ran controllermap again I pressed the buttons/joysticks in the order seen in the configuration string. This time controllermap output the string I included above. Then, as I said, I replaced the existing mapping in moonlight's config file. Then I rebooted (probably unnecessary) and launched moonlight again, and my controller was working.

@Gamerguy010101 Please mark the thread as solved

Thanks I will do that. Sorry, I didnt even know where to get started with this.

Found the solution.

Instead to just entering retroarch at the command prompt I needed to enter the full path of the binary or /opt/retropie/emulators/retroarch/bin/retroarch in this case.

If you are already in the /opt/retropie/emulators/retroarch/bin/ directory you need to type ./retroarchto run the command.

So, oddly, I figured out how to make it work. Not sure why though.
So for starters, it started working again yesterday (when I made the post), but I didn't know how. Regardless, today it stopped working again.

However, it was fixed quite simply. I plugged it into my PC, and then plugged it back into my Pi. Now it works fine again. I have no idea why, though.

Hey buddy the way i did it which is quite easy is take the bios and put it in the USB section along with your psx games section. (I know that isnt right but bear with me).
Plug your USB in like always and wait for upload to finish after done press F4 in the emulation station window to bring up a terminal and type in the following:
cd home/pi/RetroPie/roms/psx/
exactly like that then type in:
ls
You should see the SCHP1001.BIN file or whatever in this folder near the top i think, if so type the following command:
mv SCPH1001.BIN /home/pi/RetroPie/BIOS/
that will move the file from the USB for you this should fix the issue.
If the first command isnt working follow this video from 1:20

Hope this helps, glhf.