libretro / libretro/RetroArch

[macOS] Saving - Add per core name for Saves/States option

Open
#16,539 0 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 I want to congrate we are finally on AppStore.
This is really a dream come true and belows are some of my experience so far.

I tried cloud sync to my home NAS and things are working great.
Just macOS version RetroArch seems missing saving Saves/States to core name folder.
For example - PPSSPP
iOS: With option on, saves to PPSSPP folder, with option off, saves to root folder
macOS: Saves to root/PSP folder

For now it seems no configuration will let both platforms sync to one shared fold.
Windows version may be either way, gotta check it later.

In addition, can we also add "Save state" as a trigger to initiate cloud sync?
Sometimes when I finish playing, I just save state then close the app.
But this way it won't trigger cloud sync immediately, and if I launch from another device now it won't have my current save state.
I know we can trigger it by closing content, but it is just not that strait forward.

Also, is it possible to separate or add individual save box for "Auto save" saves?
I understand we have option to auto +1 slot for each auto save.
But when using auto save, I prefer it as an safe guard option in case I forgot to save.
But I don't want it to be blended into my manual saves.
When they are in the same area, it is hard for managing.

Overall, the iOS release is a big success I can say.
Emulator games are one of the biggest missing piece I missed since switching from Android.
Great jobs!

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

The issue names no files or tests and combines per-core save folders, save-state cloud-sync triggers, and separate auto-save storage. Start by locating the macOS save-path and cloud-sync implementations, then confirm the intended scope with maintainers. Done would require an agreed design and tests covering each requested behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, macos
Domain
cloud, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.