Emulator Issues #11469
Boom Blox and Boom Blox Bash Party both occasionally lock up after level select screen
Boom Blox and Boom Blox Bash Party
Game ID? (right click the game in the game list, properties, info tab)
RBKE69 and RYBE69
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
What's the problem? Describe what went wrong.
After the level select screen, both games will fade to black (which is normal) and occasionally fail to return with any video, putting the game in an essentially locked state. Audio from the level is still audible.
What steps will reproduce the problem?
Start either game. Select Solo from the main menu and pick a level.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
The behavior was encountered today for Boom Blox Bash Party in Dolphin 5.0-9156 for MacOS, and was encountered a couple of weeks ago for the original Boom Blox in another 5.0-91xx version for MacOS.
Is the issue present in the latest stable version?
Unknown, as the behavior is sporadic.
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
Not really applicable. It's just a black screen.
What are your PC specifications? (CPU, GPU, Operating System, more)
Late-2015 iMac, 4GHz Intel Core i7, AMD Radeon R9 M395X with 4GB RAM, MacOS Mojave.
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
This issue may be related to creating a save file.
The behavior was observed in both games upon a first run. In both instances, emulation was restarted, and the same process was started to enter the same level, which caused the problem to vanish. The only difference was that the second boot involved loading instead of creating a savegame. It's not 100% certain that this is the cause, but is likely an important clue about the cause.