SNES Save State Test core

[paulbnl]

Basically when loading the core, loading save states only seems to work after you create a save state. This behavior did not occur with the previous save state core.

Thanks for your report. I think I know what this is. You should also be able to work around this by loading another slot first, even if that slot does not contain a save state.

[MARl0]

Basically when loading the core, loading save states only seems to work after you create a save state. This behavior did not occur with the previous save state core.

Thanks for your report. I think I know what this is. You should also be able to work around this by loading another slot first, even if that slot does not contain a save state.

Nice, that work around does indeed work! Definitely better than what my work around was. Looking forward to further updates!

[jnols]

This is really cool! Tested it out and it seems to work great. Just wanted to note that this seemed to fix some other issues I was having with SA1 roms on the stable build. Thank you paulbnl

[paulbnl]

Update:

The savestates.bin file is now auto loaded as boot1.rom. This requires unstable Main from today.
Fixed first state load after core load.
Add DSP cart support.

[MARl0]

Nice! Just tested this out, and the previous issue I mentioned is indeed fixed. Plus I tested Pilotwings (DSP chip game) and it works as well! Incredible progress on this.

[Dudu]

amazing work! it's working perfectly! you have so much talent!

[PistolsAtDawn]

I somehow missed this announcement. This really made my day! I've gotten so spoiled by having save states through software emulators that I couldn't help but miss it on the MiSTer. Thank you so much for working on this!!

[xadox]

Thx for the fresh new release.
Where does the boot1.rom has to be placed?

[SwedishGojira]

Thx for the fresh new release.
Where does the boot1.rom has to be placed?

Put it in the games/SNES folder where you usually keep your roms.

[segamemister]

while i know mister unstable is needed is there a way ini wise to tell it to use a certain mister binary this way i could keep a stable system for the rest

[rhester72]

I've never seen many reports of issues using MiSTer unstable with 'official' cores, tbh.

[redxiii]

Update:

The savestates.bin file is now auto loaded as boot1.rom. This requires unstable Main from today.
Fixed first state load after core load.
Add DSP cart support.

Thanks paulbnl for this great feature!!

I tested your latest build and it works well. Only problem I've encountered so far is with Super Mario Kart (DSP). After saving a state and reloading it the sound was very strange. It sounded like Toads karts engine was blown up. Only after a Cold Reboot (and reloading the state) it was gone. I also encountered this a second time in another track and this time pressing gas only made Toad go very slow. Also fixed after a reboot. I tried to replicate it but haven't found out a specific cause (or way to trigger it) yet.

On another note, perhaps too early too mention, but I think it would be nice if the core could be paused when the OSD is opened. This way it's possible to save while driving for instance.

Thanks again and looking forward to new releases

[todgerbodger]

Update:

The savestates.bin file is now auto loaded as boot1.rom. This requires unstable Main from today.
Fixed first state load after core load.
Add DSP cart support.

Thanks paulbnl for this great feature!!

I tested your latest build and it works well. Only problem I've encountered so far is with Super Mario Kart (DSP). After saving a state and reloading it the sound was very strange. It sounded like Toads karts engine was blown up. Only after a Cold Reboot (and reloading the state) it was gone. I also encountered this a second time in another track and this time pressing gas only made Toad go very slow. Also fixed after a reboot. I tried to replicate it but haven't found out a specific cause (or way to trigger it) yet.

On another note, perhaps too early too mention, but I think it would be nice if the core could be paused when the OSD is opened. This way it's possible to save while driving for instance.

Thanks again and looking forward to new releases

Not the developer and I also have a chimp brain. I think pausing the core is not possible since this is not the “traditional” way of doing save states with all due respect to paulbnl‘s work. Correct me if I’m wrong of course.

[lordelan]

Thank you for the update! But I’m confused I cannot find unstable Main. Is this from the mister-unstable-nightlies github? Is this referring to an unstable build of the SNES core?

EDIT: instructions are posted here https://www.youtube.com/watch?v=MZ9H_3AcSC8.
You have to override the "MiSTer" file on root of sd card with the unstable version found on discord.

How exactly?
I grab the latest file from OP's Github link (which currently is 5 days old), rename it and replace the MiSTer file in root of sd?
And then I run the update_all script again?

[FPGA64]

Thank you for the update! But I’m confused I cannot find unstable Main. Is this from the mister-unstable-nightlies github? Is this referring to an unstable build of the SNES core?

EDIT: instructions are posted here https://www.youtube.com/watch?v=MZ9H_3AcSC8.
You have to override the "MiSTer" file on root of sd card with the unstable version found on discord.

How exactly?
I grab the latest file from OP's Github link (which currently is 5 days old), rename it and replace the MiSTer file in root of sd?
And then I run the update_all script again?

No as soon as you run update_all it will replace the one you just manually installed

[lordelan]

Thank you for the update! But I’m confused I cannot find unstable Main. Is this from the mister-unstable-nightlies github? Is this referring to an unstable build of the SNES core?

EDIT: instructions are posted here https://www.youtube.com/watch?v=MZ9H_3AcSC8.
You have to override the "MiSTer" file on root of sd card with the unstable version found on discord.

