RetroArch
RetroArch copied to clipboard
Nintendo Switch - Save state options and core information are missing
Description
When a game is loaded from a playlist in a new RetroArch installation, "Save/Load State" options are not visible in the "Quick Menu". There is also not a "Core Information" entry under Main Menu > Information.
It seems like there is either something wrong with the main RetroArch executable, or with the way libretro_path is being set in /retroarch/retroarch-salamander.cfg.
Whatever the issue is, it causes similar symptoms to missing core information files.
Expected behavior
Normally, the "Save State" and "Load State" options should be visible in the "Quick Menu" when a game is running. Also, "Core Information" should be visible under Main Menu > Information. No user intervention should be required.
Actual behavior
The "Save/Load State" options are not visible in the "Quick Menu". Also, "Core Information" is not visible under Main Menu > Information.
Note: Starting with version 1.14, there are no workarounds to deal with this issue. It is simply broken!!!
The following steps are required to fix this:
- Start RetroArch.
- Go to
Main Menu > Load Coreand select a core to load. - Restart RetroArch.
Alternatively:
- Open the
/retroarch/retroarch-salamander.cfgfile in a text editor. - Set
libretro_pathto point to the location of a core. For example,libretro_path = "/retroarch/cores/mgba_libretro_libnx.nro". - Save the file.
- Start RetroArch.
Steps to reproduce the bug
- Set up a fresh copy of RetroArch on the microSD card. Files from previous RetroArch installs must not be present.
- Find some games that can be run by a RetroArch core with save state support. Put them in a devoted directory on the microSD card, like
/retroarch/roms/GBA. (I have only tested GBA and SNES games) - Start RetroArch.
- Go to
Main Menu > Import Content > Scan Directoryand select the directory containing your games. - Load a game from the newly generated playlist. Choose a core if prompted. (I have only tested mGBA and BSNES.)
- Once the game starts running, enter the "Quick Menu". Notice that the "Save State" and "Load State" options are missing.
- Go to
Main Menu > Information. Notice that "Core Information" is missing. - Close RetroArch.
- Open the
/retroarch/retroarch-salamander.cfgfile in a text editor. It should saylibretro_path = "sdmc:/switch/retroarch_switch.nro".
Bisect Results
- RetroArch: 1.12.0
Version/Commit
- RetroArch: 2022-10-27 nightly (194be57)
Environment information
Nintendo Switch
you should label this issue
Still valid for 1.14.0
Have the developers even noticed this issue? I get that you guys may not have time to work on it, but please at least say something...
Is there potentially a problem with PR #13562 that is causing this?
There is no issue. Simply update via the nightly bundle or manually download the /switch/ loader. This is simply a version missmatch between entrypoint and binaries.
Keep in mind that the downloader always pulls nightly, so if theres a breaking change with the stable bundle, everything goes to hell.
There is no issue. Simply update via the nightly bundle or manually download the /switch/ loader. This is simply a version missmatch between entrypoint and binaries.
Keep in mind that the downloader always pulls nightly, so if theres a breaking change with the stable bundle, everything goes to hell.
Ok so where does we download working version for the save states working ? if I understand, the problem from version mismatch between nightly and stable version.
Is there any update regarding this issue? 1.15 and still no fix? I installed fresh Retroarch on a freshly updated Switch with newest atmosphere - no quick save options (of course turned on in settings).
Hey guys any update on the issue?
Same for me Save state is still missing for me Workaround is to load the core manually
This error is still happening in the latest version.
If the devs are not willing to correct the problem, is there any guidance on where the issue is coming from? e.g., if we can download a working build from the github and manually install it, that would be preferable, as I've been dealing with the issue for over a year now.
@dmzkrsk @m4xw @nerirififi @azimaxx @namnq-sipher @FabiV7 @retropele
The issue appears to be fixed as of version 1.20.0. I tested several cores and they all worked as expected.