Emulator Issues #12458
open
Crash when starting multiple new games in Summoner
0%
Description
Game Name?
Summoner: A Goddess Reborn
Game ID? (right click the game in the game list, Properties, Info tab)
GS2E78
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
8067dc66f5da7126a7777c1a3beb616e
What's the problem? Describe what went wrong.
Game freezes at certain points. This presents firstly as popups with read/write errors though.
What steps will reproduce the problem?
Start Game.
On main menu select new game.
Press start and select skip for all cutscenes and dialog prompts.
When you get ingame press start and select quit.
Read/Write errors question popups occur here. (Ignore)
On main menu select new game.
Press start and select skip for all cutscenes and dialog prompts.
Game should freeze before you get ingame second time. (Repeat if not frozen, should freeze first time around though)
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, 5.0-13901
Is the issue present in the latest stable version?
Yes, 5.0
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.)
First Broken build is FIFO-BP-3.5-436-x64 -> https://dolphin-emu.org/download/dev/e69c58ee8919b4c5f575b3e28b5a56b3fa265164/
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)
i7-8750H
GTX 1060
Windows 10
8GB DDR4
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Revisions prior to 3.5-644 work fine.
This commit that broke this game was merged into master in 3.5-644 -> https://dolphin-emu.org/download/dev/83fc5f4747f9c8c6066bf002730827ecc17458aa/
The game failed to get past the loading screen after the bisected build.
There was a fix to make it get past the loading screen in 3.5-1337 -> https://dolphin-emu.org/download/dev/98e8f8d7d052be619545f9acc0d79c9145a7e14c/
I forced external exceptions in the same commit that introduced the problem and all it did was get past the loading screen. I also tried different values passed to the ForceExceptionCheck() but it doesn't solve the issue.
Please request more info if required.
Updated by JMC4789 over 3 years ago
- Status changed from New to Fix pending
Full MMU is needed to play this game. I was unable to reproduce opcode issues.
Updated by JosJuice over 3 years ago
- Status changed from Fix pending to Fixed
- Fixed in set to 5.0-14649
The INI PR was merged in https://dolphin-emu.org/download/dev/47d847d4686dc347d10fb005e2c55a5bf87ab3af/
Updated by ZephyrSurfer over 3 years ago
The issue is not resolved.
Following the same set of steps in the report still causes a crash.
Enabling Full MMU doesn't give popups but it does nothing to stop the crashes, I tested all this and gave a bisect.
Updated by JMC4789 over 3 years ago
Did you try single core? I just use single core by default so maybe that is why I didn't run into the the other crash.
Updated by ZephyrSurfer over 3 years ago
I have. I tried pretty much everything conventional so it's very odd to me that it's working for you.
Are you quitting after getting in-game then selecting new game and waiting until you get in game a second time around?
Updated by JMC4789 over 3 years ago
I played through the entire intro multiple times, fighting all the people on teh ship and doing the tutorial and getting to the island after that.
Updated by ZephyrSurfer over 3 years ago
It's also a pretty good test to just let the enemy kill you and select main menu, if that doesn't crash it should before getting in game a second time(selecting new game again).
Updated by JMC4789 over 3 years ago
Note that, I did reproduce the crash until I turned on MMU. After I turned on MMU I was able to do everything fine.
Updated by ZephyrSurfer over 3 years ago
The intro and getting to the island worked for a long time, some cutscenes later on in the game crash inconsistently. These steps I have provided have a better consistent and quick to test crash.
Doing these steps right at game start is 100 percent reproducible crash for me and pretty quick to do as well.
Updated by ZephyrSurfer over 3 years ago
I ran 5.0-14669, with default settings as well as single core and it's still crashing for me when using those same steps
Updated by JMC4789 over 3 years ago
- Subject changed from Crashes in Summoner to Crash when starting multiple new games in Summoner
- Status changed from Fixed to Accepted
Yeah, I see the crash after killing an enemy and resetting.
There's multiple crashes going on. Well, at least one of the crashes were fixed by enabling full MMU.
Sorry for wasting your time.
Updated by Charlese2 25 days ago
The in-game crashing I get in Summoner: A Goddess Reborn is from the game re-initializing the audio interface while a sound effect is playing. The funny part is, the sound that is playing is the dialogue confirmation sound to go back to the main menu. I confirmed it by patching out the Audio Interface DMA Interrupt Handler callback (sound effects) and all my crashing went away (with the sound effects). I figured I could because all of the last interrupts in the OSPanics I was getting were "5" with the same SRR0 register value.