Error Save Retroarch configs: RetroArch 1.12.0 (Git d6deee4)
-
This post is deleted! -
This post is deleted! -
@mitu said in Error Save Retroarch configs: RetroArch 1.12.0 (Git d6deee4):
Does this happen for all systems, or just for
nes
? Post the/opt/retropie/configs/nes/retroarch.cfg
file also on pastebin.com.1.12.0 (Git d6deee4), if I downgrade to the previous version, 1.11.1, the settings are saved normally and without problems.
RetroPie's previous version was 1.10.0, version 1.11.1 was not packaged by RetroPie - how did you install it ? Also, how did you install
lr-fceumm-mod.so
? That's not a core file that RetroPie installs.
Your setup is quite different from standard RetroPie installation - are you using a 3rd party image ?Hello, thanks for your willingness to help.
Happens with all LR emulators.
Post the
/opt/retropie/configs/nes/retroarch.cfg
file also on pastebin.com:RetroPie's previous version was 1.10.0, version 1.11.1 was not packaged by RetroPie - how did you install it ?
Editing the file: retroarch.sh
In path: home/pi/RetroPie-Setup/scriptmodules/emulators/
Also, how did you install
lr-fceumm-mod.so
? That's not a core file that RetroPie installs.Your setup is quite different from standard RetroPie installation - are you using a 3rd party image ?
No, it's the original image with the addition of extra scripts, through the https://github.com/Exarkuniv/RetroPie-Extra
And a few more settings that I made myself.Anyway, it worked before, and I never had any problems.
-
@wmarcio said in Error Save Retroarch configs: RetroArch 1.12.0 (Git d6deee4):
Anyway, it worked before, and I never had any problems.
I don't think it worked before - the configuration file (
retroarch.cfg
) you posted is not a full config, so RetroArch wasn't saving on exit the configuration as you think (with version 1.11.1). Probably in the new version it correctly logs that it cannot save the config, while in the previous version was not logging this. I'd check the permissions on the file.As a side note, you may be better running without
config_save_on_exit = true
, since it wasn't working before, so it's not really needed for your config. Though I'd probably remove thelibretro_directory
option from the file, since it's added automatically at runtime byruncommand
.Note that in newer versions, running a libretro core without a corresponding
.info
file will lead to not being able to use save/load states. Since you're using a non-standard libretro core (fceumm-mod
), that may affect the options present in the quick menu or the functionality of the core. -
@mitu Hello, thanks for the clarifications.
Arriving home tonight, I'll take a look, actually I'm already wanting to migrate all to a USB SSD.
In any case, I will do some tests beforehand and I will delete the configuration files, thinking that a new one will be created after updating the retroarch to the last available version. -
@wmarcio said in Error Save Retroarch configs: RetroArch 1.12.0 (Git d6deee4):
In any case, I will do some tests beforehand and I will delete the configuration files, thinking that a new one will be created after updating the retroarch to the last available version.
No, it will not be created automatically when you upgrade RetroArch and I'd advise agains removing the file straight away. The
retroarch.cfg
for a system is created only when a compatible core is installed/updated. -
@wmarcio What does that fceumm mod offer over the normal one? Wouldn't it be better to use mesen? I'm not sure if it's usable on a pi3b+.
-
@wmarcio Do you have a link to the the latest redream update that works with WINCE and can be downloaded with my retropie?
-
@duglor please stop posting the same reply in multiple unrelated threads.
-
-
-
@mitu I knew something was wrong, so I'm sticking with version 11.1.1.
This bug has been happening to me for some time, but I had no time to try to ask for help, and only in November did I decide to come to the forum. -
@wmarcio The RetroArch version in RetroPie has been updated recently, the new version (1.15) should have a fix for the configuration saving issue.
-
@mitu Hello how are you. Thanks tomorrow I will test. Thanks for reminding of me.
-
@mitu It worked, in fact updating retroarch to version 1.15.0 fixed the issue.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.