Main Menu>Configuration File > Save Current Configuration v. Quick Menu>Overrides>Save Core Overrides

mrmadcatz

Re: Please explain the differences between different overrides and configurations.

I have been Googling this and searching this forum for a definitive answer for the last two days. I ended up having to wipe everything and start from scratch due to some weird issues with .cfg files in the various emulator config folders no longer being able to be saved over when trying to edit via RetroArch. I'm seeing tons of conflicting answers about best ways to save certain settings for a core. Some people say it's best to Save a Core Override, others say it's best to save a Config. To be honest, I can't seem to even find an answer about if the two are doing two different things. It's all very confusing and any clarity or guidance here would be appreciated. I don't want to bork my RetroArch install again w/conflicting .cfg files.

To be clear: What are the differences between Main Menu > Configuration File > Save Current Configuration and Quick Menu>Overrides>Save Core Overrides and what is the intended and appropriate use for each?

Genos98

@mrmadcatz
Save core overrides means it will only affect the specific core/emulator. So for example I wanted to configure a controller input to work only on let's say n64 core then I would just usually save it via save core overrides. If I don't do this then it will revert back to the standard controller settings set by retroarch everytime I open a game.

Save current configuration via retroarch will usually affect how retroarch operates and that will include all the cores. In my case I would usually only save the configuration in retroarch if I'm changing drivers or would tinker around with retroarch's general settings.

Keep in mind that save core overrides will always be prioritized and will rule out retroarch's general core settings.

Digriz

Hi,

Also, what are the pros/cons if any of saving config on exit in the main settings menu?, does this apply to the main retroarch config or the running content core config, again some advocate on most say off.

Cheers.

windg

@digriz said in Main Menu>Configuration File > Save Current Configuration v. Quick Menu>Overrides>Save Core Overrides:

Hi,

Also, what are the pros/cons if any of saving config on exit in the main settings menu?, does this apply to the main retroarch config or the running content core config, again some advocate on most say off.

Cheers.

Avoid to use saving config on exit because it will mess up the retroarch.cfg file . If you want to change something better use the configuration editor.

mrmadcatz

@genos98 said in Main Menu>Configuration File > Save Current Configuration v. Quick Menu>Overrides>Save Core Overrides:

ore overrides will always be prioritized and will rule out retroarch's ge

This makes sense and is super helpful. I think what I was getting confused about is that when I would choose "Save Current Configuration" it was not only available to me when I had a rom running in one of the RA cores, but that it would save the .cfg in the Emulator-specific folder. It being available when emulating and saving it to its own file are why it confused me. I feel like the "Save Current Configuration" almost shouldn't be available when emulation is happening since saving it can cause issues v. core overrides, although I know this is a design choice by RA and not necessarily something that can be resolved/removed just for RetroPie.

Anywa, thank you so much for clarifying a bit! I appreciate it.