es_systems.cfg empty!

[BuZz]

that file will override the /etc/emulationstation/es_systems.cfg - if you have a full config file in /etc/emulationstation and you don't want to manually "manage" it yourself - remove the one in /opt/retropie/configs/all/emulationstation/es_systems.cfg

[medicalengineer]

@BuZz uhm. I could have another look at it, but I didn't see any es_systems file in that directory. It is up and running with the es_systems i manually typed in some systems, and then updated trough RetroPie-Setup menu.

[BuZz]

it should be unless it was removed/deleted. If you update all installed packages from the retropie-setup menu it will be recreated with the correct systems. You don't need to keep another copy unless you want to manually manage it.

[DrMaxwell]

Or someone could just upload the file for you to mv into the directory and solve your problem.

[BuZz]

@DrMaxwell The file is dynamic - differs depending on what a user has installed.

[DrMaxwell]

@BuZz said in es_systems.cfg empty!:

@DrMaxwell The file is dynamic - differs depending on what a user has installed.

es_systems.cfg is dynamically generated now? So, if I install say lr-mess, then every machine supported by the mess core will be generated in the es_systems.cfg as a system?

[edmaul69]

@BuZz this reminds me, somehow my roms changed to root and not home. I had to give user pi permissions to /home/pi/ to be able to move back to that but the es_systems.cfg in /etc/ keeps setting the roms in root. Not a big deal because i manually manage my systems in opt but would like to fix it if possible.

[BuZz]

@DrMaxwell No. I didn't say that. But if you have only 2 emulators installed, only the relevent systems will be set in that file.

[BuZz]

@edmaul69 Not sure what you mean - start a new topic perhaps ?

[DrMaxwell]

@BuZz I guess I hadn't noticed; I spend too much time editing the es_systems.cfg to know what was originally there, but it's good to know, thanks.