Emulator

I will see that when have time :)

I know there are many things that need fixing but, why is it taking so long to take care of this bug? Please, can someone fix it? :)

Maybe the fifo programmers are lazy people...

Maybe the fifo programmers thought they were done with the fifo? :p

Well I find this to be a strange issue. I've had experience with JAVA code but First In First Out errors are rare as far as I've seen. The only thing I can think of that would have the issue occur (I've experienced it myself) would be a call going out to the wrong command. There must be something that a workaround for running the console is interfering with the order. However I believe that I have a different cell being call as the numbers are different as far as I can tell. Even so it doesn't seem that the system is keeping a correct track, like integers aren't being incremented. After checking(was writing this comment and testing) I confirmed the numbers were different the error code is as follows: FIFO out of bounds (sz= 1048558, at 00000000) unfortunately I don't know how the developers labeled their stacks so "sz" could be anything to me. I know this doesn't help much but I hope if someone stumbles upon this they could get some ideas from my interpretation and test experience. On second record I did a playthrough on normal and deadly difficulties which have some minor differences but both have this error occur so this leads me to believe it's the dolphin code that collides with the game code. If anyone has anymore experiences, data, or different stack errors let me know. I'm going to take a crack at this bug fix.

I pursued this error a little more and found out where the problem is likely located. I talked to my dad, who programs for a living, and he told me that the FIFO error is probably generated from one of the buffers, audio or video. We discussed it and decided that since the audio continues as though the system is still functioning but the video ceases to progress that it is a video buffer problem. the next part is trying to decide where the change of variables lies that causes the error, system, application, or iso. It's hard to consider that we get the game from the exact same area so that's most likely out, my system varies from jwr's and many others I've seen who've posted this error so that's most likely out, which leave the application which I assume a workaround from the application to make the games function on an everyday PC is the culprit. Now I don't have the skill, relation to the program, or the time to dedicate to hunting down the code responsible for this but I'm sure it's running rampant on many games similar to Killer 7 so if we could bring this to someone's attention a little sooner I feel it may lead to a major fix with would handle many catastrophic failures in the emulation. Let's try to move this issue up so someone can handle this. Have a nice day.

Does the issue continue to occur if you disable Dual Core mode?

The issue occurs at the exact same point, but now the audio skips as though that buffer had a problem. Although now my number matches jwr's error at 1048555. Could this mean that it may be too much see as dual core makes it a little further?

I just noticed something else. It progresses with different error codes instead of fully crashing.

Regarding audio skipping on single-core (on HLE), I get that on F-ZERO GX (and probably all other games) at low framerates (<20fps), but I don't get it on dual-core at all - audio always runs at full-speed even at the same low framerates.

In this case, I guess it implies that the video's hanging? </paul's_crackpot_theories>

Yeah my thoughts exactly Paul. For whatever reason it's trying to put whatever image in location 00000000 which is just wrong. My dad feels like something isn't being initialized. Either way the error is definitely coming from the application not the iso or the system.

lol

This was fixed years ago. Can't remember what revision though. Hope to see it fixed again soon.

Still here as of 3.0-843

There is a solution; it's not ideal but you'll be able to progress. Open the Config menu, then go to the Interface tab. There should be a box labelled "Use Panic Handlers". If you uncheck this box, when you shoot the angel's wings, the game will slow down considerably (about 2 fps on my laptop), but with a little bit of patience, you will be able to progress through the rest of the game at full speed.

@xjordand
At one point later in the game another effect turns up that causes the glitch again.

But instead of being an event, like shooting something, it's stationary as part of a room. It's impossible to navigate the room at the low framerate.

Issue 5724 has been merged into this issue.