Emulator Issues #11815
open
[FEATURE REQUEST] Auto-download compatible Dolphin version when incompatible savestate is opened
Added by Jebeld17@gmail.com over 4 years ago.
Updated about 1 month ago.
Issue type:
Feature request
Relates to performance:
No
Relates to maintainability:
No
Description
I have a lot of saved savestate files from my emulated games over the years, and it gets a little difficult keeping track of the versions of dolphin I've used over the years in relation to the savestate files. There must be a way to get around this "compatibility error" hurdle better - where I'd have to go back manually and re-download the old Dolphin build just to resume an old savestate - in an automated fashion.
I have a solution:
Upon opening an incompatible saved savestate file, Dolphin:
1. auto-downloads the needed Dolphin build,
2. auto-installs the needed Dolphin build to a temporary location,
3. re-opens the savestate file in the new Dolphin build directory, applying the same game's .ini settings and Dolphin settings where possible
4. deletes the temporary file(s) used in the process after the user closes the session.
No thanks, automatically doing all of that is far, far, more than a user could expect or want in some cases. The closest thing we could do is put a link to the build in the on-screen display messages and let the user choose whether or not they want to download another build.
JMC4789 wrote:
No thanks, automatically doing all of that is far, far, more than a user could expect or want in some cases. The closest thing we could do is put a link to the build in the on-screen display messages and let the user choose whether or not they want to download another build.
Even though the users may have not asked for it directly, adding a nice automated feature into the program to do this shouldn't be off the cards. I believe adding more automation into programs increases productivity and saves time.
I don't think it would provide enough value to users to balance out it making things messier on the code side. But a link should be fine.
- Issue type changed from Bug to Feature request
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by