Project

General

Profile

Actions

Emulator Issues #8017

closed

Annoying Crashes in Metroid Prime! (GameCube)

Added by mkikoen6196 over 9 years ago.

Status:
Duplicate
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

[READ THIS: https://forums.dolphin-emu.org/showthread.php?pid=276132 <<<
Your answers are there!]
[Leave the questions as they are and answer them in the next line]
[Remove lines written inside brackets [], but nothing else]

Game Name?
Metroid Prime (GameCube)

Game ID?
GM8E01

What's the problem? Describe what went wrong in few words.
Metroid Prime has crashed at least 10 times now due to the stupid error message saying "FIFO is overflown by GatherPipe, CPU thread is too fast!" This is really infuriating me because I'm tired of these annoying FIFO issues forcing Dolphin to crash! Every time it happens whenever I'm in the underwater area trying to access the crashed Frigate Orpheon by using my Thermal Visor to scan invisible Power Conduits and then use the Wave Beam to activate the Power Conduits to power up the doors. Every time the EFB to RAM is enabled by default, the frame rate of the game underwater and in big areas slow down dramatically and I'm done with this nonsense because this is happening too frequently.

What did you expect to happen instead?
For the game to function correctly, have a smooth frame rate, and to gimme a damn break with the crashing due to these annoying FIFO issues.

What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]

  1. If you guys have played Metroid Prime before and have progressed far enough, First just go to Tallon Overworld. Go to the Frigate Crash Site room. If you have the proper items including the Ice Beam or have the cheats enabled, open the ice door, and just progress until you get to a room called the Reactor Access.
  2. From this point forward, use the Thermal Visor and if EFB to RAM is enabled, you'll start to see the annoyance of the frame rate dropping dramatically - it's most noticeable as hell whenever you rise out of the water itself when EFB to RAM enabled, with EFB to Texture enabled, the slowdown rarely happens.
  3. Eventually in certains rooms, the frame rate will start to slow down so badly to the point where the Dolphin Emulator gives the FIFO Error Message and crashes the game. 😑

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
Dolphin 4.0-4863

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Macintosh OS X Yosemite
Version 10.10.1
iMac (21.5 inch, Mid 2011)
Processor - 2.5 GHz Intel Core i5
Memory - 4 GB 1333 MHz DDR3
Graphics - AMD Radeon HD 6750M 512 MB

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
[Upload big files to a hosting service and post links here!]
Here's the most recent Crash Log of Dolphin regarding the FIFO crashes. The specific numbers of CPU Threads in all of the Crash Logs that crashed are CPU Thread: 0, 7, 8, 11.

[Do not attach files to this issue. Upload them to another site and
link here. Use imgur.com for images and pastie.org for logs. Monitor the
email address that was used to create this issue.]


Related issues 1 (1 open0 closed)

Is duplicate of Emulator - Emulator Issues #7143: DualCore Timing Mega IssueAccepted

Actions
Actions

Also available in: Atom PDF