Project

General

Profile

Actions

Emulator Issues #6938

closed

The Legend of Zelda: Ocarina of Time Master Quest Likes to Hang/Crash [cpuTiming]

Added by JMC4789 over 10 years ago. Updated about 8 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
PPC
% 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

This issue doesn't fall into the normal stuff. This is probably a pretty serious JIT problem, and I did a lot of discussion over IRC. Only essential information will be described here.

Game: The Legend of Zelda: Master Quest - D43E01

What went wrong?

The game likes to crash a lot. It happens on JITIL, It happens on JIT, If Interpreter ran over 1 fps, I woulda tested that too! Regardless, I've heard people say this happened, but in my short test periods, I never had a crash.

Until I actually played the game. I'm not 100% sure what's happening, and none of the crashes are absolutely consistent. They just "tend" to crash. It isn't like time of play is consistent either, it can happen 3 - 5 minutes in, it could take 30 minutes of deliberately trying to crash it.

There's also two types of fails. One is the Crash, and one is the hang. I've had about 35 hangs and 10 crashes, but I feel like crashes just come in streaks when they do happen

I tried using a debug build + minidumps to get useful information and couldn't. Apologies for being such a pain in the ass with no knowing what to do and messing up settings, it was new territory. But, with the minidumps useless, I can at least provide the most consistent method I've found to crashing it so far.

I provided a savefile at the bottom of this issue which has Deku Tree beaten. While the pathway to Deku Tree and Kokiri Forest is a good crash point, I believe the link between Hyrule Town and Hyrule Field is more consistent.

Methods
Method 1: Play in the Water in Kokiri Forest, then walk to the loading zone between Kokiri Forest and Deku Tree. You will know you passed the loading zone because enemies instantly spawn. Then go back toward the town until the enemies instantly despawn. If your game hasn't crashed, you can try two or three more times, maybe attacking enemy. If it hasn't crashed or hanged at that point, go play in the water some more. This method is extremely inconsistent, but has provided 90% of my crashes

Method 2: Forest Escape Kokiri Forest with Navi Dive and follow the waterfall. Requires moderate knowledge of Speedrunning tricks, but nothing demanding in terms of reaction time or skill level. When going down the water fall, sword bounce into superspeed in the water (every waterfall, just mash B) and sometimes the game will outright crash. Rarely hangs when doing this, but it can hang as well.

Method 3: Use the Link between Hyrule Castle and Hyrule Field. Using my Savefile, just walk out of the forest, and head to Hyrule Castle. Go in the castle, and leave, and it will crash or hang about 25% of the time. If it does not crash/hang, try entering exiting a few times. If it odesn't work, stay outside during the day, play in the water, and at night fight the monsters, hop on the ledge near the drawbridge, tease them, and do stuff. If it does not crash at night, EVERY single time it's crashed or hanged on my way back inside Hyrule Castle on morning. This is the most consistent method I know of triggering a crash. I've read other methods on the forums, but I was unable to reproduce.

-Dumpfiles-
https://dl.dropboxusercontent.com/u/484730/Dolphin.exe.4912.7z
https://dl.dropboxusercontent.com/u/484730/Dolphin.exe.1376.7z
https://dl.dropboxusercontent.com/u/484730/Dolphin.exe.5472.7z

These may be useless.

Savefile: https://dl.dropboxusercontent.com/u/484730/D43E_ZELDA.gci

