Project

General

Profile

Actions

Emulator Issues #11721

closed

Metroid Prime and Okami throw FIFO Unknown OPCode errors when using Vulkan

Added by FireNX70 almost 5 years ago. Updated almost 5 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
Yes
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
5.0-10063
Fixed in:
5.0-10179

Description

Game Name?

Metroid Prime(PAL) and Okami(PAL).

Game ID? (right click the game in the game list, Properties, Info tab)

Metroid Prime:
GM8P01

Okami:
ROWP08

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

Metroid Prime:
b1379c44e0ebc521e18215de3e5dbeea

Okami:
86b621b0dce79d6397d5f9bb2fe90a22

What's the problem? Describe what went wrong.

This only happens when using Vulkan.

Dophin throws a GFX FIFO unknown opcode error (Illegal command 56) when launching Metroid Prime(PAL) and Okami(PAL). Despite this, the games runs normally after closing the error dialogs. I tried turning off Dual core and it still happens.
Metroid Prime's error says Illegal command 56 whereas Okami's says Illegal command 17.

What steps will reproduce the problem?

Choose Vulkan as the video backend and launch any of those two games.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Yes, 5.0-10167

Is the issue present in the latest stable version?

5.0 works fine.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

Happens from 5.0-10063 onwards.

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

Can only start recording fifologs after the error has occurred.

What are your PC specifications? (CPU, GPU, Operating System, more)

Intel Xeon E3-1241v3 (Equivalent to a 4770)
nVidia GTX 1080Ti (430.39 Drivers)
Windows 10

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

All hacks except for Disable bounding box are turned off and texture cache accuracy is set to safe.

Actions #1

Updated by JMC4789 almost 5 years ago

This is likely due to the Monster Lab fix. There's probably a hack somewhere else in Dolphin's FIFO to make up for the broken behavior we just fixed...

Actions #2

Updated by FireNX70 almost 5 years ago

Fixed by 5.0-10179

Actions #3

Updated by JosJuice almost 5 years ago

  • Status changed from New to Fixed
  • Regression changed from No to Yes
  • Regression start set to 5.0-10063
  • Fixed in set to 5.0-10179
Actions

Also available in: Atom PDF