libretro / libretro/RetroArch

SteamDeck/EmuDeck/RetroArch/.srm file not recognized

Open
#15,044 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

[Description of the bug]

Load up a rom (Legacy of Goku 2 GBA) on Steam Deck via Retroarch, play rom until in-game save point, save game. Reload, no save detected in-game, .srm file is available and updated in folder. Retroarch not detecting the game's .srm file.

Expected behavior

[What you expected to happen]

Load up a rom, play until in=game save point. Save. Reload. Load from save-point. Factory reset Steam Deck and reinstall as a fix, didn't change problem. No other forum or thread solution via Google search fixed issue. Save states work fine.

Actual behavior

[What is actually happening]
The in-game save is not being recognized in-game, even though it is updated and present within the folder.

Steps to reproduce the bug
  1. [First step]
    Get a factory resetted Steam Deck or new Steam Deck.
  2. [Second step]
    Install Emudeck/Retroarch
  3. Install/Transfer games (in this case Legacy of Goku 2 GBA)
  4. Configure save locations/directory.
  5. Play game.
  6. Save in-game.
  7. Exit game.
  8. Reload game
Bisect Results

[Try to bisect and tell us when this started happening]

Noticed this when I turned off auto save-state on my game and attempted to load from the in-game save instead of save state. When dying in game the save is detected, when you load the game after exiting anew, it is not detected.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: [version/commit]
  • v1.14.0? The most recent available via Emudeck
Environment information
  • OS: [The operating system you're running]
  • Steam OS
  • Compiler: [In case you are running local builds]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are identified in the report. Start by reproducing the Legacy of Goku 2 save and reload sequence on Steam OS with RetroArch v1.14.0, then trace save-file detection; done means the in-game save is recognized after restarting the game.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.