Savestate: Difference between revisions
Jump to navigation
Jump to search
m
→Miscellaneous
m (6 revisions: try #3) |
m (→Miscellaneous) |
||
| Line 35: | Line 35: | ||
===Miscellaneous=== | ===Miscellaneous=== | ||
*Savestates can range anywhere from | *Savestates can range anywhere from 10 MB to upwards of 25 MB in size - it can take a few seconds to finish creating the savestates, they are not created instantly. Therefore don't expect the emulator to be able to make quick successive saves - like taking screenshots - by jamming the F1 ''(save state)'' and F2 ''(change to next slot)'' keys repeatedly. Make allowances to save during a pause in the action, for example by opening a menu in the game (because most games pause the action when you open menus). | ||
*Create savestates intelligently: don't make one when you are already desperate to avoid a split-second game over - you might end up saving the moment of your death. Needless to say that savestate | **Doing this allows the emulator to create a more stable savestate because things are not moving all over the place. It is comparable to taking a picture of a group of Olympic runners standing together posing for a team pic, instead of trying to take a picture of the same team while they are in the middle of running a race. You get a clear picture (i.e. a stable savestate) of the team pose picture because everyone is standing still, compared to the blurry picture you get when the team is running. The savestate will still be created (you can still take a blurry picture), but you may not be able to load it. | ||
*Create savestates intelligently: don't make one when you are already desperate to avoid a split-second game over - because savestates are not created instantaneously, you might end up saving the moment of your death. Needless to say that savestate isn't going to be useful to you. | |||
*Savestates are not 100% reliable. While they function exactly as advertised 95% of the time, it's that 5% when they don't which you need to look out for. | *Savestates are not 100% reliable. While they function exactly as advertised 95% of the time, it's that 5% when they don't which you need to look out for. There are 10 savestate slots for a reason, don't be afraid of using all 10 of them. | ||
** | **Each game has it's own 10 unique savesate slots, depending on the game's CRC number. The savestate slots are game-dependent. And when you run out of slots but still want to keep the existing 10 savestates, you can simply cut-paste the savestate folder somewhere safe, leaving you 10 free slots again. | ||
*Regarding the | **Regarding the savestate folder, the savestates are named using the game's code, e.g. 23A97857, 3A446111, CEC42835, with the savestate slot tacked behind it. So in the third example CEC42835 (which happens to be the code for the game ''Dave Mirra Freestyle BMX 2''), the filename of savestate in slot 0 will be "CEC42835.000.p2s", for slot 1 it will be "CEC42835.001.p2s", and so on. | ||
*By default the PCSX2 savestates for all games are lumped inside one folder. People who like | *By default the PCSX2 savestates for all games are lumped inside one folder. People who like to be organized can use the naming information mentioned in the previous point to segregate their savestates into different folders, e.g. by moving savestates into different folders by game name when they aren't playing that game anymore so that their savestate folder only contains the savestates for the game currently being played. | ||
*Finally, it is strongly recommended that you not neglect to keep an updated memcard save as well. Savestates are all well and good but the only way to transfer your progress when you update the emulator or any of the plugins to a newer version is to use memcard saves. Remember, savestates care about every single detail, game saves only care about the game. | |||
[[Category:Guides]] | [[Category:Guides]] | ||