/vr/ - Retro Games

[Anonymous No.5171094]

I need someone to vindicate me because I feel like I'm taking crazy pills. I just got an SNES Classic and I was playing Earthbound using a combination of SRAM and Save States, whichever was more convenient. Well today I couldn't remember if my SRAM or my save state was further ahead so I booted up the save state first. Nope, further back than my SRAM save in game was last night, time to reset and load the game up by itself.

THE SNES CLASSIC OVERWRITES THE GAMES SRAM WITH ITS SUSPEND POINT DATA.

The worst part? Everyone online is acting like this is normal and this is how emulators work. Last I checked retroarch's .state files don't fucking TOUCH my .srm files. Has anyone else experienced this insanity? How could Nintendo think making your states play Russian roulette with your SRAM would be a good idea?

[Anonymous No.5171121]

>>5171094
Save data is a part of the state. Most games use sram as save, but some use it as general purpose ram too, so not reloading and overwriting it could have problematic consequences.

You should at least know something about the platform you're emulating before complaining.

[Anonymous No.5171128]

>>5171121
If troll post, +1

If serious, use any emulator. State data never writes to .srm data.

[Anonymous No.5171132]

>>5171121
Not OP, but most emulators have two separate files. One for regular save data, the other for savestates. If I load a savestate it does not wipe out my regular save data, if I reset the game it will load my regular save by default. There is no reason for loading a savestate to cause a permanent loss of regular save data.

[Anonymous No.5171141]

>>5171132
Correct. The amount of people online who don't realize this is staggering. Nintendo includes this tiny disclaimer in their support section online that basically says "we didn't implement this properly, you should probably only use suspend points". Incredible.

[Anonymous No.5171206]

well this happened to me with various emulators actually (I don't have a snes classic) so don't think nintendo is fucking with you intentionally or using a subpar emulator
I think many emulators keep SRAM in actual RAM and to reduce writing on disk continually they only write on file when emulator is closed/reset, probably snes classic flash storage is cheap and low quality and many writes would kill it faster
my theory is that the savestate contains a SRAM copy and that it's written on your .srm after resetting the console to load from the in-game save system
I usually make a savestate immediately after a in-game save, just to be sure

[Anonymous No.5172354]

>>5171094
nerd

[Anonymous No.5172374]

>>5171094
The game-select straight up tells you that if you load a save state, it will erase your save game.
Read the fucking screen. Those words mean things.

[Anonymous No.5172401]

>>5171128
>>5171132
>>5171132

fceux does not work like this

[Anonymous No.5172407]

A possible solution is to not use save states.

[Anonymous No.5174432]

>>5171094
no, you're not crazy. the classic is garbage.
>>5171121
you're an idiot.
>>5171141
top kek. what a fucking joke.

[Anonymous No.5174438]

>>5172407
Based and redpilled

[Anonymous No.5174491]

>>5174432
save data IS part of the save state

to have it work differently would mean you have to save the save data twice, once in memory and then later to disk

[Anonymous No.5174525]

So on a normal emulator, say I play the game for hours save it in-game AND make a save state.
Then I restart from scratch and done in-game again.
Which version of the in-game save do i have when I load the state?

[Anonymous No.5174734]

>>5174525
The first one. The save state is a complete capture of memory, including the sram.

[Anonymous No.5174758]

>>5171094
Welcome to emulators. Hope you learned your lesson.