Emulator

Game Name?

Manhunt 2

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

RHTE54

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

f8291f1fb37eb437d84e40cd5e1217a7

What's the problem? Describe what went wrong.

There's two different ways things can go.

Single Core

When booting the game, after the Wii Strap Screen, the game screeches to a halt. It will run ~1 FPS through the Rockstar logo video. If you skip the first FMV, the main menu and actual gameplay run at normal speed.

Dual Core

Same thing happens, but the FPS will bounce around from 0 to 30, to 60, to 24, etc. etc. and eventually lock up with an unknown opcode.

What steps will reproduce the problem?

Boot the game, changing between Single Core and Dual Core for the two behaviors.

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

5.0-17713

Is the issue present in the latest stable version?

Yes

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.)

N/A

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

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

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

AMD 5950x, RTX 3060, Linux

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

Increasing the Emulated CPU clock to around ~184% seems to rectify the issue but I'm not entirely sure how/why. This seems like an odd failure state.