File size: 2,067 Bytes
123e810 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | # Save states save and load to the wrong save state slot
- Source URL: https://github.com/MiSTer-devel/Gameboy_MiSTer/issues/174
@RobertPeip,
I have found an interesting menu issue that seems to affect all cores save states implemented in them. To reproduce this issue choose a save state slot 2, 3, or 4 and save your settings on the second menu page. Close the core or switch to a different core then come back to the core. The save slot displayed will be what was saved previously. If you choose save or load save state it use slot 1 regardless of what slot is displayed (2,3,4).
I thought I was going crazy until I realized slot 1 was briefly coming up onscreen when trying to load a save state.
I also discovered more strange save state behavior for the cores that use bootX.rom files to auto load an initial game. For Gameboy it's boot2.rom and NES boo1.rom. Save states seem to work until exiting the core then cease to exist upon returning. My guess the core probably doesn't have valid filename to use to store the save state.
## Fetched Issue/PR Details
Title: Save states save and load to the wrong save state slot (#174)
Description: The reporter describes a menu issue affecting save state functionality across multiple cores. When selecting save state slots 2, 3, or 4 and saving settings on the second menu page, the core displays the previously saved slot number upon reopening. However, attempting to save or load always uses slot 1 regardless of the displayed slot. The user observed slot 1 briefly appearing onscreen when loading save states.
Additionally, the reporter notes problematic behavior with cores using boot ROM files (like boot2.rom for Gameboy and boot1.rom for NES). Save states function initially but "cease to exist upon returning" after exiting the core, suggesting the core lacks a valid filename for storing the save state data.
Status: Closed (linked to PR #240)
Reporter: dot-bob
Opened: August 8, 2021
Comments: No comments or additional discussion visible on the page.
Linked Issues: Resolving PR #240.
|