Run emulationstation --debug from a terminal window and post the output. My guess is that there's no HW accelerated GL support, but the log output would help confirming the assumption.

@sirhenrythe5th Ill Uninstall ReDream and try Flycast and see if the same thing happens

@rtarroyo BTW

The internal switch is turned on to safe shutdown and im running the latest version of Retropie, installed it today

@dankcushions I just played through the entire first mission without it crashing. This definitely fixed the problem. Thanks a lot!

You didn't mention how installed RetroPie.

I'd like to fully admit I'm a moron...
The cord wasn't fully plugged in which is why my recording device and etc were having issue detecting the raspberry pi..

I am so so so sorry for wasting your time.
e2fdd77a-4b4c-4d68-875f-3c2ed67dd43a-image.png

@sad_muso said in Pi 4 Retropie issues:

Hi,

I've just upgraded to a Pi 4 and performed a fresh install of the latest Pi 4 install file (md5: 9154d998cba5219ddf23de46d8845f6c). I know this is still a beta, but I've experienced a couple of quite big issues. Is it the build or something I'm doing?

WiFi search initially found about 8 of my SSID name (for some reason). I couldn't connect to any, but now it can't find any SSIDs at all Retropie has crashed on a few occasions (with 'Retropie has crashed' message) Can't change resolution from 4k to 1080p because I can't get into the resolution menu - it just stays at the same menu level

Have I somehow got the wrong image or copied it to the SD card incorrectly?

I had similar issues

WiFi - I created the file pre setup so didn't have this, however did notice a lot of repeats in Bluetooth when setting up my sixaxis for PS3.

Didn't get crashing

Raspi-config resolution... I couldn't get into this either although I did get a workaround which helped.

Never mind I have fixed it. I used the MC command and changed the word kidmode to full in the /home/pi/.emulationstation/es_settings.cfg.

@spacepilot7132 are you using an official RetroPie image? Anytime you have odd behavior you should turn off your overclocking and retest.

@Spectreman

Just wanted to chime in here and say that I had this same exact problem, and this same exact solution fixed it for me. And the weird thing is that I definitely had 5200 stuff working previously. This problem only just started happening for me. Very weird.

@tackett1980 Cool.. you know, I'm just gonna say the difference in bios files might be a wild goose chase.. so only search for mine if you're really bored :P Hopefully the reicast folks will address the build issue with the stable branch on rpi3.

I have an rpi4 with retropie running, and was able to play for several hours with no issues.
I started with a base raspian image, and followed these instructions here to install retropie:
https://github.com/RetroPie/RetroPie-Setup/wiki/Manual-Installation

Please don't post links to rom/copyrighted material sites - https://retropie.org.uk/forum/topic/2/forum-rules.

@Efriim that was it - thanks a lot!!! I just cleared selected mode

@mitu As the 16.04 still has support until 2021 I will still keep with it a little bit and continue reading the comments, if in a while there is nothing very negative about the 18.04 I upgrade. Even because this pc is an old Dual-Core Celeron that I use as a retro console and to watch some videos.

@Superman550 emulationstation-dev replaces emulationstation when installed, you don't have to do anything to make it start. Do report if you still encounter this error.

@mitu @kyuzumaki

Curiously, I have something similar on 18.04.1, which is also a recent thing. I just stumbled across this post but already made my own thread with my own findings this evening:
https://retropie.org.uk/forum/topic/21139/error-and-gui-terminates-back-to-es-when-launching-retropie-setup-direct-on-machine-libudev-but-ssh-is-ok

Let me know if I can help grab any further information here to get this resolved.

Thanks!

Please provide us with the information that is asked for in https://retropie.org.uk/forum/topic/3/read-this-first and with the exact wording of the crash screen (preferably in form of a screenshot).

@dayvolk Just to confirm you are using the correct retropie image for the pi3?