@Lolonois said in Emulationstation Shutdown Script Issue:

In ES there is a menuitem Save Metadata, set it to Always. Then you should be able to hard kill ES via shutdown/reboot without losing changes to gamelists / favorites / collections.

BAM!!!

That worked!

Thank you! Not sure how I never noticed that option before! Almost seems like “always” should be the default.

@mitu said in Prevent Emulation Station to read all ROMs when starting:

Note that if you add or remove games, they will not show up/disappear unless you disable this option so that EmulationStation will write the correct/updated gamelist.

As I have all the ROMs I want collected (that's why it takes so long for the EmuStation to read) I will give it a try.
Thanx

Looking at the code, it seems the removal of any (extra) text from the game names is intentional and not a bug, probably to eliminate confusion when the system name is appended.
So if the game is named "Street Figther II' (World)", then in the collection it would be displayed (by default) as "Street Figther II' (arcade)" instead of "Street Figther II' (World) (arcade)". With the Show System Name in Collections option disabled, the game is displayed as "Street Figther II' (World)", since there's no additional (arcade) suffix to be displayed.

Wanted to close this off after I thought about how I wanted to organize this.

Here's what I've done.

I converted all the .bin files into .chd files to save on a little bit of space all around. In roms/psx/ I created a hidden .chd folder where I have subfolders for each game and their respective .chd or .CDX files. In roms/psx/ I have a several .m3u files, one for each game, that each point to the .chd directory, and the individual game folder where the relevant game files are located. This allows me to keep the roms/psx/ relatively clean which is what I was going for.

I really appreciate everyone's help in getting me to clean up the roms directory!

@sirhenrythe5th said in Jump to saved state:

@sleve_mcdichael in this great Museum you have the choice of several points to jump in.
The latest savepoint is just one.
So how can we get to the point of choosing between multiple savepoints to jump in without using hotkeys?
I would try to write commandlines as stated above and add them to the gamelist.

You could use a bash script to copy the desired save state file to the required $SRAM_PATH.auto filename before launching with the savestate_auto_load setting enabled.

@JimmyFromTheBay You can also output that ls command there mentioned earlier. Just type emulationstation to relaunch (just type em and TAB should fill the rest, hopefully).

@Davehhf said in EmulationStation crash when pressing x button:

How do I install emulationstation-dev?

RetroPie-Setup > manage packages > experimental packages > emulationstation-dev

@cdaters Hmm, hitting Start does nothing for me.

@shift838 said in No Movement using MAME or MAME4ALL:

The only issue I seem to be having now is even though I have 2 joystics any game with MAME if selecting 2 player all plays off the first joystick. but so far I have only tested games that had only one joystick. I still need to test games that had multiple joysticks for players to play at the same exact time.

That's completely normal if you've ever played the actual arcade games. The only time you'll have the second controller active is on games where both players play at once.

From the distance/information provided some guesses.

As you state it works most of the time and then the custom collection loading fails: Could be that the threaded loading may have an impact.

To switch the threaded loading: Locate your es_settings.cfg (usually /opt/retropie/configs/all/emulationstation. Spot the entry <bool name="ThreadedLoading" value="<your_value>" /> and bool invert that <your_value> (e.g., true gets false and vice versa).
Then run this config for a while / for several reboots and note if your reported effect still occours.

To avoid the daunting task of re-enabling all of your collections in ES make a copy of <string name="CollectionSystemsCustom" value="yadayada,yabadaba,..."> and keep it in a safe and dry place thus you can restore it if you encounter the effect again. But only do edit your es_settings.cfg while ES is not running. And do not put an extra space between the delimiter (,) if you want to edit collectionnames manually in the editor.

Also make sure you only use ASCII characters for your collection custom-*.cfg files. (But I doubt this is the cause, as the custom collections loading would fail everytime).

Last but not least: The pugixml, which is an external lib to ES and is actually handling every xml in ES (f.i., es_settings.cfg) is a little dated (1.8 from 2016), current is 1.11.
Maybe updating remediates your issue. However, I skimmed over their releasenotes/issue tracker but did not find on a cursory look a bug directly linked to long string reading (i.e., your value of name="CollectionSystemsCustom").

HTH

@sleve_mcdichael said in How do I get rid of emulationstation-dev?:

But yeah, backups are good. I had done something that was causing ES to crash, once in a while, unpredictably, at launch. So I burned a fresh image, hopped on my WiFi, restored my backed-up roms and config files, and I was back in action.

Obv I have backups, but restoring from a backup onto a 256GB SD card takes hours and hours and hours and I try to avoid it wherever possible...

@iandaemon
ok great info I didnt realize that
thank you

@babyboodle said in PulseAudio unable to connect; poor emulator performance issues and menu crashes.:

reset to default settings

If you have reset RetroArch to default settings in the RGUI and then saved the config you have probably set non ideal defaults. Our defaults are not the same as the RetroArch defaults. You should remove /opt/retropie/configs/all/retroarch.cfg and reinstall retroarch from "Manage Packages/Core Packages"

It's a resize issue, I think it's fixed in the development branch of EmulationStation. You can install the dev branch from the experimental section of the packages, it's called emulationstation-dev.

Pressing select is equivalent to the screensaver-start event, sleep is triggered after the configured timeout.

So I found a solution that I think works (at least for me.) I changed the entire configs.hdmi>daphne folder permissions to 555 and when I add a new controller, I get this error:

daphne input.jpg

However it does NOT overwrite my current dapinput.ini file. I can't see anything else in that directory that it would need to write to anyway.

I tested all 17 Daphne games and they all worked and they all kept my controller configs even after configuring a few new controllers so I think this is at least a fix for my situation.

Thanks for the input everyone! It was helpful to put me on the right path!