Emulator Issues #5415
Killer 7 "FIFO out of bounds"
1) Game Name and ID (as it appears in right click > properties: "GZ2P01",
2) What is the expected output? What do you see instead?
Shooting the angel's wings near the end of the first level should cause an explosion of feathers(this is probably what causes it). Instead as soon as you pull the trigger a message box pops up with
FIFO out of bounds (sz = 1048555, at 00000000)
Music continues to play, and the level geometry and HUD are still there, but the angel herself is no longer visible.
Dolphin freezes up and has to be force closed.
3) Did the game ever work correctly (i.e. not have this problem) on an
earlier version of dolphin? Please specify the exact revision when the
As far as I know this issue has always existed.
4) What steps will reproduce the problem?
1.Get to this point in the game
2.Shoot one of the Angel's wings
5) What version of dolphin are you using (32bit/64bit along with the
version as it appears in the title bar, etc)? Do not say 'latest version'
this changes multiple times a day.
On what operating system, drivers, and hardware? Be sure to list OS,
graphics driver information, and video card model if you are having
graphics problems, for example.
AMD Phenom II X4 955 @ 4GHz
nVidia GeForce GTX 560 Ti; driver version 296.10
6) Please provide any additional information below.
There was issue 3896 which was the same Issue, but was merged into issue 3694, for general FIFO issues. But apparently that has been fixed and any FIFO related issues are game issues, so this would be relevant again.
7) Attachments. IMPORTANT! We have a limited storage quota on
GoogleCode, so please use a 3rd party host for screenshots or any other
files (http://min.us/ for example).
Here is a save file right before the boss in case anyone wants to test it
#5 Updated by Semi.Pacifist over 8 years ago
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.
#6 Updated by Semi.Pacifist over 8 years ago
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.
#10 Updated by pauldacheez over 8 years ago
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?
#11 Updated by Semi.Pacifist over 8 years ago
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.
#15 Updated by xjordandavisx about 8 years ago
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.