Emulator

upload somewhere savestate close to this place with error. i will try to find more about this problem

I got the same problem too, I tried dolphin 32&64 bit with win7 64 bit (notebook samsung r478)
Please look for us if u can. A thousond thanks
this my save file (sorry u need to enter the nearest door from save point and kill the ghost at the end of the path.I want to upload savestate but it's always crash so I upload save file instead hope it work)
yhanks again

you din't uploaded memory card file :P
it should be called MemoryCardA.EUR.raw

I found the fixed solution.
You can follow this instruction ,unfortunately, it is chinese.
http://www.netatlantis.com/?p=2851

But it is well reading via google translate

http://translate.google.com/translate?js=n&prev=_t&hl=zh-TW&ie=UTF-8&layout=2&eotf=1&sl=zh-CN&tl=en&u=http%3A%2F%2Fwww.netatlantis.com%2F%3Fp%3D2851

Now I will try from what you upload Thank you very much both of you mr.kos...@marinenet.jp and mr.mcpm...@gmail.com Im really appreciated it...
Thanks again so now I might finish this lovely game :)

Ah I cant bypass it ...
maybe because I dont understand what exactly I must do... oh poor google translate ...
by the way now i try dolphin r7317 and I can use savestate now, This is my save state for ff4 >>> in slot 3 after 3 seconds the game will crash...
Could u look for me, please??

this is mysavestate file, Thanks in advance.
http://www.sendspace.com/file/3s1m83

hm... i do not see third slot save state here, only the last over writed state - lastState.sav and R4ZJ01.s01 that is first slot save state and more then that - it's corrupted when extracting :P
better upload both: GC folder (there is memory card) and save states folder

and Wii folder is also needed as i see O_o

I dont know why but the real file size is 116 mb but at sendspace it's just 25 mb?
but now I hope that it's would b... now save state with wii and gc folder
http://www.sendspace.com/file/ve9rst
thanks you guys

oh i can't find an place where to fight a ghost. i loading from third slot of memory card. then entering the closes door i see.. there is a labber down and two more doors. the one leads to some open place (maybe on the top of building) with water place that reflects the moon, the second room leading to another room with thing where i need switch some rumbles, but i don't know an order.
if i enter to another door from the save point (i can say the door from where madoka and her companion enter this building in the begin) there are many tables, on the one of those some shining object, if i try to pick it up, the ghost hand captures girls hand and i can't free from it, since emulated wii mote works bad for shaking, so staying like that forever -_-
could you maybe make an map where i need to go from save point?

and save states isn't loadable... they all crashes. actually i didn't expected anything else

Thanks again kos...@marinenet.jp, please excuse my manner for unclear-explaining...
I think that u can figure it out without the map.

• loading from third slot of memory card.
• entering that closes door (u entered the right one). There is a ladder down
  and two more doors. left and right.
• choose the left one that leading to another room with thing where u need to
  switch rumbles (the very same room that u entered), switch in order up up down
  down up.
• after switched u will see the ghost enter another door follow it.
• walk until the end of the path, pick up lens and back to where u from
• when u try to open the door the ghost will attack u, finish it and when it
  done the game will crash...

ok i found where it crashes. very weird crash, but i will try to fix it :P it need for me also, i want to play ff4 as well :D

that's hard to fix for someone that don't know how all this code works. i spend 5 hours on that and well... i can get rid of crash, but then it just hangs :P
this must be fixed by someone who know this code as native thing.

