Project

General

Profile

Actions

Emulator Issues #8809

closed

Paper Mario: The Thousand-Year Door battle crash

Added by EranStockhammer almost 10 years ago.

Status:
Invalid
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?
Paper Mario: The Thousand-Year Door

Game ID?
G8MP01

What's the problem? Describe what went wrong in few words.
When mario attacks an enemy, the game crashes.

What did you expect to happen instead?
The game to continue.

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. Start the new game
  2. Get into a fight
  3. Use your jump or hammer

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

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

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Mac OS X Yosemite 10.10.4 CPU:2.4 GHz Intel Core i5 GPU: Intel HD Graphics 3000 384 Mo

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

Actions #1

Updated by pauldacheez almost 10 years ago

  • Status changed from New to Invalid

Intel HD Graphics 3000

Yeah, uh, this is definitely the cause. Under OS X's drivers, it doesn't properly support more than a few things Dolphin uses – OS X tries to help by using its software renderer whenever necessary, but this doesn't play nicely with games in dual-core mode because it's so slow. Taking too long to render a frame usually causes the game to crash or freeze like this. (Single-core mode makes the game wait for graphical rendering to finish before doing anything else, so it doesn't have this issue.)

You can fix this by unchecking "Enable Dual-Core" in the main config, but you can fix it better by throwing your current Mac out a window and replacing it with literally any recent Mac with a proper dedicated GPU that'll have some semblance of reasonable and functional OpenGL support.

Actions

Also available in: Atom PDF