I tried everything that I could find in the forums, and it still wouldn't work.

So I uninstalled it and reinstalled it... works perfectly. Nothing like a good ole fashioned reinstall.

Still don't know what caused the problem though.

Sounds like a bad/fake card. If not check the compatibility list:
http://elinux.org/RPi_SD_cards

@ScottF80 That's it - and you solved all by yourself ;)

@sphirst You can accomplish this by editing your runcommand-onstart.sh script, as @herb_fargus mentioned.

edit /opt/retropie/configs/all/runcommand-onstart.sh nano /opt/retropie/configs/all/runcommand-onstart.sh then paste the following into script (it checks if the system is psx, if so, play the mp4): [[ $1 == *psx* ]] && omxplayer -o both -b --layer 10001 /path/to/your/ps1.mp4 lastly, which I'm not sure is even necessarily, but make it executable. chmod a+x /opt/retropie/configs/all/runcommand-onstart.sh

In case you need it, here is the ps1 boot screen (mp4 format): https://dl.dropboxusercontent.com/u/23611685/video/ps1.mp4?dl=1

Well for the GBC all you need to do is to drag n drop the roms into the rom folder of GBC.

As for MAME. Well, you need to know which emulator you're going to use and you need that romset, lets say the romset is something like the version of the roms.

I can recommend you to use the lr-fbalpha emulator, this requires the 0.175 romset. if you can find this romset and download the games you're fine, all you have to do then is drag n drop the mame roms to the FBA roms folder and you're ready.

However, if you find a different romset you need to "upgrade" this romset to the romset the emulator is supporting. You can do this with a program named clrmamepro.

Here is how I did it the quickest way, just check this page:

https://github.com/retropie/retropie-setup/wiki/Managing-ROMs

See which romset is needed for the emulator you're going to use, like for an example "fba 0.2.97.39" Just add the two magic words one starts with a "D" and the second starts with a "R". Use Google for this. There is one site it's name starts with an "A" and ends on ".org". Well I said to much now... Good luck!

@justhoeber if it does it again with a new pi then you may have a bad TV ;)

@Xanathar Awesome!

When I first started with Retropie thegamesdb.net went down for a day... then a couple days... then a week. Turns out their hosting service cut them off for excessive sessions without any warnings so they have to raise enough $$ to pay for a dedicated servers.

The service does go down from time to time as well, so it's not uncommon to see what you are seeing. That's part of why I still scrape from the command line: scraper -append -thumbs_only once you are in the correct roms directory will update any new roms in that directory.

@trekdrop https://github.com/retropie/retropie-setup/wiki/runcommand#adding-custom-launching-images

@zmanz You are on the right track with all/retroarch.cfg. That's the starting place to look for keymaps for libretro emulators. In addition, you could look at configs that might also have key mapping in them according to the emulator. So, mame-libretro/retroarch.cfg would be next, assuming you placed roms in the corresponding folder. arcade/retroarch.cfg if you are using the arcade folder. You get the idea.

However, this brings up a less common issue when using a keyboard controller. . . mame2003 and possibly other lr emulators accept inputs via the "virtual" retropad controllers, but it ALSO SIMULTANEOUSLY accepts raw keyboard inputs. That's why you see both a key and a retropad referenced in the MAME GUI (in game menu brought up with <TAB>) when you are remapping in there. In other words, it's possible to have the retropad mapped in the retroarch.cfg file and have that be in direct conflict with the actual raw keypress that is setup inside MAME2003.

You could go into the MAME GUI and try to remap keys, but the layers of controls and remapping can get pretty confusing!

Here's a post from a while back where some of these details are described. It might be worth a read.

@columboscoat said in Any way to disable or hide the yellow controller message when launching a ROM?:

In what way is your solution better than using the RetroArch GUI?

Now I'm at my laptop and I'm able (have patience) to type better than on my Android phone...

