Emulator

Game title

Metal Gear Solid: The Twin Snakes
Metal Gear Solid: The Twin Snakes (Disc 2) etc.

Game ID

GGSPA4

MD5 Hash?

4d44fc6da6d2fbc7a47e7fdda868139c

What's the problem? Describe what went wrong.

Emulation auto-pauses each time if focus is not in the Render Window after working perfectly for about 20 sessions.

The issue occurs either when the Render Window is first initiated after a start of the app, and therefor focus is not yet in the Render Window or because you click out of the Render Window. "Pause on focus loss" is turned off and "Ask to stop on focus loss" is on — yet, emulation pauses on focus loss each time.

What steps will reproduce the problem?

This bug manifest by the emulator non-immediately, but once it first exhibited it, it continues to do so despite restart of the app, deleting and reinstalling of the app, and restarting the computer or using a different disc of the same game. The first occurrence probably happened after about 15-20 initiation of emulation by selecting the disc and clicking "play". I do not know what triggered it; I wish there was a "Restore default configuration button"; I am confident it would resolve it. I probably made a wrong setting; however, the closest that relates to this is the "Pause on Focus Loss" option of the menu "Render Window" which is disabled in my case.

To compel its exhibition, the following steps are necessary once it first occurred:

1. Start a compatible disc.
2. Emulation automatically pauses, and the Dolphin host app window ("Host Window") will show the play icon and the "Play" label under it instead of the pause icon and the label "Pause" indicating that emulation is paused.
3. Click inside the Host Window, and click "Play", double click the disc or choose from the menu Emulation > Play — it will now start emulation from Pause. 3.a. If you clicked in the Host Window, and now want to bring the Render Window into the forefront by clicking into it or choose full screen of the Render Window with your mouse, ……emulation will pause again. (Post the first occurrence of the bug, the only way I found to still play was to not click into the Render Window after one of the methods to initiate emulation.) 3.b. If you initiated emulation inside the Host Window and start by Emulation > Play, the game will run just fine until the next focus change including clicking any of the menu options of the Render Window itself. For example, loading a state will pause emulation again, and Emulation > Play will need to be pressed again.

If the issue isn1t present in the latest stable version which is the first broken version?

I am not sure of the version number of "the latest development version", the info I found in the About menu includes "[b]ranch: [M]aster", "[r]evision: 8335ec70e253eb21509408ca6b5736ed57dfc", "[u]sing Qt 5.15.2.

Is the issue present in the latest stable version?
Yes, Dolphin v. 5.0-16380. This is the first time I am using Dolphin, and therefore I do not know if the issue was present before, my searches for "auto-pause" "auto pause" or "pause" did not result in finds that would have appeared to be the issue present here in the reported open issues.

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

I could not find the "fifologs", screenshots are not really necessary, as the bug is simply pausing emulation as described above, and it is independent from the games, happens across the board.

What are your PC specifications? (CPU, GPU, Operating System, more)

MacBook Air 8-core M1, 2020, macOS Monterey 12.4, memory 8 GB.

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

I .zipped the config and logs folders, and attached them below. Not sure which one it would be, and I am fairly sure restoring the default configurations would resolve the issue. Please add a restore default configurations button if possible (or make it more prominent for the simple folk like me).