RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Save states aren't read after binary based installation 3.6 -> 3.7

    Scheduled Pinned Locked Moved Help and Support
    8 Posts 3 Posters 2.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Arcuza
      last edited by

      Hi,

      After updating from 3.6 to 3.7 the N64 emulator don't read the save states, the SNES emulator does, and the GBA as well.

      I have the exact same runcommand settings now on 3.7 as I had on 3.6.

      When looking in the rom directory, I still have the .sra and .st0 files there.

      Strange though that the rome file is

      Legend of Zelda, The - Ocarina of Time (Europe) (En,Fr,De).n64

      while the saves are

      Legend of Zelda, The - Ocarina of Time (E) (M3) (V1.0) [!].sra
      Legend of Zelda, The - Ocarina of Time (E) (M3) (V1.0) [!].st0

      But hey, it seemed to work on 3.6...

      Do you have an idea what has happened?

      Thank you for your support!

      1 Reply Last reply Reply Quote 0
      • Z
        zerojay
        last edited by zerojay

        You're using a different or renamed ROM is what happened. Nothing changed with savestates between 3.6 and 3.7. If you were using the same ROM, you'd have it named the same as your ROM with a .st0 or .sra at the end.

        A 2 Replies Last reply Reply Quote 0
        • A
          Arcuza @zerojay
          last edited by

          @zerojay Thank you, that's really strange as the only thing I did was to do the upgrade. I never changed file names. What I did not was to rename the saves to give them the same name as the rom, still no luck though. The emulator won't load the files.

          Do you have any idea on how I can let the emulator load the saves or at least troubleshoot what might be wrong?

          Actually I'm quite confused why it worked on 3.6...

          1 Reply Last reply Reply Quote 0
          • A
            Arcuza @zerojay
            last edited by

            @zerojay I suspect the "real" save states are in a different directory, since they didn't have the same name. Is it possible to search for the save state files on the SD card?

            1 Reply Last reply Reply Quote 0
            • dankcushionsD
              dankcushions Global Moderator
              last edited by

              whilst i don't understand how it upgrading would do this, maybe there's something to it: https://retropie.org.uk/forum/topic/355/n64-save-files-are-deleted-after-binary-update

              A 1 Reply Last reply Reply Quote 0
              • A
                Arcuza @dankcushions
                last edited by

                @dankcushions I think I have figured it out. I'm running the standalone version of mupen, which saves under ~/.local/share/mupen64plus/save . So unfortunately I backed up the wrong save file when upgrading.

                However, the rom file is still named as above and the save file as above.

                Legend of Zelda, The Ocarina of Time (Europe) (En,Fr,De).n64

                Legend of Zelda, The - Ocarina of Time (E) (M3) (V1.0) [!].st0

                Isn't that really strange?

                dankcushionsD 1 Reply Last reply Reply Quote 0
                • dankcushionsD
                  dankcushions Global Moderator @Arcuza
                  last edited by

                  @Arcuza

                  @dankcushions I think I have figured it out. I'm running the standalone version of mupen, which saves under ~/.local/share/mupen64plus/save .

                  but i'm using standalone, have valid save files (mario 64 has the stars i've got), but have no files in this directory, but DO have save files in my rom directory?

                  maybe something went wrong with the update? i'm running 3.6

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    Arcuza @dankcushions
                    last edited by

                    @dankcushions Do you know what's really strange? When upgrading I lost the save states from loading on mupen. But now when I copy the save files from the rom directory to the save directory under muper64plus it load the saves again!

                    So, two questions:

                    1. Where are the standalone mupen64plus saves and save states stored? I would say both roms/n64 and mupen64plus/saves since I backed up from roms and restored to saves, and it worked fine. IE it saves to roms/n64 and mupen64plus/saves and loads from mupen64plus/saves only.

                    2. Why do the save file and the roms file have different names? I cannot answer that. It seems like mupen recognizes the rom and saves files with a standard name.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post

                    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.