My solution pleases my own taste because when using RGUI RetroArch dumps the current status of every single option of the running instance in the retroarch.cfg, overwriting the previous content. All those useful comments explaining what the options do will disappear.

We all know that RetroArch documentation is very scarce and scattered. I think that the retroarch.cfg skeleton is a good resource of information about the RetroArch options.

@dankcushions said in Ms. Pacman - Squishy Vertical Screen (lr-mame2003):

hi! hmm, do you have the latest lr-mame2003 ? that change was done in the last few weeks so won't be in your image, and possibly not in the binaries either. you probably have to install lr-mame2003 from source (takes about 40 minutes).

https://github.com/retropie/retropie-setup/wiki/updating-retropie#updatinginstalling-individual-packages

Updating from source did the trick! Bless you, very much appreciated. ^_^

@pawpie try to follow these steps I'm talking here:

https://retropie.org.uk/forum/topic/2719/keyboard-stopped-working-after-i-played-around-in-the-controller-config-in-rtgui/2

It could simply be a lag issue. I doubt that the Bluetooth receiver in the Pie3 is as robust as the PS4 one. For this reason I don't use more than 2 PS3 wireless controllers at a time.

The only related issue I could find is this one, but that's more about power draw from the controllers than Bluetooth lag:

https://retropie.org.uk/forum/topic/6756/solved-ps1-controllers-random-input

@Shay You may want to check the link in my signature. I just made a quick video about this right before Christmas. I am at work right now so everything is blocked but the Enable HD graphincs for N64 video should help you out.

Raspberry Pi 3
Retropie 4.1
USB Keyboard
USB Zettaguard Wireless Dongle
Bluetooth Controller
5V Fan connected to internal pins for overclock

I am also having this issue. I'm using the Zettaguard wireless dongle and I have two XBOX 360 controllers that connected at first... but now will disconnect randomly either during configuration or immediately after exiting a game (if they last that long--it's been awhile since I've actually been able to configure them). Two controllers is an absolute no-go. Won't work at all.

I have wiped my SD card and reinstalled the Retropie 4.1 software to start over and have uninstalled and reinstalled the xpad driver multiple times as well as trying the Xboxdrv driver. Neither work for me. I have a 2.5A power supply that came with my Canakit off Amazon but I have added a fan to the internal pins of the Pi. I usually have a USB keyboard connected as well and right now I've got a bluetooth controller connected so I can at least play one player games. It's a Matricom G-Pad XYBA from Amazon. I've tried three different XBOX controllers with NEW batteries.

So as the XBOX controller sits and flashes at me endlessly, I will occasionally see the text on screen say that the controller connects and is not configured. This will happen multiple times while I'm using my bluetooth controller to play. So it gets a connection but then loses it...SO FRUSTRATING. When I get connected and try to configure the controller, it will lose connection during the "configure input" mode and my system is frozen. The keyboard won't exit out of this screen and I have to pull the plug. ... Is there a way to hard-connect these controllers by editing a CFG file and forcing the Retropie to keep a connection to the controller?

I ran into the same issues as described here. The following steps resolved my problems:

Step 1: autoconfigure your joypads once by starting mupen53plus while having all controllers connected properly Step 2: in opt/retropie/configs/all/autoconfig.cfg -> Disable N64 Hotkey here (this was my biggest catch because it is in the all directory!) Step 3: in opt/retropie/configs/N64/mupen64plus.cfg -> assign the hotkeys and put the mode of all registered joypads from 2 to 0
After this it seems to work for me without any problems. So I hope it helps.

PS: I believe that the WIKI should be updated with Step 1, this is such a catch when trying to follow the WIKI N64 instructions.

Hi!

Yes that's what i mean => Hotkey used in emulator (emulationstation is OK and as you say, don't have/use hotkey)
I read the wiki about the file retroarch.cfg (and already edited this one) but in lr-FBANext, i still have a hotkey active (the one that make the game on "pause") and i wonder if some emulator core configuration file have also some hotkey.
If yes, where are they?