Emulator Issues #13334


Super Paper Mario Chap 6 UNPLAYABLE

Added by enderyl 7 months ago. Updated 5 months ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Game Name?

Super Paper Mario

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

R8PE01 (0001000052385045)

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


What's the problem? Describe what went wrong.

In 19890 to 19939, Chapter 6 will open and begin as normal. After beating the Jade Blooper, cutscene begins. When King Sammer says "Vessels, come to me!" the scene pans to a set of doors which will open and then immediately freeze the game. Display will freeze to either a black screen or the last frame of the doors opening, and droning sound will play (from the game because it can be muted). Escaping and/or stopping the simulation WILL NOT WORK, you have to force exit. Luckily the file will not corrupt, and you can continue playing in Flip/Flopside and already completed chapters, but you cannot progress in the storyline/game.

In 19951, the door to Chapter 6 is completely inaccessible as it causes the emulator itself to crash. The whole computer screen will go black (fullscreen or not), all Dolphin windows close. Save file still accessible and you can play Flip/Flopside and already completed chapters.

What steps will reproduce the problem?

Open the chapter 6 door (I've only tested this as first-time entry) and play past the Jade Blooper. The cutscene will then initiate and cause the freeze.
After updating to 19951, chapter 6 cannot be played to this point as it will crash shortly after opening the door to the chapter, if it opens the door at all.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Issue present in development version Dolphin 5.0-19939 (Chap6 freezes in cutscene) and the very newly added 5.0-19951 (game crashes when opening Chap6 door).

Is the issue present in the latest stable version?

Issue present in latest stable/beta version, Dolphin 5.0-19870.

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 and anyone who is building Dolphin on their own can use git bisect.)


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:

Screenshots included:

  • 140747--The doors begin opening in the cutscene
  • 140756--Doors are open; game freezes
  • 140142--Game occasionally will freeze on a black screen instead of the one above


  • 163011--Mario right before entering the chap6 door. When entered, screen will turn black and emulator crashes.

Fifoplayer won't work for me (and yes I checked/unchecked everything the Dolphin fifoplayer guide told me to); unable to finish recording and save it.

What are your PC specifications? (CPU, GPU, Operating System, more)

Windows 11 Pro v22H2
Dell Vostro 14 5410
11th Gen Intel(R) Core(TM) i5-11320H @ 3.20GHz 2.50 GHz
x64-based processor
Intel(R) Iris(R) Xe Graphics
(If something else is needed let me know)

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

Prior chapters don't have any issue loading and don't have any notable instability. Chap 6-1 also has no issues before the freeze point (in 19939 and prior). The savefiles seem to be working properly but I don't really know. As for 19951, you can't even open the chapter. I would have these in separate bug filings but the problem is in the same spot, chapter 6, and I updated to 19951 and discovered this mid-writing. It is possible that this bug could affect the opening of any unplayed chapters but I cannot confirm so.
Sorry for the long one.


Screenshot 2023-08-18 140747.png (1.47 MB) Screenshot 2023-08-18 140747.png doors begin opening in cutscene enderyl, 08/18/2023 08:14 PM
Screenshot 2023-08-18 140756.png (1.43 MB) Screenshot 2023-08-18 140756.png door open frame that game freezes on enderyl, 08/18/2023 08:14 PM
Screenshot 2023-08-18 140142.png (10.4 KB) Screenshot 2023-08-18 140142.png game will sometimes freeze on a black screen after door opens enderyl, 08/18/2023 08:14 PM
Screenshot 2023-08-18 163011.png (1.28 MB) Screenshot 2023-08-18 163011.png game right before entering chap6 door, causes emulator crash when entered enderyl, 08/18/2023 09:32 PM
Screenshot 2023-08-18 233835.png (771 KB) Screenshot 2023-08-18 233835.png the vassals actually arrive enderyl, 08/19/2023 04:39 AM
Actions #1

Updated by enderyl 7 months ago

I HAVE FOUND A WORKAROUND! After digging in the dolphin forums era 2012, changing settings so that Immediately Present XFB is ON somehow fixed this problem, which is a little bit confusing because I was looking at bounding box (that was the issue back then along w/ other graphical errors). I'm going to keep Immediate XFB on now just in case. After hours of distraction and frustration, I can finally get past the dreaded vassals. this is on dev version 5.0-19951.

(Side note. Game totally crashing on 19951 was actually something I changed deep in my settings in an attempt to fifo. Once I got that fixed up, 19951 went back to reacting the same that the other versions did.)

Screenshot of after the doors open attached.

Actions #2

Updated by NanoExplorer 5 months ago

Hello, I am encountering this issue on 5-20193 and 5-19870 for MacOS 13.5.2 on M1 Max (Macbook Pro).

The specific issue is that the game freezes and plays a loud buzzing sound when the door opens after the "Vassals, Come to me!" quote.

I attempted turning on Immediately Present XFB, but this does not appear to change anything. I think I'll try the 19951 build to see if this is specifically a MacOS issue.

Actions #3

Updated by NanoExplorer 5 months ago

Ah hah, this only happens when the backend is Metal. With backend OpenGL there are many error messages when the game first starts, but at least I can get past the door opening issue.

Actions #4

Updated by OatmealDome 5 months ago

Note that OpenGL has no support for bounding box on macOS, which this game uses extensively. You will encounter other problems if you continue playing on OpenGL.

Looking at some past issues, it appears this might be a dual core timing issue. (

Perhaps disabling Dual Core (Config -> General tab) will fix the problem.


Also available in: Atom PDF