Emulator Issues #9075
closedSuper Paper Mario crashes during the prolog
0%
Description
Game Name?
Super Paper Mario
Game ID? (right click the game in the game list, properties, info tab)
R8PP01
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
38048fdd50616374cae924adf1eafe0d
What's the problem? Describe what went wrong.
Game crashes during the prolog with the error "Memory stride too small".
What steps will reproduce the problem?
Boot game up, start a new save, skip through the cutscene, the crash happens when Bowser's castle fades out.
Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?
4.0-8133
What are your PC specifications? (CPU, GPU, Operating System, more)
i7 3770k
AMD 7970
Arch Linux
Open source radeon drivers
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Phire said it could be a bounding box issue.
Updated by Anonymous about 9 years ago
Not necessarily related to #8956 since this is a different game.
Updated by phire about 9 years ago
- Related to Emulator Issues #8956: Memory stride is too small added
Updated by wildgoosespeeder about 9 years ago
I'm trying to reproduce the problem for Dolphin Wiki's sake and can't. Unless the bug is fixed, I need to see a demonstration.
4.0-8137
Updated by Anonymous about 9 years ago
Well that's weird, I'll make a video of it tomorrow. Which OS are you trying it on ?
Updated by phire about 9 years ago
wildgoosespeeder, Make sure you have panic handlers enabled, otherwise dolphin silently discards the error.
Updated by Anonymous about 9 years ago
Right, that's important. If panic handlers are turned off the game will freeze with a buzz for me.
Updated by Helios about 9 years ago
Might be worth including which version of Mesa you're running, since you're on open source drivers.
Updated by wildgoosespeeder about 9 years ago
Panic handlers are always on. I tested this in Paper Mario: TTYD and have it happen there.
Windows 8.1
NVIDIA GeForce 610M
12GB PC3-12800
Intel Core i5-3210M @ 2.5 GHz
Updated by Anonymous about 9 years ago
Super Paper Mario is not TTYD. There's already #8956 for that, I opened a new issue because it's not the same game.
Updated by wildgoosespeeder about 9 years ago
Streetwalrus wrote:
Super Paper Mario is not TTYD. There's already #8956 for that, I opened a new issue because it's not the same game.
I know that. I have noted that other issues associated with PMTTYD and SPM are shared, such as bounding box, EFB2RAM, and Direct3D having issues because the engines that power both games are shared. I was trying to say that I have panic handlers on because I was able to trigger the weird message but not specially SPM:
https://wiki.dolphin-emu.org/index.php?title=File:TTYD-MSITS.png
Updated by Anonymous about 9 years ago
Sorry, I misread your comment. Video is transcoding, will upload once it's done (if ffmpeg decides to finish one day).
Helios: Mesa 11.0.4.
Updated by Anonymous about 9 years ago
Here's the video: https://sr.ht/YV9M.webm
Updated by wildgoosespeeder about 9 years ago
Streetwalrus wrote:
Here's the video: https://sr.ht/YV9M.webm
Can you upload to Imgur (or YouTube to Imgur using Video-to-GIF)? I can play the WEBM in VLC Media Player but for Wikipedia, it might be best to have it in either YouTube or GIF format. Imgur has the ability to convert WEBM, MP4, and GIFV into GIF for backwards compatibility.
For example:
http://i.imgur.com/Grib4T4.mp4
http://i.imgur.com/Grib4T4.gif
Updated by Anonymous about 9 years ago
I think he means MediaWiki, for the Dolphin wiki. Webm is supposed to be embedded in web pages, doesn't MW support embedding videos with ?
Updated by wildgoosespeeder about 9 years ago
Streetwalrus wrote:
Here's the video: https://sr.ht/YV9M.webm
OK, three things I noticed:
First, Linux. I'm using Windows 8.1. I wonder if that has anything to do with it.
Second, you had to create a new file. I extracted the save from my real Wii for use in Dolphin thanks to SaveGame Manager GX, a homebrew app.
Third, my MD5 checksum is fe441d77d5cb9a7f01de954e84e6ca49 (R8PE01). Yours is 38048fdd50616374cae924adf1eafe0d (R8PP01). Bad dump?
Updated by wildgoosespeeder about 9 years ago
Streetwalrus wrote:
I think he means MediaWiki, for the Dolphin wiki. Webm is supposed to be embedded in web pages, doesn't MW support embedding videos with ?
Yeah. Wrong place. I meant Dolphin Wiki. :P
Updated by Anonymous about 9 years ago
No, you have a US copy of the game, I have a PAL copy.
Updated by JosJuice about 9 years ago
The MD5 is obviously going to be different if the discs aren't from the same region. 38048fdd50616374cae924adf1eafe0d gives me a bunch of good search results, so I don't think that's the problem.
Updated by wildgoosespeeder about 9 years ago
Streetwalrus wrote:
No, you have a US copy of the game, I have a PAL copy.
Is the PAL copy a good dump?
Updated by wildgoosespeeder about 9 years ago
JosJuice wrote:
The MD5 is obviously going to be different if the discs aren't from the same region. 38048fdd50616374cae924adf1eafe0d gives me a bunch of good search results, so I don't think that's the problem.
I'm aware. Just ruling out some things.
Updated by Anonymous about 9 years ago
As far as I can tell by googling my hash, yes my copy is good.
Updated by wildgoosespeeder about 9 years ago
Streetwalrus wrote:
As far as I can tell by googling my hash, yes my copy is good.
The tests:
- Linux
- New save file vs. extracting a save from a real Wii for use with Dolphin
Bad dump
Updated by Anonymous about 9 years ago
I've just reinstalled windows, will test on there asap.
Updated by wildgoosespeeder about 9 years ago
Streetwalrus wrote:
I've just reinstalled windows, will test on there asap.
I think your issues might be related to being specific to the PAL region. I created a new save and I still didn't get a crash. Linux, not sure if that is a factor. I can't test that. To conclude the issue might be related to:
- PAL (most likely)
- Linux
Updated by Anonymous about 9 years ago
I'm unable to reproduce the issue on the same machine on Windows 10 with the latest beta of Catalyst drivers, running on the OpenGL backend.
This leads to two possibilities:
-Dolphin bug on Linux
-Bug in the driver (more likely)
Updated by wildgoosespeeder about 9 years ago
Streetwalrus wrote:
I'm unable to reproduce the issue on the same machine on Windows 10 with the latest beta of Catalyst drivers, running on the OpenGL backend.
This leads to two possibilities:
-Dolphin bug on Linux
-Bug in the driver (more likely)
If you can update/backdate the driver for Linux, please report back! I have a feeling it is Linux Dolphin instead.
Updated by Anonymous about 9 years ago
Closest I can do is booting up a slightly newer kernel (I run Linux-ck which is not always in sync with the stock Arch kernel), and that doesn't help.
I've been trying to downgrade Mesa but due to some version dependency maze, I can't get GL to work with an older version (10.6.x). The easiest and most effective way to pinpoint this to the driver would be to install Catalyst but I don't really want to do that for now.
Updated by Anonymous about 9 years ago
New Mesa update (11.0.5) didn't solve the issue, I dived in and installed catalyst, on which it works. Driver issue is confirmed I guess.
Updated by Anonymous about 9 years ago
Just to make extra sure I tested again on Mesa in software rendering mode (not the Dolphin feature), and I'm getting the same issue. As I can't downgrade Mesa, it's hard for me to figure out when the bug was introduced, but the 11.0 update seems the most likely.
Updated by phire about 9 years ago
- Status changed from New to Invalid
Ok, on the hacks screen of the video options you have "Disable Bounding Box" checked.
Uncheck it, and you find the bug will go away.
Updated by Anonymous about 9 years ago
This setting is overridden by the game INI, disabling it doesn't help.
Updated by phire about 9 years ago
- Status changed from Invalid to Questionable
Weird.
I only managed to reproduce this bug when I force that option on.
Perhaps it's a dual core issue. Can you re-produce this in single core mode?
Updated by Anonymous about 9 years ago
Yes, still the same issue in dual core mode.
The only parameter that seems to have changed anything up until now is Mesa vs Catalyst, on which I can't reproduce the issue.
Updated by MayImilae almost 9 years ago
- Related to deleted (Emulator Issues #8956: Memory stride is too small)
Updated by MayImilae almost 9 years ago
- Status changed from Questionable to Duplicate
I asked delroth, and he said they should be marked as duplicates, just as we have always done. So, changing!
Updated by MayImilae almost 9 years ago
- Is duplicate of Emulator Issues #8956: Memory stride is too small added