Emulator Issues #7938
closed
GFX FIFO Unknown Opcode in Resident Evil 0 Wii PAL
0%
Description
Game Name?
Resident Evil 0
Game ID?
RBHP08
What's the problem? Describe what went wrong in few words.
After 3-4 minutes into the game I came upon a hang and a FIFO error message appears. After clicking a few times "OK" button (error message changes each time I press OK and it complains about different opcode) the game seems to continue but without video (I can hear only audio and that's how I know that the game still is working)
What did you expect to happen instead?
:)
What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
- Play the game for a few minutes
2.
3.
Which versions of Dolphin did you test on?
4.0-4603
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Not tested, although a month ago I reported another FIFO issue (FIFO overflow) which is now replaced by this issue. For sure the game worked perfectly fine on 4.0-4250 but I suppose this is not much of a help.
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
You can see them on the attached screenshots, but anyways:
Intel Core i5 4690, GeForce GTX 970
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
http://i.imgur.com/Fr31A83.png
http://i.imgur.com/2kifcNJ.png
Updated by skidau almost 10 years ago
Try to find the revision between 4.0-4250 and 4.0-4603 where this issue first started.
Updated by bgtsetso almost 10 years ago
Well, I definitely cannot test 350 revisions since the issue takes various time to reproduce. If you can reduce considerably this number by finding which revs might be responsible for this then of course I can try to find the culprit.
Updated by pauldacheez almost 10 years ago
You don't need to test 350 revisions, just test the one in the exact middle of the range and repeatedly cut your range in half depending on which half of the range the breakage is in. If 4250 works and 4603 doesn't, test ~4427. If that works, test ~4515, and if it doesn't, test ~4339.
Updated by bgtsetso almost 10 years ago
Sure, this an improvement but still this would take lots of time. That's why if there are only, let's say, 7 or 8 revs that could have caused this issue it would be of much help.
Updated by JMC4789 almost 10 years ago
Bisecting it would make it take less than 20 builds.