lr-gambatte - Core Does Not Support Save States
-
¯_(ツ)_/¯
-
@AwesomeKingClem said in lr-gambatte - Core Does Not Support Save States:
¯_(ツ)_/¯
lol! Ok so this response at least makes me think I'm not totally crazy. At least I tracked it down. Still have no idea wtf could have caused it.
-
@TPR said in lr-gambatte - Core Does Not Support Save States:
and when when I did the "remove" from the retropie-setup that it didn't remove RA completely and doing an install from source didn't fix this issue until I went in and manually removed those folders?
That's correct, removing a package in RP-Setup does not remove the configs in
/opt/retropie/configs
. They are retained so that they can be re-used if it is installed again later.Initial tests seem to indicate it is working now, but still curious why that happened.
There was likely a setting saved somewhere that was causing the issue. There are any number of ways this can happen, but by removing the config folder and then reinstalling, you have now got back to the default settings.
-
@sleve_mcdichael Yep! Thank you again guys! All the feedback most certainly made me go look and different things and try to trace back to where the issue was coming from.
-
@TPR said in lr-gambatte - Core Does Not Support Save States:
UPDATE!
It was my <console>.cfg file in the /opt/retropie/configs/all/retroarch/config/ folder (...) Any idea why? For example, here is what the Gambatte one says:
[wall-of-text config]
Those files shouldn't exist. They're created when you save certain settings through the RetroArch GUI. They will override and break integration with RetroPie configs. Then they hard-code every setting and don't update values when defaults change underneath. Recommended way to persist settings instead is with configuration editor. (Remaps are one exception, they are fine to save through RetroArch GUI as they save to a different file than these core overrides.)
-
@sleve_mcdichael said in lr-gambatte - Core Does Not Support Save States:
@TPR said in lr-gambatte - Core Does Not Support Save States:
UPDATE!
It was my <console>.cfg file in the /opt/retropie/configs/all/retroarch/config/ folder (...) Any idea why? For example, here is what the Gambatte one says:
[wall-of-text config]
Those files shouldn't exist. They're created when you save certain settings through the RetroArch GUI. They will override and break integration with RetroPie configs. Then they hard-code every setting and don't update values when defaults change underneath. Recommended way to persist settings instead is with configuration editor. (Remaps are one exception, they are fine to save through RetroArch GUI as they save to a different file than these core overrides.)
That is incredibly useful to know! Thank you!
-
@sleve_mcdichael I'm also trying to figure out what I must have done to create those ,cfg files. I can't think of anything I really needed to change with an emulator core or needed it to be hardcoded to any one specific version.
-
@TPR Did you choose 'Save on Exit' or used 'Reset Settings' from the RetroArch's menu ?
EDIT: BTW, to get the RetroPie default
retroarch.cfg
for a system, just reinstall one (if there are many) libretro cores for the system after removing the configuration file. -
@mitu said in lr-gambatte - Core Does Not Support Save States:
@TPR Did you choose 'Save on Exit' or used 'Reset Settings' from the RetroArch's menu ?
I think I just figured it out. Using lr-gambatte as an example, I had gone into the core settings and set the video mode to "full" so it would fill up more of the screen on a 4:3 display and then I went to Overrides > Save Core Overrides to make sure every game loaded up in that video format which created that .cfg file.
So, let's just say for the sake of argument I was looking to do exactly that, is there a better way to make sure each game loads into "full" that using the core overrides?
-
@TPR said in lr-gambatte - Core Does Not Support Save States:
So, let's just say for the sake of argument I was looking to do exactly that, is there a better way to make sure each game loads into "full" that using the core overrides?
You would edit the general
retroarch.cfg
file (not for each core/system) in/opt/retropie/configs/all/retroarch.cfg
and modify the option forvideo_aspect_ratio
(which is what I assume you modified). The option would be automatically set for all libretro cores, without the need to edit each system's configuration. -
@mitu Ha! I was just watching Floob's video linked above and I did exactly what you posted! Thanks again to the team! Your help is always very much appreciated!
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.