Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Bug] Sstate corruption bug
#1
# PCSX2 version: PCSX2 0.9.7.r3876
# CPU options: default
# Plugins used: GSdx 3693
# Description: Game freezes when sstate is loading after save.

Log: Trap exception at 0x006905e0
Game: Dot HackG.U. Vol3 Redemption

Guys, seriously, why dont you implement a backup of sstate, then saving? I'm not the first time running into this error with sstate, and it angers me very much. Angry
Based on the size of the sstate file (14562989 instead of 15xxxxxx bytes), it just did not finish save completely. Why?
Reply

Sponsored links

#2
savestates have always been unstable, unfortunately.
AFAIK, merely because of plugins

It's not recommended to rely on them, but use classic save points
I remember using savestaes with PS1 emulation.
A lot of them crashed.

moved to general discussion
CPU : I7 2600K Oc'ed @ 4.2Ghz
Mobo : Intel P67 southbridge
GPU : NVIDIA Geforce GTX 750 Ti
RAM : 6 Go
Reply
#3
How about adding backuping for overwrited sstates? This may solve problems such as mine.
Reply
#4
you can try make a new folder as backup inside the sstates folder and use the copy-paste function.
make sure you know the CRC of that game.
Main Hub:i5-4670(3.4Ghz Factory Clocked),ATi Radeon HD7770(GDDR5+128-bit+1GB),Win 10 SL(x64),ASUS H8M-E,8GB DDR3 RAM
Reply
#5
(11-19-2010, 02:43 PM)tallbender Wrote: you can try make a new folder as backup inside the sstates folder and use the copy-paste function.
make sure you know the CRC of that game.

No, I meant to add this feature in next build as automatic backup. You never know when a failure in save occurs, so it makes no sense to do it manually.
Reply
#6
devs don't take requests.
but as this is an open source project, you can bring your piece of code at http://code.google.com/p/pcsx2/
CPU : I7 2600K Oc'ed @ 4.2Ghz
Mobo : Intel P67 southbridge
GPU : NVIDIA Geforce GTX 750 Ti
RAM : 6 Go
Reply
#7
Savestates not writing out correctly is not a common problem.
There's a lot of safeguards in place for that and I wonder indeed how you manage to break it ><
Reply
#8
Could be system instability but anyways as mentioned before relying in savestates all the time is not a good practice to begin with (I do agree with a backup for last savestate overwritten tho) Tongue
Core i5 3570k -- Geforce GTX 670  --  Windows 7 x64
Reply
#9
(11-19-2010, 05:44 PM)jesalvein Wrote: devs don't take requests.
but as this is an open source project, you can bring your piece of code at http://code.google.com/p/pcsx2/

I dont think, that renamеing old file into filename.bak, before writing new one is need huge pice of code. Tongue
But, if devs dont take requests and dont pay attention to this problem, this thread is useless.
Reply
#10
(11-19-2010, 05:51 PM)rama Wrote: Savestates not writing out correctly is not a common problem.
There's a lot of safeguards in place for that and I wonder indeed how you manage to break it ><

Just load my sstate in 5-8 seconds after save, lol. ^_^
Not the first time, nor the last, I think.
Reply




Users browsing this thread: 1 Guest(s)