Thanks everyone.
It was due to bad dumps. I had bin files and a .zip romset solved the problem.
The control issue came from the 8bitdo controller. I connected it like a switch pro controller and everything is fine again.
I went further and replaced some of the original roms with dreamcast ports in order to use Redream. Really good perfs now !

@adamantiumpimp said in Stuck on a splashscreen/command prompt!:

@exarkuniv Apologies for my ignorance. Is it the PlayBox part of it that is the rebuild? Sorry I'm just now getting into all of this and am unfamiliar with the lingo.

It is impractical to provide support for a system that neither you nor we know how is configured. *Pre-built, aka third-party (anyone[3] who's not you[2] or the RetroPie project[1]) systems are not supported. The only supported configurations are the official SD images available on the download page or installed on top of an existing OS using the setup script.

We will gladly help you through the process if you'd like to start over with the default image and build a system yourself. Or, you can contact the author of your custom build and ask them to provide support for the system that they have configured.

Hi again.

The above post has solved my problem. I was able to effortlessly pair both controllers by following those instructions. For anyone who is stuck and sees this thread, I believe it was this command that solved the problem: sudo apt install bluez=5.50-1.2~deb10u1+rpt2. After updating the packages and checking the bluetooth status, I still got the Failed error messages, but once I inputted this command they disappeared. Of course, try everything just to be safe.

Thanks for your help!

@mitu Thanks for the reply! I’m not at my Pi at the moment but when I get situated, I’ll give that a shot and report back!

Just add your scripts to the retropie menu, very simple. i never had to make any edits to make it work, just some editing to get the script to have a picture in EmulationStation and description of the script.

If you want the scripts to appear within your Ports, you might need to include .sh with the filetypes that are supported with Ports even though from memory it should already be set up like that (i cant double checking this right now, currently making a backup of my SSD)

If you can see the scripts in EmulationStation but theyre just not executing after selecting them, then you will need to chmod +x your sh files.

@benmclean

The Raspberry PI 4B with 8 GB of RAM. The performance gain is small for gaming because RAM is usually not the bottleneck

Eh? The performance gain past 2GB is zero. Retropie uses around 1GB with swap and all. The extra ram might help with installing emulators from source or if you want to use it as a desktop someday.

You need a compatible power adapter and lots of companies make them.

I only recommend the official psu due to reliability. They are $8US so there shouldn't be a reason to get a 3rd party psu that no one knows how reliable they are.

If you're going with a plain pi4, for a case, I recommend the argon one v2 if you don't want that nespi. It has a fan and converts the microhdmi ports into normal sized ones.

@blboun said in XBox one controller logo button not working in games:

not sure what you mean by that ? how can it work in retroarch ? it still doesn't work when I open any game...

I thought you disabled the Xpadneo driver and the hotkey would start working. Xpadneo maps the SHARE as a key event, that's why I asked for the model and checked whether you're using it or not:

Full support for the Xbox Series X|S controller is present including the share button. This is currently mapped to keyboard event KEY_RECORD and may not work at all for any purpose.

and yes, it says Button 10, not key 10, my bad

OK, that's cleared up, though it doesn't explain why the hotkey doesn't work with it. I have an older Xbox One controller (not S) which has the same layout, but it doesn't have Bluetooth. The Xbox button works as a hotkey, but since it's wired it's not the same thing.

@breadpie If you created a Retropie folder on your USB drive, and are just using it to transfer games, then I think it just transfers the same data as when using Retropie-mount.

Retropie-Mount, meaning the games run from your usb drive, it also transfers BIOS, retropiemenu, roms, and splashscreen info. As far as I know, neither transfer any configs. Screen Shot 2021-08-20 at 3.45.39 PM.png

Can you explain how you fixed this? I've been wrestling with this all day.

I tried multiple solutions suggested here, but to no luck. In the end, I just started the whole installation all over again and it's working fine now. God knows what happened, but it seems re-installing everything seems to have fixed it... weird.

Thanks for the replies everyone!

@skykid said in Despair over controller ports constantly swapping:

I hear setting up Samba on OSX is a ballache, which is why I was looking for an easier option.

It's not, you can access the RetroPie shares from macOS without any issues:

open Finder, select "Go" menu and "Connect to Server". Type smb://retropie and hit "Connect".

@windg
Alrighty! I'll keep playing normally, i'll install duckstation just to see it working
Thanks!

Additional notes:
I installed the duckstation core, i tried playing the game there and swapping discs works perfectly, although it doesn't recognize the CD1 or CD2 extension i had to rename them as .cue files again and change the m3u to reflect the changes

@dankcushions I'm going to do a full update and reinstall of as much as I can right now.

@mcjones9631 said in Ubuntu PC having issues running ROMs:

Controller always gives "✔️ USB Gamepad (121/17) not configured" when in games and games can only be exited from the keyboard

This usually happens when your controller doesn't have a configuration file/profile in RetroArch. If you configured your controller in EmulationStation, a RetroArch configuration file for the controller should be created automatically, unless you turned of the auto-configuration of controllers in ES.

Is you controller working in EmulationStation, after you have completed the input configuration ? Did you disable the auto-configuration in EmulationStation, by any chance ?

@gerry69 Conclusion:

I thank you all for trying to help me!

As I was about to reinstall again (!) I discovered Recalbox as an alternative distro and thought I'd give it a try (forgive me). While on Retropie Vice refused to install, and lr-Vice had to be compiled 3 hours for stuttering results and Sega Mega Drive was unplayable with both emulators, in Recalbox EVERYTHING works perfectly smooth without even the need of setting up or installing anything.

So I hope you all understand that at this point - after at least 20 hours of trying to get Retropie going - I give up and go happily with Recalbox.

Thanks again anyway - cheers!

Ok it is kinda working, it seems I need to do a lot of editing to the github files to make it work nicely with the original retropie install as various default directories are different in this alternative emulationstation.
This isnt as straight forward as I thought it would be lol

You can hit F4 on the ES menu to get to the command line of the Pi. If using Samba or SSH you can get to the file structure on another computer, WIndows for example.

Yeah I use my switch pro controller, I havent done any extra configuration at all and it pairs just fine. Can you try another bluetooth controller? Dualshock 4 or Xbone one controller?

If this is your first time pairing via bluetooth, you might want to check that your bluetooth is working correctly with this command in the terminal:

systemctl status bluetooth.service

Thanks guys, that was exactly the problem. I followed the thread @windg provided, and it worked first time. I really appreciate you guys