Emulator Issues #12065
GC Zelda OoT windowed instability
The Legend of Zelda: Ocarina of Time, both from the Master Quest disc and the Zelda Collector's Edition.
Game ID? (right click the game in the game list, Properties, Info tab)
D43P01 and PZLP01.
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
b18019b6b399c9826bae843f06c43d08 and 1c9fa0c8adc9584e5169d4cfb51425f3.
What's the problem? Describe what went wrong.
Both version of OoT hang when leaving fullscreen. The video immediately hangs while the sound continues to play for about 2 or so seconds before hanging. Also, if running on a window to boot, the game freezes shortly after it's done loading.
What steps will reproduce the problem?
Boot Ocarina of Time from either game, enter fullscreen, leave fullscreen. Alternatively, just run the game windowed.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Is the issue present in the latest stable version?
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.)
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
See OoT.dff. Started recording when the loading screen's progress bar was near the end. Graphics are a completely garbled mess when playing back.
What are your PC specifications? (CPU, GPU, Operating System, more)
AMD Ryzen 3700X
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
I don't think it would have that big an effect in this particular situation and it would improve stability. Besides, there's already the issue with the JIT running out of cache causing stutters so it's not like OoT is gonna run without a hitch no matter what people do. At the very least the wiki needs to be edited to include a warning against using the DC hack. In any case this can be closed.