Emulator

One of the errors that appears is unknown Opcode(0x5a)

and 0x60

illegal command 34

Does this happen on single core mode also?
or only dual core one?

Both modes, and just as often.

confirmed, it happens in SC mode too since the new datareader. I have to fix the
DoState for videoplugin in fifo.cpp... Not sure how to do it yet.

thanks to nakee, r779 should fix this for SC mode.

Don't know how useful it is, but common errors are 0x7a, 0xd, 0x2, followed by
corresponding illegal commands, when you try to load a state in Zelda WW in r779 in
DC mode.

First of all, you do great job federelli... +1 for you ;)
Well... I don't think it's very usefull but I don't get where did you found those
"common errors". In the fifo desync popup (GX illegal command) or before in debug?
BTW, DC need serious fixes to enable correctly savestates and more. But for now, let
say that in DC there is one small part of the state that isn't sync with the other
part. That's obviously the problem :p.

Yeah i understand what you mean, thanks for the compliment :), but reporting issues
is nowhere near fixing them.

What i mean with common errors is the kind of error i get when the emulator crashes
upon saving/loading a state. For example:

GFX: Unknown Opcode (0x62)
...

Followed by:

Illegal Command 62
CPBase: 0x00419f60
CPEnd: 0x004b9f40
CPHiWatermark: 0x0009c000
CPLoWatermark: 0x00050000
CPReadWriteDistance: 0x0002e000
CPWritePointer: 0x004b3ca0
CPReadPointer: 0x00485cc0
CPBreakpoint: 0x00000000
bFF_GPReadEnable: true
bFF_BPEnable: false
bFF_GPLinkEnable: true
bFF_Breakpoint: false
bPauseRead: false

I can only begin to imagine the amounts of things that need to be saved in order to
save a state, while keeping the emulator synced and writing 15+ MB files to the HD,
and even after that, restoring said state, mantaining sync once again.

... but unreported issues are nearly hard to fix :)
So yes those "common errors" mean nothing... :p

Well i had to try didn't i :P.

savestates don't work for me in MP1 (intro movie + menus) DC on and DC off. I wonder
if it use to work in SC before my datareader change... r729 (TOCHECK).
Guys? Reports if you have any savestate issue in SC mode please (infos: rev + games +
where). Thanks.

Aight, we'll test when i'm able.

Savestates remain broken, being completely unreliable in most games. Metroid Prime
being one of the worst cases.

Issue 463 has been merged into this issue.

I don't think that issue 206 is the same issue as 463.
Issue 206 was reported at Sep 26, 2008. My issue appeared only when I updated a week
ago to most recent revision. When I used older revisions there was no problem. So
there is new bug.

crashes for me too in everygame i tryed. sound starts for a sec of the saved area but
no graphics + emu hangs / crashes. (for example wii sport hangs 100% for me)

Try single core mode and not dual core mode. Also, I'll be very glad (and might fix
the problem) if you track the exact revision.

Single core mode also causes crashes.
It's too difficult for me to track the exact revision, I cannot download and compile
every revision possible, but it should be between 1577 and 1634, because 1577 worked
for me, and 1634 and more higher revisions I tried, all caused the same crash.

This in an excellent testing feature, and it's a major downside that it is not
working in either mode DC/SC.

Any updates?

I have tracked the exact revision that causes the problem. It is r1594.
Revisions before it work good for me in Shadow the Hedgehog. R1594 and any revision
after causes the crashes. Please try to fix that.

First of all, thanks.

Now I just have to reproduce the crash.

I have a crashing savestate for MP1. Crashes every time I load it, no matter wether
Metroid is already running for a while or has just freshly started (loading during
Nintendo logo).

The problem is not always in the loading. Try saving again and loading.

We've changed some savestate infrastructure recently.

My problem - issue 463 is in the saving, not in the loading. The emulator crashes
when I save the game or soon after that, without loading.

But now I see that the latest revisions seem to fix that.

Sorry for merging this but as you can see, it was necessary. Too many duplicate
issues exist and this is the collaborative one for saving/loading savestates.

Still unstable as always in r2048

I wonder why it always works for me... :)

Broken for me as of r2217, but it worked on r2210...

r2195 tried saving Zelda (both), Metroid 1/2, RE0/1, MGS: TS.

If they don't crash while saving, they crash/hang while loading, sometimes it works
sometimes it doesn't. Seems to work better when there's no 3D (like during logos and
intros).

