@Slick I suggest opening a separate topic with recommended information: https://retropie.org.uk/forum/topic/3/read-this-first

@TPR said in Does the Pi keep in ongoing log in case of a crash?:

@retropieuser555 Still trying to figure this one out. Any help on how I can get verbose logging in retroarch to stay on when I load a game?

Just in case anyone ever needed the answer to this, I added the following to my retroarch.cfg file in my /config/gc folder and this worked:

log_verbosity = "true"
log_to_file = "true"
log_to_file_timestamp = "true"

Note this was the only fix that I found that would force logging verbosity stay on for me.

@sugarfree FIXED IT
Turns out uninstalling redream does not clear the config files. manually going to opt/retropie/configs/dreamcast and clearing everything then removing and reinstalling redream though retropie setup has seemingly fixed it. redream menu now opens in game.

@sleve_mcdichael Thanks. This has been merged now.

@mitu said in GZDoom crash (Opengl 3.3 needed):

+vid_preferbackend 3

Yes that will make it work. Now will it work for that wad. I don't know.

My hang up when I had a script in my collection. Was it was a unsupported version for certain wads.

There's no resolution related setting in EmulationStation - are you sure you haven't set-up the resolution in your desktop ?
Please post the EmulationStation log taken after starting EmulationStation with

emulationstation --debug

With what games do you have this issue ? Can you try with lr-scummvm (experimental packages) to see if the games are working here ? I suggest also to update your system if you haven't done it.

Edit: I just remember something from the day that was using RPi3. Can you change the Graphic mode to OpenGL in the ScummVM gui and try again the games that don't run?

I was able to convert my .srm save file from lr-mupen64plus-next to an .sra file with this online tool.

https://drehren.github.io/ramp64-convert-web/

I then copied the .sra file into /opt/retropie/configs/n64/mupen64plus/save/

Then I launched ocarina of time with mupen64plus-GLideN64 and played it nonstop for about 2 hours without any crashes or major issues. GLideN64 may have had a few more video glitches than lr-mupen64plus-next was having, but not a single crash for that entire period of time, and that was picking up the game where I left off playing with lr-mupen64plus-next.

So it seems that I don't have these crashes with standalone emulators, but do with libretro emulators.

@harelnaveh10 How did you solve it ? Other user that may encounter similar problems may learn something - so as we, that tried to diagnose and provide assistance.

@mitu Ahhh on the keyboard to be PAIRED? No, I did not understand. Thanks, I'll try that.

edit: of course, it now works. I can't quite believe I didn't understand that part of the instructions haha

So most likely the USB hub is disconnecting at some point and EmulationStation crashes during that moment. Can you try and get a separately powered USB HUB ? Or perhaps a newer PC, since the one you have is more than 10 years old ?

It's a bug, but something that shouldn't affect many users since it wouldn't occur without this symlink loop. It's probably affecting also the reading of the ROM/game folders, which would make EmulationStation freeze on start-up in this kind of scenario.

@lostless thank you so much for the reply as I am new to the retropie community am bit of a bit of a noob to retropie and the ins and outs but I can get a keyboard and a cheap laptop tomorrow then what steps do I take thank you again
**

@retropieuser555 I got noticeably reduced framerate and frequent audio drop-outs with lr-next on a stock Pi4 w/ no overclock.

@mitu Is there an exact reason for the coredump caused by this renderTextCache? Wsl2 is based on a virtual machine, it should be possible to adjust or fix the code to make retropie run normally in wsl2?

@mitu I fixed retropie by adding some roms

No idea, since I'm not familiar with the installer/script you're using.

@Neo-Rio said in Retroarch build failure on PC:

currently trying to build retroarch fails with an error about "HEAD is now in branch 'retropie-v1.10.0' " and "Error running "git checkout retropie-v.1.12.0"
some patch branch on retropie isn't on github as expected to be or something's going on there.

More likely your local source copy is still present, because v1.10.0 fails to build with Ubuntu 22.04. Clean up the source folder before attempting another install.