Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first. The reason for the crash is probably shown in the emulator log file (/dev/shm/runcommand.log) can you get the files's contents and post it ?

@KN4THX The problem it's not the hotkey, a lot of NES games use the select button for doing things in game. I'm a medium-skilled developer, with some guidance on the retropie bluetooth scripts and stack I could write myself a script which does in background the pairing procedure again, at least with one model, the SN30. If someone is willing to help or pointing me to who ask questions to, i'll be happy to try to write then publish such script.

@scuzzbuster said in ROM Issues - Intermittent weirdness - And Minor Issues: I've cycled some of these ROMS through every MAME emu by holding down the button and using the menu to set a new default Mame EMU with no luck on some if I'm not sure which version the ROM was. This is what I'm saying is your problem. You need to start over and find a matched set for the emulator you wish to use not the other way around. Google search for a "mame2003 0.78 romset" and use it exclusively with mame2003. The link I posted earlier walks you through all of this.

@Lummox-JR So if you're not wanting the Bluetooth USB either, I'd recommend checking this out : https://github.com/RetroPie/RetroPie-Setup/wiki/Sound-Issues#using-a-usb-audio-device

Update: Updated the RetroPie-Setup script and all OS packages and restarted the Pi. This got the Bluetooth to connect (unreliably, it still fails to register about 1/4 of the button pushes I make). Frame rates are still very poor but I think that might just be the state of RetroPie on Pi 4 at the moment.

But... if you're trying to just prevent the message from appearing when you don't have a controller available, the easiest solution is to configure a keyboard as input in EmulationStation. When started, even if there's no controller connected, EmulationStation will skip the welcome message and go right into the system list.

THX! It looks like there was a hidden sign (copy and paste failure)

@Dinsdale Your screenshot shows an error that happens during pairing in the Bluetooth setup - possibly a timeout during the process. Re-connection is handled by the OS, there's no RetroPie script involved afterwards - so I don't think that's the problem. EDIT: you can try and pair the controller manually - see https://approxeng.github.io/approxeng.input/bluetooth.html, the Pairing with Bluetoothctl section).

Press Start to open the Emulationstation menu, then use the Input Configuration entry to re-configure your controller.

Amazing! This did the job!

@a4c8 said in NES30 found but can't connect (details inside): I can start emulationstation afterwards, configure the controller and run games, but after restart they aren't solid anymore and blink instead. I tried setting the mode to boot or background, as described, but with no change. I get the same behaviour with another model, they don't re-pair automatically if you restart RetroPie without shutting them down first. If you restart RetroPie, shutdown the controller and then start it up again, they should re-pair and the light will turn solid.

@Pundan I did not really look forward to rebuild the entire Retropie installation with thousands of ROMs (pretty much had every system there is scraped and sorted) just for this I feel your pain. After having to go through that I started storing a big chunk of ROMs on an USB flash drive. It makes rebuilding so much easier! I've also tried storing them on an external USB hard drive (non solid state) and they usually work great with smaller ROMs but with like the larger PSX games, if you're playing a game and the hard drive spins down and then the emulator needs to read the game disc image again, most times it will crash because it times out before the hard drive can spin back up, so in other words, use a solid state drive! Running ROMs from a USB drive: https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/ Loading roms from USB harddrive: https://retropie.org.uk/forum/topic/7780/loading-roms-from-usb-harddrive

I went a slightly different route with mine. I went for a thin build: INITIAL IDEA= and HALF DONE= .

Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Yes, it's possible - see the docs on how to pair and connect them https://retropie.org.uk/docs/PS3-Controller/ https://retropie.org.uk/docs/PS4-Controller/

@mitu Thanks for the info. Sorry for jumping in. My brain didn't register that this was a RPi4 specific thread. FWIW, Turns out my issue was xpadneo README's instructions for raspbian. Installing the raspberrypi-kernel-headers package on 4.5.1 causes the buster headers to be installed on top of the stretch ones (which are already present on the retropie image).

I don't have a HDD attached at this time. I won't until Kodi is operational on the Pi 4. I had to use the manual set up to get emulationstation up and running. I am not sure it fully took. I looked under "retroarch" in the menu and see no core, even after I have installed cores.

You should try out the xpadneo driver: https://github.com/atar-axis/xpadneo see the section under install. This is specifically designed to work with the bluetooth xbox one controller model 1708.