05-30-2018, 02:44 PM -
I wish to propose an alternative to propose an alternative to compression, which might be irrelevant and more time consuming to code, as well as CPU consuming.
"
My suggestion is on a first run, first usage of a savestate feature, a warning saying that the "savestates take around 500 mb disk space. It is recommended to use no more than one or two if disk space is a concern." Most emulators anyway have a max of 10 save state slots available, which would take no more than 5-10gb disk space, which is really trivial for most modern computers.
This might have been obvious, but just wanted to point it out because sometimes when I code, I put off features because the implementation does not seem optimal or it seems to consume a relatively high amount of disk resources, but then I realize that for most users, that is a non-issue.
"
My suggestion is on a first run, first usage of a savestate feature, a warning saying that the "savestates take around 500 mb disk space. It is recommended to use no more than one or two if disk space is a concern." Most emulators anyway have a max of 10 save state slots available, which would take no more than 5-10gb disk space, which is really trivial for most modern computers.
This might have been obvious, but just wanted to point it out because sometimes when I code, I put off features because the implementation does not seem optimal or it seems to consume a relatively high amount of disk resources, but then I realize that for most users, that is a non-issue.