Emulator Issues #12168
closed
Savestate load issue in Mario Golf: Toadstool Tour
0%
Description
Game Name?
Mario Golf: Toadstool Tour (North America)
Game ID? (right click the game in the game list, Properties, Info tab)
GFTE01
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
5fd9909e73df7fb704d2e443e17346b5
What's the problem? Describe what went wrong.
With 5.0-12226, whenever I load a save state, I get this error:
"After "VertexShaderManager", found 0 (0x0) instead of save marker 66 (0x42). Aborting savestate load..."
No matter where I put a savestate in the game.
What steps will reproduce the problem?
Reverting to 5.0-12219 fixed this problem.
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, issue is in 5.0-12228.
Is the issue present in the latest stable version?
No.
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.)
5.0-12226
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)
Windows 10 1909, i7-7700, 32 GB ram, GTX 1060 6GB video card.
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Just the error image: https://i.imgur.com/5MtMhTd.png
Updated by JMC4789 almost 4 years ago
I guess something we did should have bumped up the savestate version. Either way, savestates aren't meant to be portable between builds, so you should make a game save instead before swapping builds in the future.
Updated by ShadowMario3 almost 4 years ago
JMC4789 wrote:
Either way, savestates aren't meant to be portable between builds, so you should make a game save instead before swapping builds in the future.
This isn't the issue. My save state was created in 12228 (problem started with 12226), and loading that save state causes the error.
I also tested out Super Smash Bros. Melee (GALE01, Version 1.02) on 12228 created a new save on the memory card, created a save state, and tried to load it. Same error occurred.
Updated by ShadowMario3 almost 4 years ago
Can confirm that 5.0-12230 fixes this issue. This topic can be closed.
Updated by JMC4789 almost 4 years ago
- Status changed from New to Fixed
Yeah, sorry. I didn't realize the issue you were reporting! Good catch.