Emulator

Little update on this issue.
I tested with the latest version I found (Dolphin-3.0-421) and the problem is still there.
However this time I also tested the x86 version of Dolphin. It crashes at the exact same moment but this time I have a popup window with "DSI Exception in stmw". I click the OK button then another one comes up with "DSI Exception in lmw" then again the other one, etc. Then I need to kill Dolphin in the task manager.

6 months ago I had these crashes too but recently (in december) I played the whole game and was not able to reproduce this bug.

Can you check if you can reproduce the bug with the three GFX backends (DX9/DX11/GL) or if it only happens with a single backend?

Additionally, can you check with "EFB CPU access" unchecked in the graphics configuration?

I just had this issue too. I am on the latest revision, and everything worked fine with "Ignore EFB CPU access" checked (if I uncheck it, game becomes extremely slow at loot screen), I was able to sell some items and photos at the first village shop, but when I entered the capital (I play in French so the names aren't the same, sorry), I tried selling some photos, and this time, the game crashed.

PC specs :

Core i7-2670QM
AMD Radeon HD7690m XT
Tried on DX9 only, because I didn't save my game before entering the shop so I have to play a lot before entering the capital again.

I just tested with Dolphin-3.0-421 and with the three backends.
I have a save file in the second capital of the game (Sheikath I think). I go to the shop 2 screens left and I try to sell the "Iron Bettle I" magnus photo I have in my inventory.
On Dx9, it freezes very quickly, less than five seconds after my cursor is on the card.
On OpenGL, it stays a little bit, I am able to browse my inventory before the freeze.
On Dx11, I have the same behaviour as with OGL. I took a screen at the moment of the freeze (the music is still playing in the background).

@delroth: if you managed to play from beginning to end without the bug, either there is a magic option/magic revision to get rid of it or you were extremly lucky (and didn't take many photos :p ).

Sorry for the double post.
I forgot to mention that I had checked "Skip EFB CPU access" for the tests.
I just tested with this option unchecked. The freezes happened much later with OpenGL but they happened instantly when I highlighted my photo in my inventory with Dx9 and Dx11 (like in the screen attached to the previous post).

I am getting the same problem. I managed to get it working for a little while in 3.0-415 with OpenGL, EFB access to CPU unchecked, EFB copies to RAM with a (fast) cache enabled. However, after awhile and taking/selling a few more photos, I got that "DSI Exception in lmw" error when looking at one in the inventory. I kept hitting OK (because why not) then I got some different errors... not sure if they're related to the problem with the game or if it's just because I kept hitting OK, but I figured I'd post them just in case.

can you reproduce this in easy way? Could you giveem your save files or save states for reproduce this?

Sure, here is a link to my memory card with the Baten Kaitos save. Just load the first one, you will be in a city. Go 1 screen left then enter the first doorway with the lights on (it is the shop). Choose "Shop" then "Sell". Highlight the item "Iron Beetle I" in the inventory and wait. Sometimes it freezes instantly, sometimes you need to wait 10 seconds or 1 minute.

Link to Memory Card :
http://dl.dropbox.com/u/12974601/MemoryCardA.USA.raw

Thought I'd upload mine too, since I have a save that acts weirdly.
http://www.mediafire.com/?watvjvuaq666dl2
In file No.003, I have 3 Shawra magnuses. The first two, for some reason, DON'T freeze the game; can look at and sell them all you like, everything happens as it should. However, the last one (and any subsequent photos taken) freeze like normal when you try to sell them. Not sure what the difference is between them, they were all taken at roughly the same time in the same place.

In think this hangs is not related with fifo, the fifo seems fine.
But i found this Example 1:

48:48:836 Src\PixelEngine.cpp:412 N[PE]: SetFinish_OnMainThread
48:48:836 Src\PixelEngine.cpp:370 N[PE]: UpdateTokenInterrupt 0
48:48:836 Src\PixelEngine.cpp:377 N[PE]: UpdateFinishInterrupt 1
48:48:836 Src\PowerPC\PowerPC.cpp:390 N[PowerPC]: CHECKEXP EXCEPTION_DSI
48:48:836 Src\PowerPC\PowerPC.cpp:400 N[PowerPC]: EXCEPTION_DSI
48:48:838 Src\PowerPC\PowerPC.cpp:373 N[PowerPC]: CHECKEXP EXCEPTION_FPU_UNAVAILABLE
48:48:838 Src\PowerPC\PowerPC.cpp:384 N[PowerPC]: EXCEPTION_FPU_UNAVAILABLE

Example 2:

32:16:253 Src\PixelEngine.cpp:370 N[PE]: UpdateTokenInterrupt 0
32:16:253 Src\PixelEngine.cpp:377 N[PE]: UpdateFinishInterrupt 1
32:16:253 Src\PowerPC\PowerPC.cpp:441 N[PowerPC]: INT_CAUSE_PE_FINISH
32:16:253 Src\PowerPC\PowerPC.cpp:446 N[PowerPC]: EXCEPTION_EXTERNAL_INT
32:16:253 Src\PixelEngine.cpp:370 N[PE]: UpdateTokenInterrupt 0
32:16:253 Src\PixelEngine.cpp:377 N[PE]: UpdateFinishInterrupt 0
32:16:253 Src\PowerPC\PowerPC.cpp:446 N[PowerPC]: EXCEPTION_EXTERNAL_INT
32:16:253 Src\PowerPC\PowerPC.cpp:366 N[PowerPC]: EXCEPTION_SYSCALL (PC=8014c248)
32:16:253 Src\PowerPC\PowerPC.cpp:366 N[PowerPC]: EXCEPTION_SYSCALL (PC=8014c248)
32:16:253 Src\PowerPC\PowerPC.cpp:366 N[PowerPC]: EXCEPTION_SYSCALL (PC=8014c248)
32:16:253 Src\PowerPC\PowerPC.cpp:366 N[PowerPC]: EXCEPTION_SYSCALL (PC=8014c248)
32:16:253 Src\PowerPC\PowerPC.cpp:384 N[PowerPC]: EXCEPTION_FPU_UNAVAILABLE
32:16:253 Src\PowerPC\PowerPC.cpp:366 N[PowerPC]: EXCEPTION_SYSCALL (PC=8014c248)
32:16:253 Src\PowerPC\PowerPC.cpp:384 N[PowerPC]: EXCEPTION_FPU_UNAVAILABLE
32:16:253 Src\PowerPC\PowerPC.cpp:446 N[PowerPC]: EXCEPTION_EXTERNAL_INT
32:16:254 Src\PowerPC\PowerPC.cpp:366 N[PowerPC]: EXCEPTION_SYSCALL (PC=8014c248)
32:16:254 Src\PowerPC\PowerPC.cpp:384 N[PowerPC]: EXCEPTION_FPU_UNAVAILABLE
32:16:254 Src\PowerPC\PowerPC.cpp:400 N[PowerPC]: EXCEPTION_DSI
32:16:255 Src\PowerPC\PowerPC.cpp:384 N[PowerPC]: EXCEPTION_FPU_UNAVAILABLE

The game always hang with EXCEPTION_DSI. And this exception only happens in the log once time when hang :P

Too bad it was not FIFO related. At least you narrowed it down :) . I checked the forums a bit and I found users saying that activating MMU, BAT and Accurate VBeam might solve the problem. I tried that and I only get a black screen instead of a freeze :s .

Can anyone reproduce this issue on Linux btw? I wasn't able to get the freeze after about 10 minutes with the Iron Beetle highlighted. Both Jit and JitIL.

Also, does this also happen with the GL video backend on Windows, or only DX9/DX11?

I don't have a Linux at hand :( .
On Windows, the hang happens on every backend. The time the game takes to freeze is significantly higher on DX11 and OpenGL whereas nearly instantaneous on DX9.

So just to check, you tried OpenGL?

FYI, I wasn't able to reproduce this issue with dualcore turned off.
I also wasn't able to reproduce this issue with thread affinity set so that only one core can be used in dualcore mode.
(It's quite odd that nobody else mentioned this in this issue thread, though...)

Probably some kind of timing problems with EFB access: AFAIK the EFB peeks are executed in the CPU thread but execute GPU functions (glReadPixels for example). Dualcore turned off or only one core being used forces GPU and CPU thread to be executed sequentially instead of concurrently, "solving" this bug.

I downloaded the latest version I could find (Git-3.0-687) and like wordmanw... said, there is no bug/freeze/crash when the "Enable Dual Core" option is not checked.

I didn't play the game to see if it is really demanding and we can see an significant impact on performance. I'll give it a try next week I think.

You could also disable EFB CPU access in the graphics hacks tab. AFAIK they are not used for anything important in Baten Kaitos.

I still get the problem with EFB CPU access disabled. It was suggested early on in this thread but it seems the effect varies with the users, some still have the problem others don't after checking this option box.
Anyway the Dual Core trick is safer for now.

Enable dual core turned off works for me but game becomes very slow

I forgot about this issue for a while but retested it with the latest build I could find (Dolphin 3.0 748).
I played a little bit with the thread set affinity on one core in Dualcore mode and I played with Dualcore mode off. And while it is unplayable for me with the affinity on one core, it is playable with Dualcore turned off even if like the last comment the game slows down. Though at a point in the game when you have to be reactive in battle it becomes unplayable :p.

Hi guys, I ran into this problem today, I believe it happens when selling cards and after the fig with the big serpent at the forest in the beggining, IF you take its picture that is.

I could not reproduce the problem with the following settings.

-Dualcore Enabled.
-JITIL experimental recompiler enabled.
-Lock process on thread.
-DX11 backend.

I tried many things to use dualcore, but in the end the problem solved when I changed to JITIL, it is to early to tell of course, but I'll update if the freeze returns.

Never mind that last fix, it does reduces the number of ocurrences, but it did happen again, bummer.

Issue 5810 has been merged into this issue.

I think I've found a solution for dolphin version 3.0-898 uncheck dual core and turn on JITIL experimental recompiler and (not sure if only works with quad-cores) and the speed will be fine as well as the freezing on photos I haven't done extensive tests on it but the normal audio glitch you will hear when transitioning between highlighted items disappears, Which makes me hope full. As soon as I've tested this to see if it works completely I will re-post with the verdict. (Allthough I won't know if it works with your CPU's specs.)

It works yes but, the speed is down by about 25% you can decrease this deduction almost fully by enabling OprnCL texture decoder and Cache display lists and lastly openMP texture decoder.

The OpenCl and OpenMP decoders are not much help in battles with my config. With your fix, I got fullspeed when exploring but between 20-30 FPS in battles (and this is the moment when you want to be reactive).

battles work fine for me, your computer is probably slower than mine.

Thing is not all configurations or builds work fast with OpenCV or OpenMP. Its depends on a lot of stuff.

I've been using ht above options and the game works for me, but I get huge slow down in areas with water, down to like 65%. Everything else runs 100%.

I just played the game a bit with the test build for your revision.
The game doesn't freeze anymore on photos in Buy/Sell screens (I tested on 3 separate shops in 3 separate saves).
However I did some battles and everytime I take a photo the game still freezes on the loot screen. So the issue is still present in that case.

Thanks for your hard work skidau.

Small update.
I tested the game on 3.5 2440. The game still crashes when viewing a photo on the loot screen but there is now this error message :
"Backpatch: only supporting reads. Attempted to write to 404e3f58"

I forgot to mention it was the x64 version. On x86 I got "DSI exception with stmw" then "DSI exception with lmw" and it cycles between the two.

Ok, I think I find (thk google) a temporal solution for this issue . I'm using the 4.0 - 137 version, windows 8 and a dual core processor. You have to go to Options --> Configure --> General tab --> and uncheck "Enable dual core". If you do that, the problem disappear and the speed in the game doesn't suffer any important change (The speed on my computer is still the same).

I tested with 4.0.1 and the issue is still here (randomly).
But I found a solution in my case that doesn't force you to deactivate the Dual Core option (and experience slowdowns).
In the Game properties I simply unchecked "Synchronize GPU thread" and even if the description says it prevents random freezes, in this particular case it made this freeze disappear. I just finished my playthrough of the game (45+ hours for CD1&2) and I have not encountered a single issue in the game.

kosta, let's remove the sync gpu thread enablement from the game ini as per luckra7's testing and close this issue.

I already did that in latest master and changed it to single core.

where can i download the game? the links ive found online are all corrupted

Please never use the issue tracker again.

"In the Game properties I simply unchecked "Synchronize GPU thread""

This fixed the camera/loot page crash for me as well. Thanks!

The crash still occurs in Dual Core when you hover over a photo magnus that isn't fully developed on the shop sell screen (frequently) or editing your deck (rarely). Disabling Dual Core prevents the crash, but can cause slowdowns. Disabling "Synchronize GPU Thread" did not make any difference for me. Disabling Dual Core temporarily while selling magnus is a workaround, but I wouldn't consider the issue to be "fixed".