Before the implementation, I had core overrides for most cores which consisted basically of directory changes for savefiles. When testing this new GUI option, I realized the new cfg override it creates doesn't seem to check for delta on the cfg related to directories, so it just deletes any custom path I made manually. Changing paths from the GUI also doesn't get registered when saving the core override from the GUI.
To reproduce the issue:
- Enable auto-load core overrides on your retroarch.cfg.
- Manually create a core override that changes a directory. For example, create SNES9x.cfg under \config/SNES9x with the following line:
savefile_directory = ":\saves/SNES"
- Load any content with SNES9x. The savefile directory will change (you can check under "Directory" on the GUI.
- Select "Save Core Override" on the GUI.
- Check your SNES9x.cfg under the \config/SNES9x. It will be empty.
Another way of reproducing is, after content load, just manually changing any directory from within the GUI and trying to "Save Core Override". It will save an empty core override, not recognizing any changes made to directories, and directories will reset on content close.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Before the implementation, I had core overrides for most cores which consisted basically of directory changes for savefiles. When testing this new GUI option, I realized the new cfg override it creates doesn't seem to check for delta on the cfg related to directories, so it just deletes any custom path I made manually. Changing paths from the GUI also doesn't get registered when saving the core override from the GUI.
To reproduce the issue:
savefile_directory = ":\saves/SNES"Another way of reproducing is, after content load, just manually changing any directory from within the GUI and trying to "Save Core Override". It will save an empty core override, not recognizing any changes made to directories, and directories will reset on content close.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.