libretro / libretro/RetroArch

Azahar Core - Doesn't remember last save state number

Open
#19,065 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

Is there an existing issue for this?
  • This is a bug in RetroArch frontend
  • I have searched the existing issues
Description

For all other built in cores, whenever I have played a game and saved/loaded states, when I close RetroArch and play the game again later, it remembers the save slot I last saved to. With Azahar core, if I had saved on slot 10 last then close RetroArch and reopen later, it is back on slot 0.

Expected behavior

Reopening a game with the azahar core should remember the last save slot you used instead of going back to 0.

Steps to reproduce the bug
  1. Open a 3ds game with Azahar Core
  2. Save a state (like at slot 10)
  3. Close RetroArch
  4. Reopen RetroArch and open the same game
  5. Save slot will be at 0 instead of the slot you saved in step 2.
Version/Commit

d0fd865

Bisect Results

No response

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system

Windows 11

Affected Cores

Azahar

Environment information

No response

Relevant log output

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 file or test is named in the report. Start by reproducing the Azahar-core save-state flow on the reported Windows setup, then trace where the selected slot is initialized and persisted when the game closes. Done means reopening the same game restores the last-used slot instead of resetting it to 0.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.