The -dev version has been recently promoted to stable, so both versions of the EmulationStation package are now identical (for the time being, until more things are added to the new dev).

If ES crashes, the log will not be of much help, but a gdb trace (backtrace) might be helpful to see where exactly (in the code) the crash occurs. If you can reliably reproduce the crash, then it might be worth using gdb and capture the trace:

gdb -q /opt/retropie/supplementary/emulationstation-dev/emulationstation - ex run # if there's any crash, gdb will report it and show a prompt thread apply all bt

@pjft said in Snaps/Video Issue with EmulationStation (V2.10.0RP-DEV):

Should be fixed now - thanks.

Confirmed, this is fixed. Always grateful @pjft
Thank you

@reborn1840 said in I put retropie on raspbian,but Basic installation error.:

@mitu PING google.com (8.7.198.46) 56(84) bytes of data.

That's not saying much - do you get a reply back ? Is the connection working ? Can you install a simple package via apt get ?

@retropi19 git clone --branch fkms_rpi4 --depth=1 https://github.com/RetroPie/RetroPie-Setup.git

I'm not an expert in overvclocking, but if the same values have been working without issues, on the same PI, they should be ok with the new version.

@mitu said in Removed emulationstation-dev help:

@paffley Just install Emulationstation (the regular package) from the core packages section.

Thanks @mitu

I installed a fresh ES from binary then had to re-add es_systems.cfg content from an old backup I had (modified).

All working now thank you! keep up the super work!

@SeraphisCain The build/install script for the package is not updated right now, you'll need to have a bit more patience - it's not something on your end.

hi @pjft , I think I found it. When all items in the retropie system (i.e audio, bluetooth, wifi etc) are set to hidden, this causes the crash as described above. if you have at least 1 item set to not hidden, it then works fine.

Hope this helps.

@tomaz Thanks for taking a look.

@mitu the emulated chroot is created via RetroPie-Setup. See admin/image module. It's created from raspbian lite image, so it's identical to a real install which is good for catching problems and dependency issues.

It's used for building the images too which uses qemu again on a pc.

@pjft I refer to the output result ;) Really no idea?
If I want to launch CAPCOM/TESTFILE.test then the output is

/home/pi/RetroPie/roms/123456/CAPCOM/TESTFILE.test segacd /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-picodrive/picodrive_libretro.so --config /opt/retropie/configs/segacd/retroarch.cfg "/home/pi/RetroPie/roms/123456/CAPCOM/TESTFILE.test" Line is ROMname+it's path as in Gamelist... Is Emulatorcall is command call via runcommand.sh

And yes you are totally right... how to find correct emulator call :) But with a bit of investigation it is no problem. But you are totally right that are just cases no user will run in this. But I just want to show what is possible and with the knowledge collected in the last few days it seems absolutly possible to give ES the right push.

So hold on:

Consider if you terminate/shorten 123456/ in the string then you may have the full path of the rom ;) and now compare it to es_systems.cfg? We can parse the system out ;) and then ..... voila a launching abilty via folder navigation :)

In fact I won't use 123456/ give to more a stylish name hidden/, toxxic/or just vvaste/ :D I'm joking but it should work...

@theoneandonly Here is what I did:

Download RetroPie image (from zip)

Extract file

Format SD card

Use Win32IDskImager to write image to SD card

Boot into RetroPie

Configure PS3 controller

Copy roms using WinSCP

Reboot Emulationstation

Play

@kbronctjr You can also set it so it displays only the favourites from each system.