How exactly?
I grab the latest file from OP's Github link (which currently is 5 days old), rename it and replace the MiSTer file in root of sd?
And then I run the update_all script again?

No as soon as you run update_all it will replace the one you just manually installed

So I have to re-do this step every time I run update_all? Or is there a way to alter update_all to have unstable cores as well?

Also by replacing a single file on my MiSTer I automatically have the unstable save state enabled SNES core?

[MiSTer Consoles]

How exactly?
I grab the latest file from OP's Github link (which currently is 5 days old), rename it and replace the MiSTer file in root of sd?
And then I run the update_all script again?

No as soon as you run update_all it will replace the one you just manually installed

So I have to re-do this step every time I run update_all? Or is there a way to alter update_all to have unstable cores as well?

Also by replacing a single file on my MiSTer I automatically have the unstable save state enabled SNES core?

You can actually specify a custom binary to use for each core. This link shows you how it's done for GroovyMiSTer. Basically you would give the unstable binary a unique name like MiSTer_snes and then add the lines below to your ini file. That way you don't have to worry about the main MiSTer binary being updated and overwriting the unstable one.

[SNES]
main=MiSTer_snes

[lordelan]

No as soon as you run update_all it will replace the one you just manually installed

So I have to re-do this step every time I run update_all? Or is there a way to alter update_all to have unstable cores as well?

Also by replacing a single file on my MiSTer I automatically have the unstable save state enabled SNES core?

You can actually specify a custom binary to use for each core. This link shows you how it's done for GroovyMiSTer. Basically you would give the unstable binary a unique name like MiSTer_snes and then add the lines below to your ini file. That way you don't have to worry about the main MiSTer binary being updated and overwriting the unstable one.

[SNES]
main=MiSTer_snes

Being part of so many retro gaming communities over the past decades (especially on Reddit), I really have to say, the overwhelming willingness and patience to help newcomers here is really something else. Just had to point this out.

Back to topic: Thanks. I'm on vacation right now but will look into this when I'm back!

[MiSTer Consoles]

Does the newest official MiSTer binary released yesterday support this save state functionality or is it still only in the unstable versions?

[Retro-Nerd]

Yes, it does.

[MiSTer Consoles]

Yes, it does.

Sweet! I didn’t see any mention of that in the release notes and wondered if the changes weren’t included just yet.

[HuggingIntense]

Does the newest official MiSTer binary released yesterday support this save state functionality or is it still only in the unstable versions?

Yes, it does.

no it does NOT.

[Retro-Nerd]

Well, i tested it and it works fine for me. Mister v241227 (offical), Snes test core 241125.

[HuggingIntense]

Snes test core 241125.

That’s not the “ newest official MiSTer binary released yesterday”. Stable SNES core was updated yesterday.

[Retro-Nerd]

Does the newest official MiSTer binary released yesterday support this save state functionality or is it still only in the unstable versions?

Read carefully. .He asked if the latest offical Mister Main binary (27.12.2024) works, not the newly released SNES core (28.12.2024) which doesn't have save state support yet. It can't because the work isn't finished yet as it seems.

[HuggingIntense]

Does the newest official MiSTer binary released yesterday support this save state functionality or is it still only in the unstable versions?

Read carefully. .He asked if the latest offical Mister Main binary (27.12.2024) works, not the newly released SNES core (28.12.2024) which doesn't have save state support yet. It can't because the work isn't finished yet as it seems.

Yes I read carefully and applied logic. The original question never mentioned “main”. When the question says does it “support this save state functionality” it’s more than logical to assume it’s referring to the SNES core not MiSTer main.

I also don’t see why anyone would ask or doubt if the "newest official" stable MiSTer main would break the last official unstable boot1.rom functionality. Also by asking "official" it's obviously comparing to something UNofficial, and there hasn't been any “unofficial" MiSTer main. The SNES core is the only UNofficial item thus far.

[Retro-Nerd]

This is getting tiresome. It's very clear that he asked about the Mister Main binary and NOT the core. He asked this question on the 28.12.2024 and mentioned the "yesterday Mister binary "release, which was the 27.12.2024 then. The new SNES Core wasn't released on that day but one day later. My last post about that topic.

[HuggingIntense]

This is getting tiresome. It's very clear that he asked about the Mister Main binary and NOT the core. He asked this question on the 28.12.2024 and mentioned the "yesterday Mister binary "release, which was the 27.12.2024 then. The new SNES Core wasn't released on that day but one day later. My last post about that topic.

People live in different time zones.

[Lightwave]

The original question never mentioned “main”.

Tip: Anytime someone mentions "the MiSTer binary" or "the latest MiSTer binary" they are almost certainly referring to MiSTer main. Otherwise, it would be something like "the SNES core" or "the latest PSX core" (occasionally 'rbf' as well)

there hasn't been any “unofficial" MiSTer main

There are unofficial MiSTer cores being generated all the time; you can find them in "unstable-nightlies" in the MiSTer Discord.

[Retro-Nerd]

Yeah, unoffical Mister main test files are released very often in the discord chat and Github. At some point Sorg updates the Mister main then with all the new changes officially. And reading this thread carefully would have helped. Paul mentions that an unoffical/unstable Mister Main was required for his SNES save states test core in the first post. And yes unstable/unofficial means the same in this context.