I put this up on reddit as well, reposting here because I think this is a better place for discussion.
So, I've been playing dumped games last couple of weeks and I noticed that in certain games (I've had it happen on P4G and TOCS1) when you try to save game, it shows all previous save files are empty and some error when trying to save, this is fixed by closing and reopening the game. It doesn't matter if you've put the devide to sleep or you have been playing it continuously.
Now what happened yesterday was I was playing TOCS between 3:30 to 4:15 AM and I got the error. Thinking back I remembered it happening on P4G when I used to play in the early morning. So I decided to test it again today, and it happened again somewhere between 4:02 - 4:07AM. I did try to change the time from settings back to 4:00 Am to retrigger the bug, but it didn't happen, my guess is there is an internal clock that doesn't change (unless the console is rebooted after changing time in settings? I didnt try that yet) and to support this hypothesis try changing your time in settings, then open P4G if you have it, and at the title screen go into 'TV Listing' it will continue to show the original time.
Anyhow, this got me thinking about the chinese guy who asked people to change settings time to 12 hours clock (mine has always been 12hours clock and I manually set time) and to delete some file under save folder. I havent tried it yet but I'll do so and report back if it's successful.
TL;DR- The save bug is triggered EVERYDAY AT THE SAME TIME irrespective of if you keep the console in sleep mode or are actively playing it. I do not understand the significance of the time it occurs at, maybe it's the time I last rebooted, or the time I installed the game, or something else entirely.
I cannot say if it is a vitamin issue or something with HENkaku, I advice others to also try to pinpoint the approximate time the bug appears. Hopefully someone more knowledgeable will understand why this happens. But I think this proves the bug doesn't simply occur because of sleeping the console, it happens whenever the game is kept open (active or standby) and you cross that certain moment after which it bugs out.
So, I've been playing dumped games last couple of weeks and I noticed that in certain games (I've had it happen on P4G and TOCS1) when you try to save game, it shows all previous save files are empty and some error when trying to save, this is fixed by closing and reopening the game. It doesn't matter if you've put the devide to sleep or you have been playing it continuously.
Now what happened yesterday was I was playing TOCS between 3:30 to 4:15 AM and I got the error. Thinking back I remembered it happening on P4G when I used to play in the early morning. So I decided to test it again today, and it happened again somewhere between 4:02 - 4:07AM. I did try to change the time from settings back to 4:00 Am to retrigger the bug, but it didn't happen, my guess is there is an internal clock that doesn't change (unless the console is rebooted after changing time in settings? I didnt try that yet) and to support this hypothesis try changing your time in settings, then open P4G if you have it, and at the title screen go into 'TV Listing' it will continue to show the original time.
Anyhow, this got me thinking about the chinese guy who asked people to change settings time to 12 hours clock (mine has always been 12hours clock and I manually set time) and to delete some file under save folder. I havent tried it yet but I'll do so and report back if it's successful.
TL;DR- The save bug is triggered EVERYDAY AT THE SAME TIME irrespective of if you keep the console in sleep mode or are actively playing it. I do not understand the significance of the time it occurs at, maybe it's the time I last rebooted, or the time I installed the game, or something else entirely.
I cannot say if it is a vitamin issue or something with HENkaku, I advice others to also try to pinpoint the approximate time the bug appears. Hopefully someone more knowledgeable will understand why this happens. But I think this proves the bug doesn't simply occur because of sleeping the console, it happens whenever the game is kept open (active or standby) and you cross that certain moment after which it bugs out.
)
