Please forgive me if this has been addressed else where. I did a cursory search on save state issues and did not find a satisfactory resolution. A bit of technical info:
DraStic ver: r2.2.1.2a
Game: Sands of Destruction (US Ver) ran from a zip file
Phone: SCH-I545 (Samsung Galaxy S4, Verizon)
Hardware Ver: I545.06
OS: Andriod 4.4.2
Debug info:
MemOffset: FFFFFFFF
MemModifier: 0110
Threads: 3
Mode: ARMv7 NEON
Sample Rate: 48000
Buffer Size: 512
Various Configurations:
Enable uncompress to file: On
Store in-game Saves in Savestates: Off
Auto-Trim ROM: Off
Autosave: On Pause/Suspend
Resume last save when starting from shortcut: On
Savestate Overwrite needs Confirmation: On
Google Drive: Unconfigured/Not used
Directory: /storage/emulated/0/DraStic or /storage/sdcard0/DraStic
Both appear to be exactly the same. Each contains the same files with the same timestamps on recently
modified files. I am not exactly well versed in the architecture and mechanisms in the Android OS.
Alright, sorry in advance if I included far too much information. None the less, the problem that I am encountering involves the save state mechanism. This is issue began a few hours ago, in the absence of any modification of the DraStic software version or any OS modification, that I am aware of.
When I go to create a save state, it generates the save state file when I overwrite a previous save state, reflecting the updated timestamp. However, if I exit the savestate screen and reopen it, or open the load savestate screen the newly created savestate file is not reflected, instead the previous savestate that I overwrote is still there. I opened the DraStic savestate directory and looked at the savestate file details and it reflects the timestamp of the newly created savestate; however, it is not reflected in the program.
I have overwrote all 8 savestate files and the quicksave, with a new savestate and the same issue of not updating occurs. I even deleted a savestate, checked that it was deleted from the DraStic savestate directory, which it was, then tried to create a new savestate in the newly vacated slot. In the DraStic program, the savestate slot reflects that no new savestate was written to the slot; however, in the DraStic savestate directory the newly generated savestate is present bearing the correct timestamp.
So am I am at loss as to why this issue has, what appears to be, arbitrarily manifested itself and the necessary steps to rectify it. On a more optimistic note, DraStic is by far one of the, if not the, best emulators I have ever had the pleasure of using. I rank it on par with the stability of the less complex SNES9X emulator, which is damn near impossible to induce pathological glitches. Not to mention, that for some reason it is much faster and stable than PC based DS emulators. The worth far exceeds the diminutive price tag, keep up the good work.
Save state issues
Re: Save state issues
Does it still happen after you reboot your device? Can you also check how much free space you have on your internal memory?