No error messages.

It works on new savestates. If I make a savestate and load it now, it works, but if
I try to load a savestate I made a while ago (probably at about r2050), it freezes.
Any luck yourself?

Simple test, save during zelda wind waker intro, crash either when saving or loading.

I don't have WW, but it works in Paper mario:TTYD, Super Mario Sunshine, and Super
Mario Galaxy.

Just tried Sunshine, same deal, sometimes it loads sometimes it hangs, seems to work
much better than WW tho.

hmm... it works great in WW for me, i'm using DC
there's still some problems though, Metroid Prime doesn't work fine with savestates,
it saves (also takes more time than saving in WW) but when you load the savestate, it
crashes. And for some reasons, it's fine in SC mode..

yeah, it crashed on make savestate once for me, and then couldn't load the savestate
afterwards, throwing: error decompressing (-4). I guess that means that it made the
savestate, but froze while compressing it. oh well.

I can load my old savestates now! (r2223)

You shouldn't be able to load old savestates as we are constantly changing the format
of the saves. Savestates are not meant to be revision-invariant.

Since everyone seem pretty much happy, can we close this one?

no, savestates still make sms unstable. I played it for 2 hours and it crashed at
least 5 times (during make or load savestate or directly afterwards), and never if I
didn't use them (excellent job, guys ^_^) so I would say it's fixed yet.

Metal Gear Solid Twin snakes, saving or loading makes Invalid Opcode error pop up,
infinitely.

When i mean save/load i always mean same revision savestates and loads. Never try
with diff revissions.

yes. always same rev. you say infinitely...have you tried holding down the enter
key? It did that at one point during paper mario, but holding enter down for about 5
secs and going through seemingly endless opcode errors made the game continue like
nothing had happened.

Infinitely means infinitely, i'm a programmer, know what i mean :P.

It enters a loop with opcodes ending in 31 33 30 31 30 and so on, like it used to do
once in other games.

