Okay, so after some more searching I found out that the screen I'm seeing is the Raspberry Pi bootloader. I can disable it's appearance by editing it's configuration but I'm still concerned about the error message.

Should I worry it can't find "recovery.elf" and "recovery4.elf"?

By the way, I can still boot into RetroPie just fine play games.

@g30ff Thanks. The latter was it. Much appreciated!

@lostless oh

We don't support preloaded/3rd party images. Install RetroPie from the image provided at https://retropie.org.uk/download and see if you still have this issue.

@hairdyeguy said in Is it possible to save multiple wifi networks on retropie?:

Just to be clear, when you said boot partition, you meant the extra "drive" that appears on windows and can be accessed on windows, not the folder inside retropie, right?

Yes, that one.

@grimdanfango said in Location of joystick configuration files?:

Should the 2 files be the same?

No, they have a different syntax. But instead of bumping an old topic, please open a new topic and explain your problem, adding some info about your setup - as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

@cargorunner And as another tip - be careful editing your cfg files in windows. Windows uses both line feed and carriage return characters at the end of a line. If your custom list of roms contains carriage return characters then it is treated as an empty list by emulation station. You can check your cfg file using Nopepad++ and viewing special characters. For your cfg file to work in emulation station there must ONLY be a line feed at the end of each line.

As well as the usual Zelda, Sonic and Mario lists I used the player's rating scores in Launchbox to create "Top 50" lists by genre across all systems and they are good fun to look at and play through. I have really enjoyed the custom lists feature on my retropie.

When you update, you have a message stating that your current OS version is no longer supported, since the Raspbian version used by your system is too old (based on the Debian 'Jessie' release, which hasn't seen any updates in the last 3 years).
To get updates, you need to re-install your system using a recent RetroPie image (4.7.1). You can backup your ROMs and configurations from the existing image before using the new image, then transfer them back to your new installed system - see https://retropie.org.uk/docs/Updating-RetroPie/#backup-option-2.

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

@mitu said in Qix (lr-2003-Plus) .78 roms (unmerged):

@agrajag said in Qix (lr-2003-Plus) .78 roms (unmerged):

Thank you guys for all the assistance. I have NO idea what step created those huge .cfg files. I'll have to keep an eye out for that.

You used 'Save Configuration' in RetroArch's RGUI. Either that or you enabled 'Save Configuration on Exit' from the RGUI.

That is ABSOLUTELY it. I've been trying to figure out (without luck) through trial and ERROR, how to get to where I can cut off the initial post period of some of the roms (like Defender) and auto-load the "clean" state as I used to do on my PC version of MAME.

Wow. Glad to have a solution and a reason.

@kurnis

please fill out https://retropie.org.uk/forum/topic/3/read-this-first when seeking support.

you're on the right track - you need to edit the file. this is the way to change the hotkey combos.

I have tried the file manager in retropie but when I put in sudo nano /opt/retropie/configs/all/retroarch-joypads/Microsoft X-box 360 pad.cfg
the file comes up blank.

wrong path. it will be within /opt/retropie/configs/all/retroarch/autoconfig

what is returned if you input the following into the command line?
ls -l /opt/retropie/configs/all/retroarch/autoconfig

i am guessing your path is

/opt/retropie/configs/all/retroarch/autoconfig/Microsoft\ X-box\ 360\ pad.cfg

note you need slashes for files with spaces in them, or you can surround the whole path with quotes)

also, you shouldn't use for sudo for this kind of thing. no need.

I went back to looking into this again today. I've seen a bunch of threads around where people talk about vlc and using kms for hardware acceleration, so it seems like it is maybe supposed to work?

I captured the output from running it. The output looks identical regardless of whether I'm using FKMS or KMS. With FKMS, the image correctly shows on the screen (either hdmi0 or hdmi1, whatever I specify). With KMS, the output is the same, but the screen still just displays the terminal, nothing else shows up on either display.

Is there some other place I can look for errors, some other log file maybe?

Here's what the output is:

$ cvlc /home/pi/PieMarquee2/marquee/system/snes.png VLC media player 3.0.12 Vetinari (revision 3.0.12-1-0-gd147bb5e7e) [015a11d0] vlcpulse audio output error: PulseAudio server connection failure: Connection refused [015a2ac8] dbus interface error: Failed to connect to the D-Bus session daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 [015a2ac8] main interface error: no suitable interface module [01528b58] main libvlc error: interface "dbus,none" initialization failed [015bc2a0] main interface error: no suitable interface module [01528b58] main libvlc error: interface "globalhotkeys,none" initialization failed [015bc2a0] dummy interface: using the dummy interface module... [aab014b0] gles2 generic error: parent window not available [aab00ca0] mmal_xsplitter vout display error: Failed to open Xsplitter:opengles2 module [aab014b0] xcb generic error: window not available [aab00ca0] mmal_xsplitter vout display error: Failed to open Xsplitter:xcb_x11 module

@ian_uk90 said in Shaders causing performance issues:

I’ve changed this to 1080p in the launch menu and now all games are running perfectly with shaders on!
Can anyone recommend an optimum resolution? Interested to see if any of the others may make further improvements.

1080p60 is the optimum really. any lower may increase performance if gpu is the bottleneck, but if it's already full speed it's not going to matter.

also, the crt scanline shaders require ~4 vertical pixels per emulated pixel for the scanlines to look decent, and 240x4=960, so 1080 is near the typical limit anyway.

finally, lower resolutions = more obvious scaling artefacts.

perhaps some of this info should be added to https://retropie.org.uk/docs/Shaders-and-Smoothing/ - will try and do this at some point today!

@tmoe01 said in Issue launching ROMs:

... then goes black again before returning to Retropie.

Using the desktop is not supported on Raspbian/Raspberry Pi, start EmulationStation at boot (from the terminal) and not from a desktop session. More details how to configure that here.

@dankcushions My main worry was that the msu-1 file will get entangled with other files, especially if I was to add ,ore msu hacks, but this is more of my paranoia. I also thought it would be more tidy, but if it adds more clicks and I can't use lr-snes9x anyway, I guess I'll pass.
Thanks for your help!