-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GeneralConfig: Option to autoload most recent savestate at game launch. #3087
Conversation
Why can't you just press F1 as soon as the game has been loaded? That doesn't sound very hard... And frankly, relying on savestates is a bad habit, as they can be broken by any number of things (see the forum) and destroy your save data. |
You also can ask "why you can't launch dolphin through commandline and specify all the options". And still we have UI and configs. |
That's not a fair comparison at all! The command line requires obtuse learning of specific commands, and offers no way to learn said commands or how to combine them. A UI is far more friendly, since the only learning required is basic reading. Meanwhile, pressing a single button after a game loads? That's not hard. And yes, I am definitely worried about users getting too comfortable with savestates - because it is already a problem. If savestates become the primary or only method one uses to save, which this method would encourage, than they will learn the pain of it breaking, which it will inevitably do. They are not meant for long term use! In their unstable state they are useful for temporary things, like saving before a boss so you can reload if you die, and then standard saving afterward, so they shouldn't be removed because of that. |
So let's move it to advanced tab? (As if it'll help...) |
Well... I could keep going, but honestly... I think it's best to wait on this. sigmabeta is planning to set up a system to create a savestate on emulator close and then auto-load a savestate on reopen. This is to match android behavior, but it would accomplish what you are wanting with this PR far better than this alone, I think. And since it will be a standard behavior for the emulator on a platform, it's going to be vetted, nitpicked, bikeshed, and heavily tweaked to avoid savestate problems! So I think it might be best to wait until sigmabeta implements that, and then just create a version (yes please, in the advanced tab!) for the main Dolphin? |
Major, i don't think we should block a feature just because someone is planning to possibly do somethi g in the future. Void-ghost, The idea is good, but I don't like the way it is hacked into hotkeys. @dolphin-emu-bot rebuild |
Yeah, I was working on save-on-exit too. I see no problem, if it's already in development then I just keep that branch to myself, until it appears in main. |
FifoCI detected that this change impacts graphical rendering. Here are the behavior differences detected by the system:
automated-fifoci-reporter |
{ | ||
if (!silent) | ||
Core::DisplayMessage("State doesn't exist", 2000); | ||
} else |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
I agree with @phire with regards to how it's intertwined with the hotkeys. |
@@ -177,6 +177,7 @@ void SConfig::SaveDisplaySettings(IniFile& ini) | |||
display->Set("PAL60", bPAL60); | |||
display->Set("DisableScreenSaver", bDisableScreenSaver); | |||
display->Set("ForceNTSCJ", bForceNTSCJ); | |||
display->Set("AutoLoadSavestate", bAutoLoadSavestate); |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
I'm not really in support of this change. Like MaJoR said, why not use hotkey to load savestate 1 the moment you boot the game? It's just one step away. If this option is a thing, how much steps will it take to NOT autoload the savestate on boot? |
It'll take three mouse clicks: General -> Autoload latest savestate -> OK. |
Lol, the users will have to go through the settings just to be able to turn on or off the autoload feature. I'm sure if you held the hotkey while starting the game emulation it will be pretty much as if the autoload feature was enabled. |
That hotkey is not bound by default. So, no, user had to remember in which slot he saved last. |
I've seen people complaining about accidentally quitting a game on emulators so a savestate on close would be nice for them. |
Has any progress been made with this PR? |
We don't want to add this to Dolphin, for the reasons described here: https://bugs.dolphin-emu.org/issues/10012 Because of that and because the PR hasn't been updated in a year and a half, I'm closing this. |
For what it's worth, that is not much, i just want to say that this part of the argument for closing:
Can be mitigated by just not saving on exit (overwriting it) if the special savestate didn't load on start of the game for some reason and warning the user to try the earlier version of the emulator and normal save. It's not hard to prevent, and something you'd probably want anyway even if savestates were stable. |
@i30817 By "randomly don't work", I didn't mean that the loading process has a chance of failing, I meant that savestates might be saved with bad data and thus always be impossible to load correctly regardless of which Dolphin version you use. |
Just noticed i skimmed right over the first line like a schlub. Sorry about that. |
This allows you to continue to play from the last savestate you've made. You don't need to remember into which slot you've saved last, you don't need to wait for some strange heavy iso-disc access to complete before you can play the game (hi, Xenoblade). The game just continues from the last save.
Added a new option into dolphin.ini and a checkbox to Config->General.
This change is