ok...I thought it was indefinitely until I figured out the enter key trick, I was
trying to help (I'm a programmer, too :))

Issue 680 has been merged into this issue.

Some more input.

Loading is borked, just as bad as saving.

If a game saved properly, loading the savestate once will work, but on the next load
of that very same savestate, Dolphin crashes.

Should I be merging this into DC unstable?

Issue 807 has been merged into this issue.

Issue 1012 has been merged into this issue.

Is anyone ever gonna take a look into this? It's so frustrating lol!

Well it's complicated

(That's what she said)

here is a picture of the messages
"Internal LZO error" so far has only appeared on few games (like shadow the hedgehog)
the other 2 issues happens on every single game, Specially "metroid prime's"
issue is presented no mather the version x32 or x64 and no matter the config you use
(dual core on/off iddle skip on/off ... etc)

Issue still happens on version 3404 x64 x32

Saving is somewhat better now, but still unstable, it crashes the emulator but much
less often.

It's nice to get a warning when you are trying to load a savestate from another game.

Saving on videos still doesn't work.

Loading is as usual, sometimes it loads the save, sometimes it crashes the emu.

much less?? Oo
metroid prime's games are impossible to save with this method (well you can use the
savestate sometimes without getting a crash, but loading will surelly crash it)
what i noticed is that the emulator saves a lil bit better when the cammera is
focused on one point (like for example in Morph ball mode or in 2d games)

nothing has changed on the stability side unfortunately, savestates are much more
convenient and faster now, but still somewhat unreliable :(

it's graphics-dependent I guess. Also SA2:B saves and loads perfectly and always.

I'd ++ the release if i had access, superb job

Thank you, thank you :D

WTH, no, TY!!

I mean, you must know, as a tester/coder how important a feature this is to be able to
share savestates between users!!

Sure. As long as it works, have fun :P

Also, check the pictograph quest now that we have the sun glare (Peek Z)!

Tell me the result in the "unable to finish pictograph" issue :)

Errr Metroid Prime still hangs will saving, as soon as i press shift+f1 the game closes
itself, no clear cache and no saving state message get to appear, the emu just shuts-
down.

No files were generated either.

Maybe it's the emulation freezing that's not working and not the saving itself, since
no files were generated and no visible output.

Yeah, metroid tends to randomly crash (or so I've heard). I think that it's
unrelated/gameissue.

Doesn't crash when switching views for a bunch of revs now, but it's a guaranteed crash
if you try to save.

Well I don't have MP so I can't test it :(

You got me for testing whatever you need, but i doubt it'll help much besides what i'm
able to report.

Metroid prime does not ramdomly crash (i played the whole game without problems but
the savestate problem.

Issue still happens in version r3661 x86 x64
and i tested it with a bunch of games (such as megaman network transmition, shadow
the hedgeog, metroid prime, castlevania judment, and a few more "still testing" games)

now it does not crash as ofthen while savingstates, bu loading states will hang the
emulation most of the times...

if you want to talk add me to the messenger, i will like to go into the team for
testing more seriously (as been in touch make things faster) ;)

pretty sure savestates arn't crashing anymore.

I said that Saving by savestate does not crash things anymore (well it does
sometimes, but a very much less ratio)
but Loading still crash the emu EVERY time

Loading won't crash anymore, you have the chance to load again and again and again
and again, it will work in one of the times....

I'll try to figure it out later on

believe me it's not working....
for example while i was testing metal gear solid control issue. the times i used
savestate and loaded the emulator did 2 things
or either it gets stuck (music playing) and black screen or previous screen (freezed)
or directly the load works but then afther you move the emulator closes...
so still not working (i set metal gear as an option cuz i was playing the whole game,
but it also happens in a few more game i tested such as megaman network transmition,
metroid prime 3 etc...)

Found out something really important i believe.

Chances of the emulator crashing when it needs to create the savestate file are around
90% in stables games such as Z:WW. In the same game, savestating to an already creted
file will never ever hang the emu, hell, not even keeping shift+f# makes it hang/crash
(although memory consumption starts going up fast).

Sump up: Savestating will almost always crash if it needs to create a file from zero.

well my savestates are created just fine thank you.

It's just that loading sometimes issues a "Failed to decompress (-8)" error that I
need to solve.

Savestating does not represent any problem to me either (not a problem creating or
saving over an already created one), the problem is ONLY when "LOADING"... and i have
detailed the problem on the previous post

Meh, it almost always crashes here when i'm saving for the first time, and then that
one time it doesn't hang, the next times i save it never ever hangs again.

Saving works fine here in DC mode, haven't tried SC mode yet (on Pikmin GC NTSC-US).
Loading worked up to r4365, but loading a saved state causes black screen and sound
loop freeze with both SC and DC mode, in r4366 and after r4375 or r4379 it causes the
emulator to fully crash, at least in DC mode.

Ref: http://forums.dolphin-emu.com/thread-4696.html

Using Save States between revisions is not -always- going to work unfortunately,
actually it depends on the change, but its not to be trusted, also there should be a
nice windows telling you that your savestate is not compatible, but it seems like
nobody cares to update the save state revision :P

Ok, I'll make a fresh savestate in r4366 and report back.

Yup, r4366 does load it's own savestate. Go figure! lol

Anyways, I guess I should file a separate issue for memory card saves not always
working... :-/

I get the error when I try to load a save on a newer revision...

what´s inside exceptioninfo.txt =

Unhandled Exception
Code: 0xC0000005
Call stack info:
ntdll!0x7C91AC4A : RtlpWaitForCriticalSection
ntdll!0x7C901046 : RtlEnterCriticalSection
0x0824448B : ?

Sounds like RtlEnterCriticalSection (called from wx's critical section macros)
received an invalid CS handle, but I think there's too little information to tell
where it went wrong.

game Zelda wind waker
save state created with rev 4434 (loads fine)

r4425 = loads fine
r4435 = loads fine

r4447,r4450,r4460,r4466 = no way loading LoL = when I select the file and click
"open", the emulator just "disappear" (closes with no error messages)

xp sp3 32bits

and if it helps, here comes my ini files from /user/config

thanx

romanodj: read comment 87

ok, using save states between revisions is not always going to work.. sadly

i´ll start over the game using r4466 and check for here on what happens

thanx

I haven't experienced a crash nor saving or loading states on the last revisions
since r3972 BUT most of the times when i try to Load a savestate this end up going
wrong and instead of taking you to the exact point you saved it does nothing (just
the music plays as if you where in the place you saved, but the screen is freezed and
no command is inputed either "example if you where against an enemy you will notice
the action is not going on cuz there is no sound of struggle etc..." just the
background music and the screen freezed)

tested it on a lot of games (and doing it more than once to see if it's fixed by
stresskey... but no)

another problem is with wii games that uses wiimote (I do not have a wiimote so i
don't know it this happens with a real wiimote, I tested it on wiimote pluggin
keyboard emulation)
Once you load a savestate most of the times you will get a "disconnect" from the
wiimote and there is no way for you to Re-connect it.... so even if you have a
savestate you can't continue due to loading the state makes imposible for you to
move... ergo you can't continue the game. tested this on "Dead Rising" and "Metroid
Prime 3"

last revisions I Tried where: r3972 x64 x32 and r4460 x64 x32

Loading a state in SuperMarioGalaxy also stops wiimote from working.
Rev 4460 same for Save and Load.

Well I haven't got a savestate crash for a while now. I do get the black screens
though and end up restarting dolphin and reloading. This is probably due to a deadlock.

ryan.hunt.44: This is not the savestate issue, but the wiimote desync issue, which we
should also solve for savestates to work properly on the Wii.

Thx

I do have many savestate crashes on Zelda Twilight Princess for gamecube using r4588

Still get them loading and saving from time to time - occuring for me in the 47xx
series.

Issue 1937 has been merged into this issue.

time to time saving crashes the Emulator (so you need to save in different states in
order to keep last save safe)

it does it random
reported up to r4826

Yes indeed, saving/loading is still not safe :/.

I'm not sure how save states currently works. But would it be possible to pause the
game, save the pause status then resume the game? Or possibly add a pause and resume
into the current save state to make sure the save is correctly synced?

Pausing the game is also unstable, usually results in crashes.

Really? I've never had an issue with pause only stop. Maybe OGL only issue with
pause? Cuz DX9 I have yet to crash pausing.

It happens with D3D too, mostly in wii games (not so much in Gamecube ones but it
does happen)

Pausing or not makes the emulator crash anyway (it's not a desync thing)

Issue 2250 has been merged into this issue.

Issue 2100 has been merged into this issue.

it's NOT that ofthen, but it does still happen... you need to save in different slots in order to be "safe" from corrupting the savestate and not been abble to use it, as when it saves as the emulator crashes the safe file becames sort of "invalid"
so the issue remains (just now is more stable)

last revision i tested was r6025 x64 and x32
(i don't know if this is relevant, but it seems to happen more ofthen with WAD games)

Do the games that crash (while saving) need MMU enabled? Or are they normal games? erm... just name the game and the part where it seems to crash. Are you using the DX9 plugin or the OGL plugin? DX9 seems to be more stable for savestates.

I used booth pluggins to test this and it does not change the rate of crashing it simply does no matter wich one you use and as frequently.

they do not need mmu (but you can use it if you want, it wont change)

for where it crashed is not an specific place, it happens around most games (specially if you stress the savestate) try on megaman 9 & 10, Castlevania The Adventure Rebirth, Contra Rebirth, Metroid Prime 3, Dead Rising.

like i said it does not happen in an specific place, but start saving over andover and most surelly by the 3rd or 4th time you save it will happen (if not i will try to make a video)

This is still an issue... I'm using Dolphin 2 r6205 SSSE3 x32, Dual Core enabled, D3D9 plugin, Dolphin Wiimote New Incomplete plugin, playing on Megaman 9.wad and Megaman 10.wad. I've experienced this problem with both KEYBOARD and USB Controller configurations for the Wiimote plugin.

In my case:

A 'crash' still leaves the video and audio playing but the input/controls are disabled, even after refreshing the input source in the wiimote settings

Saving a new save state will NOT ALWAYS crash the game

Loading a 'valid' save state will NOT USUALLY crash the game

Loading an 'invalid' save state will ALWAYS crash the game

I've had some great save states that I save with no issues only to find that when loaded, they are unable to be played (controls/input do not respond). This is repeatable.

The wiimote not reconnecting after a savestate is loaded is issue 2484.

This issue refers to the crashing that occurred on save or load.

Remember that wiimote disconnection IS NOT the only issue here, creshing happens (not always, but LOTS of times by stress)

The Metroid games are particularly thread unsafe for some reason, Metroid Prime 3 over all.
Sometimes you save and it saves fine but then it crashes 3-5 seconds after loading.
Sometimes it saves and you load and you get a black screen with sound.
Sometimes it saves and you load and you get nothing.
Sometimes it saves and you load and you get a crash.
Sometimes it doesn't even save and you get a crash.

Unknown Opcode 0x18 with Brawl, happens in single and dual core mode, seems to usually work out of combat. Never works in combat, or when game is paused. Using 3.0-397