Posted: 11/5/2013 6:57 PM
Post subject: snes9x - option to prevent savestates from loading SRAM?
Quote
BigBoct
He/Him
Editor, Former player
Joined: 8/9/2007
Posts: 1692
Location: Tiffin/Republic, OH
I'm still doing the blindplays of randomzied Super Metroid runs I mentioned in my last time, and I'm trying to do them with minimal tool-assistance. I'll save a state occasionally for a really hard part, then save the SRAM at a save point. Problem is, then sometimes I load a state by reflex, and the SRAM from that savestate overwrites the newer SRAM from the actual save and I lose progress. I know there's an option to not do that in ZSNES, but I don't know where it is in SNES9X. I'm using v1.52-rr, SVN revision 184 I believe.
Previous Name: boct1584
Posted: 11/5/2013 11:52 PM
Quote
FractalFusion
Editor, Skilled player (1941)
Joined: 6/15/2005
Posts: 3247
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
I think it would be better to make a savestate after you save to SRAM, and only use that savestate if you need to go back (I assume you aren't going back further than that). That savestate also provides backup protection if you load a savestate further back by accident.
Posted: 11/7/2013 12:30 AM
Quote
BigBoct
He/Him
Editor, Former player
Joined: 8/9/2007
Posts: 1692
Location: Tiffin/Republic, OH
The most recent incident was that I tried to do that, but there was an input lag spike (my computer's not that great) resulting my system not registering that I was holding Shift when I hit F1, and it loaded the state instead of saving it. My problem is that for the longest time, I save-scummed with savestates on everything I played, and it's still a reflex for me to do that.
Previous Name: boct1584
Posted: 11/7/2013 7:31 AM
Quote
FractalFusion
Editor, Skilled player (1941)
Joined: 6/15/2005
Posts: 3247
Glitchy TAS of 2013 Gameboy TAS of 2013 PSX TASer of 2010
There are a few options left: - Reassign the savestate/loadstate keys so that you can never press them on reflex/by accident, including disabling them. - Reassign the savestate/loadstate keys so that the keypress for savestate can never be mistaken as the keypress for loadstate. - Find the save RAM file. After saving to RAM, immediately backup the file. Edit: Another option, don't know if it helps though: - Find the savestate files. After saving to RAM, delete all your savestate files.