Project

General

Profile

Emulator Issues #12376

Metroid Prime 2: Echoes hangs on title screen

Added by Interslice about 2 months ago. Updated about 2 months 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:
Fixed in:
5.0-13424

Description

Game Name?

Metroid Prime 2: Echoes

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

GM2E01

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

ce781ad1452311ca86667cf8dbd7d112

What's the problem? Describe what went wrong.

Dolphin freezes shortly after pressing start on the title screen.

What steps will reproduce the problem?
Press start on the title screen

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

Is the issue present in the latest stable version?

No, 5.0

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

This issue was not present in 5.0-13240

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)

Arch Linux Kernel 5.9.14
i7-6700
RTX 2060 Super

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

Appears to happen only on Linux. I never got an error message for my crash but another user did. https://cdn.discordapp.com/attachments/586296076424839180/794947716584964116/unknown.png

History

#1 Updated by Interslice about 2 months ago

Game ID is actually G2ME01

#2 Updated by Miksel12 about 2 months ago

Did you try without dualcore?

#3 Updated by JMC4789 about 2 months ago

The bisect doesn't make any sense, as it refers to a build that added 360 degree rotation support to Wii Remotes. I'm guessing that it's not a bisect and just the last build you used before updating? If so, can you please do a proper bisect. It would make this a lot easier.

#4 Updated by JMC4789 about 2 months ago

  • Status changed from New to Questionable

I was going to try to bisect this for you, but I ended up not being able to reproduce this.

You have to find the exact build that is causing your regression. Also, please try to make sure that you check any possible settings that could contribute to it. Figuring out both may make narrowing down what changed even easier.

#5 Updated by Interslice about 2 months ago

After attempting to bisect the issue, I was not able to reproduce on a clean clone of the repo. I suspect this issue was caused by building over an older version.

#6 Updated by JosJuice about 2 months ago

  • Status changed from Questionable to Invalid

That's strange... But I'll mark this as closed, then. Let us know if the problem happens again.

#7 Updated by merry about 2 months ago

Bisected to d06d59e9c2cef995fc3933d72a928cef456b230d, however PR 9262 was not direct cause.

Narrowed down to this specific PPC instruction sequence at 80258b24:
~~~
li r0, 2
subfic r0, r0, 2
li r5, 0
cntlzw r3, r0
~~~

#9262 introduced an optimization to handle immediate arguments for subfic.
This allowed cntlzw to be optimized away as r0 was now an immediate (r0 = 0).
However, #9374 introduced a bug for this optimization.

Fixed by #9422.

#8 Updated by JosJuice about 2 months ago

  • Fixed in set to 5.0-13424
  • Regression changed from No to Yes
  • Status changed from Invalid to Fixed

Also available in: Atom PDF