Future Plans: Test other versions of Ocarina of Time (I also own Collector's Edition) and see wtf they do.


Related issues 1 (0 open1 closed)

Has duplicate Emulator - Emulator Issues #5761: The Legend of Zelda: Ocarina of Time - random freezing + hanging if happens while showing Ocarina notesDuplicate

Actions
Actions #1

Updated by JMC4789 over 10 years ago

lol, spend all that time writing the issue and get the game name wrong.

By the way, I'm am playing the vanilla OoT, not the remixed Master Quest

Actions #2

Updated by MayImilae over 10 years ago

Be sure the check the virtual console version as well. I'm very curious if it has any differences.

Actions #3

Updated by JMC4789 over 10 years ago

Legend of Zelda Collector's Edition has the same exact problems on Ocarina of Time.

Actions #4

Updated by JMC4789 over 10 years ago

Gotten other reports from people of it crashing like this.

Actions #5

Updated by parlane over 10 years ago

  • Status changed from New to New
Actions #6

Updated by JMC4789 over 10 years ago

  • Status changed from New to Accepted

I've gotten multiple confirmations that this happens. Dunno why it wasn't accepted.

Actions #7

Updated by phire almost 10 years ago

Ok, I looked into the collectors edition.

Unfortunately the debugger didn't work, but the few crashes I managed to examine pointed the game trying to execute random data as code.

Actions #8

Updated by sorairo.te.alastor almost 10 years ago

http://puu.sh/byejF/90613fbe19.png

Got that on the scene with the Deku tree explaining the misery hyrule's in where the 3 goddesses decent from ?space? to create the land... (had the game crash about 5 times at the same spot without showing a message, I guess constant usage of SaveStates and trying different things after beating gohma make the emulator go nuts at some point...)

Game is: GC Zelda OoT* / MQ Disc PAL - md5: b18019b6b399c9826bae843f06c43d08 (D43P01)
Using Windows 7 with OpenGL, HLE on 4.0-3210-dirty

PS: been pressing Yes for a while, seems like only the "unkown instruction 000********" seems to change, I hope this gets us in a direction where this comes from... (at least it's better then crashing or freezing, back to "playing" it on 0,05 fps or so...)

Actions #9

Updated by skidau almost 10 years ago

sorairo, please upload a zipped version of your memory card so that we can recreate the issue for debugging purposes.

Actions #10

Updated by sorairo.te.alastor almost 10 years ago

Unfortunately I've got past the scene investing about 1 hour of button mashing and saved it straight away before the next episode starts, therefore I also added 4 SaveStates which jump you to the scene in question, especially the 4th.

http://puu.sh/bzpof/db6afa382b.7z

The file is a 7z one because uncompressed it's 117MB big which would take ages for me to upload... (1024 kbit/s is my upload max in a perfect world, so meh)

I'm pretty sure tough that this kind of error will appear eventually even when playing on from the last memory card save...

I hope this helps :x

Actions #11

Updated by JMC4789 over 9 years ago

Issue 5761 has been merged into this issue.

Actions #12

Updated by william.ribeiro.ibiapina over 9 years ago

Master Quest also appears to suffer from this issue. Moreover, playing the ocarina with the notes/buttons appearing on screen may potentially bring forth a crash.

Actions #13

Updated by JMC4789 over 9 years ago

Can you please try it in this build? Majora's Mask in Collector's Edition appears to be confirmed fixed there -> https://dl.dolphin-emu.org/prs/pr-1316-dolphin-latest-x64.7z

Actions #14

Updated by sorairo.te.alastor over 9 years ago

I get the feeling that Dolphin got a lot better recently regarding Zelda OoT / MQ.
I managed to stream an entire 100% playtrough without errors or crashes split over multiple days (each with at least 2h playtime non-stop.)
Finished the playtrough today with 4.0-4654

Actions #15

Updated by JMC4789 over 9 years ago

I wonder if our the icache fix actually affected the stability?

Actions #16

Updated by sgrez14 about 9 years ago

noticed that it hangs alot less for me if I overclock cpu to 170% or so, also disabling dualcore helps a little bit

Actions #17

Updated by JMC4789 about 9 years ago

At 29% CPU Clock it ends up being perfectly stable. Probably a race condition of some sort.

Actions #18

Updated by JMC4789 about 8 years ago

  • Status changed from Accepted to Fixed

I don't know how this is still open. the Event Timing/JIT Slice Fixes should have killed this bug.

Actions

Also available in: Atom PDF