libretro / libretro/RetroArch

[Feature Request] Manually flush save

Open
#18,239 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hello :) As a new user, I just got to realize that the saves are not flushed to disc until you leave/reset the game. So if the game crashes or the battery runs out you lose your progress.

That is fine, I know that the reason for that is that it seems some games access the saveRAM all the time and so there would be too much disc access.

I also know that there is an option to save periodically and it works well, thanks for that!

But I'd like to propose an option to manually select a button and flush the saveRAM. That would save battery and also make the disc last longer with fewer accesses. It even could be tied to a shortcut + a notification.

As a reddit user suggested, it may be hidden by default and enabled when toggling the option
Settings>User Interface>Show Advanced Settings.

Thanks so much for the amazing application! :)

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

Begin by tracing the existing periodic-save option and the saveRAM flush path, then inspect Settings > User Interface > Show Advanced Settings. Done means a configurable manual control or shortcut flushes saveRAM, with the requested notification and without changing periodic-save behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.