It tells you to use raspi-config. You can run it by sudo raspi-config (sudo runs it as root = administrator).

@g0nz0uk Yeah that option didn't make any improvements for me either.

Here's a link to the shared backdrop worksheet that I created: https://docs.google.com/spreadsheets/d/1IrWY23hIjK30ND-7ZTsxeR5b4wsHhKSA0pfb3CSRlJY/edit?usp=sharing

An easy way to replace the artwork location in the gamelist.xml with another / new one is the sed command (stream editor). This example changes the video directory from the relative path ./media/videos/ to the absolute path /mnt/artwork/videos/:

cp gamelist.xml gamelist.xml.backup # make a backup in case something goes wrong sed -i 's#<video>./media/#<video>/mnt/artwork/#g' gamelist.xml

The part in single quotes does the actual sed-magic:
s(earch)#[old string]#[new string]#g(lobally, i.e. all occurences)

This works for every other path, just change <video> to <image>, <marquee> etc. Omitting the artwork tag before the path will change any occurence in the file, e.g. if the whole artwork is located in another place.

Execute man sed in the command line to get the manpage (manual page) of this tool, or search the web for myriads of examples.

Welcome to this forum.

For RetroArch cores, see https://retropie.org.uk/docs/RetroArch-Configuration/#hardcoded-configurations. Besides, that applies to the official RetroPie image. Third-party images may have other config hierarchies and are not supported here for that reason (among others).

Other emulators are not standardised and may save their configurations in different places. Which emulators are you exactly interested in?

OK.. I fixed the issue, but this is a little odd.
Apparently, Controller 1 (Player 1) has to be in USB1 on these 3040's, Controller 2 (Player 2) in USB2, etc, etc.
Is this a unique situation for the 3040 or is this a universally known fact in RetroPie land? If it is, then I apologize for not doing more research.

This may just me being a little more Windows oriented than Linux oriented, but does it really matter which slot the controllers are plugged into? I'd think that the programming of the controllers would follow the unique ID and not care about the USB Slot at all.

Thoughts?

@hostolis Yeah it was the round white “Xbox” button on top. How did you uninstall it and install the neo version?

@mitu Thanks!

Everything working good now! :D

@xtv said in Read psx roms off SD card & USB:

One solution could be splitting this into two subdirectories, like A-J and K-Z, one of them being a symlink to the USB drive.

That would be a simple visual solution to "hide" the separate-location structure. You could also split it on release year or franchise to help hide the fact.

@Hillbilly The page you have linked for your display is their whole lineup so I'm not sure which one you have, but judging by your config it should be an easy fix. I have a similar display that they give me almost identical settings with.

The main issue is that you've been given a bunch of text to copy and paste without any explanation from the supplier. To top it off, what they've given you is erroneous and based on an old config. This is a great resource for figuring things out and checking whether your /boot/config.txt settings are valid and have the proper syntax: https://www.raspberrypi.org/documentation/configuration/config-txt/README.md . If you bought it off a place like Amazon, there's a good chance someone has posted the correct options in their review.

Long story short though, you should replace the last section that was added after overscan_scale=1 with:
hdmi_group = 2
hdmi_mode = 87
hdmi_cvt=1024 600 60 6 0 0 0
hdmi_drive = 2

This will properly set the resolution to the display if it indeed the correct resolution by putting the equal signs next to cvt and actually setting the option. group 2, mode 87 lets you set a custom CVT that is 1024x600 resolution @ 60 Hz with a 15:9 (6) aspect ratio and no margins (0), progressive (0), and normal blanking (0) described in https://www.raspberrypi.org/documentation/configuration/config-txt/video.md . I also find it good practice to put each option where they make sense only once so it's less confusing and doesn't cause frustration when you're changing one and then further down the same option is overriding your changes so I would recommend moving them back up into the config.txt to replace the others.

To remove the black bars, you can uncomment (remove the hashmark) from disable_overscan=1. You also more than likely won't need config_hdmi_boost=9 so you can probably comment that out.

Not super versed in audio troubleshooting. If sound is working in games, I would've thought it'd also be working in EmulationStation. Hopefully the previous mention of setting hdmi_drive to 2 will fix that. It's not making little clicks when you move around in the menus? Does changing it around from Auto, Headphones, and HDMI have any difference on whether you can change the volume? You might try using a keyboard to see if that helps or updating RetroPie through Setup.

Imagine you've tried all the Bluetooth options while getting Protocol not available? If you're trying to connect to speakers or headphones you'll probably have to follow a tutorial to add that functionality. I don't know if things have changed with the Pi 4, but I remember being rather frustrated when I finally got it to work and just started over with a new RetroPie image without it.

I hope at least the part explaining the config.txt options has been helpful to you.

Many 3D arcade titles still struggle on the pi 4. Unfortunately I think we are stuck using the ports for virtua racing. The saturn port is closest to the arcade version and runs pretty good using lr-yabasanshiro. You can get the experimental script module for it here: https://github.com/RetroPie/RetroPie-Setup/pull/3132 (it is not officially a part of retropie yet but you can test it out like I have been).

This issue also happens when using an 8BitDo bluetooth controller on amiberry and mame-mame4all.

@Julchak did you get any further with this? I have the exact same problem at the moment

I couldn't get speaker-test to work, or aplay. alsamixer had volume.

I ended up just re-imaging the SD card with a fresh copy of RetroPie. This fixed my issue. All ROMs I've played have had appropriate audio.

@Stefan2902 Did it work?