i can only help via showing where it crashes. but sad, i don't think any developers will check this ticket again, this is already old and out of their interest :(
void CCPU::Run()
{
Host_UpdateDisasmDialog();

while (true)
{

reswitch:
switch (PowerPC::GetState())
{
case PowerPC::CPU_RUNNING:
//1: enter a fast runloop
PowerPC::RunLoop(); //<-- crash here (actually in RunLoop(), but the pointer shows here)
break;

Ahhhh Its really sad ... "this is already old and out of their interest:("
Hope that someone might fix it soon. for what I think that it not happen for this good game only...
Its might be old but if they want to play it badly like us I think maybe they will try .... I just know a little of action script and it cannot help anything here...
thanks my dear friends for ur hard work...

i created a new ticked directly about this crash, but not about ff4 :P maybe some developers will find it fixable and fix soon. and np :P let's hope we can play ff4 someday

So basically, you commented out that backpatch error, which by the way, is a real error.
and then made a bug report on a modified version of dolphin, specifically bypassing the notification of said bug. This sir, is a dup.

Issue 4244 has been merged into this issue.

nope, this ticked belongs to ff4, my ticked belong to issue with second time start of cpu_core_base while game executing :P
and i do not commented or changed anything in dolphin sources when i showed crash place. i don't know how peoples getting back patch errors. under debugger it just crashes where i showed. without debugger (for me) it just crashes with question send or not send report to MS.
Whoooho. developers saw this problem one more time :D

Right, then backpatch is a long old known bug and no one quite knows how the code works to fix it, also no one really cares enough to fix it.

could you say maybe is it normal that emulator tries to call this function again while game play? doesn't it must be called only once at game start?

Dolphin starts out in interpreter which runs there, and then later it runs it's JIT which crashes out and that's as far as regular debuggers can debug the failure to

Wow... The conversation of programmers... u guys r rock...

From: http://forums.dolphin-emulator.com/showthread.php?tid=353&page=22

Emulator crashes after fight with the ghost near electric near the end of
Chapter 4. Tried rev 5152, 5286, 4664. Can anybody help? Or other question:
what revision I need to play this game?

look back a few pages, there was the solution. You have to go up first and
after some cutscene go back down to kill that guy. Then it won't crash

yes, i just tested it and then no crash after ghost defeating.
and that function RunLoop() doesn't called at all this time. what a weird thing O_o

Yahooooooooooooooooo At lease we bypass it even we dont know what is it problem...Its time to hunt ghosts again friends.Thanks for u all...:)

Issue 4360 has been merged into this issue.

wasn't this fixed a loooong time ago? i mean i finished this game already (around 1 or 2 years ago) and had nothing to report as the game worked perfectly (after the fix for HLE wich made the game freeze)
I remember having this kind of errors with the wrong english patched version of the game.

Issue 4244 has been merged into this issue.

This is not fixed... There is bypass way to avoid crash by choosing different game events flow. The guy in comment #28 meant the bypass way or didn't even knew about crash.
He provide a saves, starting from that save if you go to ghost and fight it, then in crash after victory, if you go to elevator, then it not crash

I mean ticket starter's saves, not a comment #28 poster

For unknown reason after you win the ghost, game attempt to call PowerPC::RunLoop() function second time after started the game. I believe this should be called only once, at game startup.

I described things here http://code.google.com/p/dolphin-emu/issues/detail?id=4244, but developers renamed it to Fatal Frame 4 related ticket and after that closed, but that ticket was about crash if ANY game call PowerPC::RunLoop() second time.

So what happens as i see it... For unknown reason first loop interrupts (couch error with return operator or etc), then code attempt to start loop again, then crash

If anyone interested, now I have the save data with the way to the crash...
I using dolphin-master-4.0-1516 and this hasn't changed since that long times.
Same place, same ghost, same crash.
Attaching memory card archive to here, so it will never got deleted again like the old memory card file on sendspace.com
The video how to reach crash: http://youtu.be/BiOmV82rlyI

metafalica, has this issue been fixed in the latest development version (Dolphin 4.0-3347)?

instead of crashing, this time emu juts hanged after victory, with 0 fps.
http://filebeam.com/a5cba5e328ea9889b8a222f2d796881c.jpg

I've just tried FF4 with 4.0-4837 and with panic panic handlers disabled the game doesn't crash after beating that ghost...with panic handlers enabled instead I get an almost infinite loop of "invalid read at 0x21251086, PC = 0x80059bb4" (since without that error messages the game doesn't crash, maybe spending some minutes with the enter key pressed to skip them, will make the game continue without crashing as well...)

I spent more than 2 hours with the ENTER key pressed (don't worry, not by myself, I put a weight on it ;-) ) and panic handlers still showed up, so at the moment the only way to avoid the crash is to have panic handlers disabled (a "skip all" option for panic handlers in this case would be very useful)

I confirm that this issue get completely fixed (no more almost infinite panic handlers messages) by enabling MMU in game properties

coming across this issue aswell its not fixed

unless the work around is considered a fix I guess

MMU is enabled by default for this game, so this is indeed considered fixed. You shouldn't be able to run into this unless you're messing with the GameINIs or are using one of those prepatched versions that change the gameid.

Pikachu025 wrote:

MMU is enabled by default for this game, so this is indeed considered fixed. You shouldn't be able to run into this unless you're messing with the GameINIs or are using one of those prepatched versions that change the gameid.

i have it correctly patched so no thats not the issue. the hand can only be avoided by the going back up workaround in chaptor 4