And why do you want to use save states?
[Wii] The Last Story
|
11-22-2012, 01:58 PM
11-22-2012, 02:28 PM
11-22-2012, 04:01 PM
Save states cease to be useful once you start encountering problems like what you described previously. There's no getting around the fact that save states were very buggy (the situation has improved though) in earlier revisions. Your best bet is to stick to in-game saving for recording your overall game progress, and use save states as momentary snapshots (e.g. before fighting a boss, just in case).
11-23-2012, 02:04 AM
Its a shame that no one can find out what to do in my case, really, i find out myself messing with the emulator options, if someone needs to know i can tell you.
Save states used to work fine with Dolphin 3.0 (about 70%) which is an official / stable version
I used save state to play Xenoblade (too lazy to use in-game saving ) . I rate it as 70% because it doesn't work sometime There is a trick to use save states : Only use it when no voice charater or no text on screen , try to avoid using save state when there are so many characters on the screen (You should point your character at the wall or sth ) Btw , you can wait for the next stable version : Dolphin 4.0 Laptop: Mini PC ::
@zherot - It's not something you can fix. Save states are buggy in old revisions, period. They'll work sometimes, but you can expect all sorts of errors to happen at any time. Newer revisions have less save state issues (not perfect, but much better). You can stick with your old version with good speed and poor save states, or get something newer with not-as-fast speed but better save states.
11-23-2012, 02:28 AM
(11-23-2012, 02:18 AM)admin89 Wrote: Save states used to work fine with Dolphin 3.0 (about 70%) which is an official / stable version Yeah, if you're not getting a 100% speed at the time, savestate will give issues.
......?????
11-23-2012, 11:03 AM
(11-23-2012, 02:22 AM)Shonumi Wrote: @zherot - It's not something you can fix. Save states are buggy in old revisions, period. They'll work sometimes, but you can expect all sorts of errors to happen at any time. Newer revisions have less save state issues (not perfect, but much better). You can stick with your old version with good speed and poor save states, or get something newer with not-as-fast speed but better save states. I found out how to solve the problem, period.
I'm saying you can't fix it because it's the way Dolphin's code handles the save states. There are things you can do increase the success rate of save state loading, but it's not going to be perfect 100% of the time in older revisions. That they work now doesn't mean it'll stay that way.
If you did find a way to improve save state loading, there's no reason not to share it here anyway |
« Next Oldest | Next Newest »
|
Users browsing this thread: 2 Guest(s)