Project

General

Profile

Emulator Issues #12334

[GC] Unknown opcode errors in Metroid Prime

Added by jstolarek 3 months ago. Updated 3 months ago.

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

0%

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

Description

Game Name: Metroid Prime
Game ID: GM8E01
MD5 Hash: fdfc41b8414dd7d24834c800f567c0f8

The game occasionally crashes with unknown opcode error - see screenshots. Dolphin window then freezes. If I'm lucky I'm able to close the emulation window normally, if not I have to kill Dolphin. Happens randomly every couple of hours of gameplay. Once happened immediately after saving emulator game state, another time upon entering the menu.

Is the issue present in the latest development version?

Happens on version 5.0-13117 built from sources about two weeks ago. Current development version is 5.0-13178. I've not tested on stable versions.

What are your PC specifications?

Specs: Ryzen 9 3900X, nVidia GTX 2070 Super, Debian Buster (Linux 64bit), kernel 5.7.0, proprietary nNidia drivers v440.100

I'm attaching screenshots of the error message. The first screenshot shows one of two error windows when the crash happend upon entering game menu. The other two screenshots show error windows for the crash that happened after saving emulation state. Importantly, saving emulation state worked correctly and upon restarting the emulator and loading the state everything works correctly. Error message mentions error backend logs, but I was unable to locate those - .local/share/dolphin-emu/Logs/dolphin.log is empty. If someone can tell me where to look for these logs or how to enable them I can then provide more information.

mp_second_crash_a.png (53.9 KB) mp_second_crash_a.png Crash after saving emulation state, part 1 jstolarek, 12/05/2020 09:33 PM
mp_first_crash.png (106 KB) mp_first_crash.png Crash upon entering the menu (Start key) jstolarek, 12/05/2020 09:33 PM
mp_second_crash_b.png (39.8 KB) mp_second_crash_b.png Crash after saving emulation state, part 2 jstolarek, 12/05/2020 09:33 PM
startup_unknown_opcode_a.png (42.9 KB) startup_unknown_opcode_a.png jstolarek, 12/07/2020 04:00 PM
startup_unknown_opcode_b.png (39.9 KB) startup_unknown_opcode_b.png jstolarek, 12/07/2020 04:00 PM
8105
8106
8107
8110
8111

History

#1 Updated by JMC4789 3 months ago

This is probably just the usual dualcore issues. Try seeing if this happens with dualcore disabled. Your computer should be more than strong enough.

#2 Updated by jstolarek 3 months ago

I'll try. Give me a few days to see whether it makes a difference.

#3 Updated by jstolarek 3 months ago

8110
8111

@JMC4789 I tried disabling dual core for Metroid Prime and I'm still seeing errors. Interestingly now they happen when starting the game (roughly 50% of time) but don't crash the game. When I say they happen at startup I mean that when I launch the game this error is literally the first thing that shows up, even before Nintendo logo.

#4 Updated by JMC4789 3 months ago

yes, that's to be expected. There's some kind of timing error when setting up the initial VI. There should be none when you actually get in game with single core though.

I should have mentioned the startup issues in single core, I forgot Metroid Prime was one of the games that did that.

Also available in: Atom PDF