Project

General

Profile

Emulator Issues #11546

Metroid Prime Trilogy - Magenta Load Screen then Crash

Added by SoggieWafflz 9 months ago. Updated 7 months ago.

Status:
Working as intended
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 Trilogy

Game ID? (right click the game in the game list, properties, info tab)

R3ME01 (0001000052334d45)

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

da4fc9304933fe9137ecd5e156a1cf07

What's the problem? Describe what went wrong.

When a loading screen for one of the prime games shows up, all I see is a magenta screen, then the emulator crashes.

What steps will reproduce the problem?

portable.txt for fresh settings
disable dual core
bluetooth passthrough
direct 3d 11
asynchronous ubershaders
compile shaders before start
start loading a prime game

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-9567

Is the issue present in the latest stable version?

Passthrough isn't in 5.0, or the shader stuff, but with an emulated wiimote, 5.0 still has a magenta load screen, but doesn't crash.

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

[First broken version number here (if applicable)]

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)

i7-4770k
Radeon RX560 4GB
Win10 Pro x64
Radeon 19.1.1

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

https://youtu.be/oIXIQdpyGZY

History

#1 Updated by Techjar 9 months ago

Is use panic handlers disabled? If so, it's possible an error message is being suppressed.

#2 Updated by JMC4789 9 months ago

  • Status changed from New to Questionable

Turn off "Store XFB Copies to Texture Only" to fix the Magenta loadscreen.

The crash is likely caused by Windows trying to take over the Wii Remote during the ES_Launch. Try turning off bluetooth passthrough. If this works, you may need to completely uninstall your normal bluetooth drivers for this game to work.

#3 Updated by Techjar 9 months ago

Yeah I wanted to verify the error message first, since I'm guessing they've got panic handlers disabled. If that's the case then it's the same issue as https://bugs.dolphin-emu.org/issues/10412

#4 Updated by SoggieWafflz 9 months ago

Techjar wrote:

Is use panic handlers disabled? If so, it's possible an error message is being suppressed.

Panic handlers are enabled.

#5 Updated by SoggieWafflz 9 months ago

JMC4789 wrote:

Turn off "Store XFB Copies to Texture Only" to fix the Magenta loadscreen.

The crash is likely caused by Windows trying to take over the Wii Remote during the ES_Launch. Try turning off bluetooth passthrough. If this works, you may need to completely uninstall your normal bluetooth drivers for this game to work.

Trying to find if I have any bluetooth drivers, I don't think I do. Fairly fresh isntall of win10 and I don't use bluetooth.

#6 Updated by Techjar 9 months ago

That's odd, you should be getting a libusb error popup. In any case I'd still do what JMC suggested.

#7 Updated by JMC4789 9 months ago

Windows 10 has default bluetooth drivers. Did you install WinUSB drivers with zadig?

#8 Updated by Techjar 9 months ago

Specifically, the part about disabling bluetooth passthrough.

#9 Updated by SoggieWafflz 9 months ago

SoggieWafflz wrote:

JMC4789 wrote:

Turn off "Store XFB Copies to Texture Only" to fix the Magenta loadscreen.

The crash is likely caused by Windows trying to take over the Wii Remote during the ES_Launch. Try turning off bluetooth passthrough. If this works, you may need to completely uninstall your normal bluetooth drivers for this game to work.

Trying to find if I have any bluetooth drivers, I don't think I do. Fairly fresh isntall of win10 and I don't use bluetooth.

XFB removed the magenta, and the game launched properly as well. Seems to be working fine now.

#10 Updated by Billiard26 7 months ago

  • Status changed from Questionable to Working as intended

Can't reproduce. Working for user as well now.

Also available in: Atom PDF