Emulator Issues #10693
Donkey Kong Country Returns – Objects flicker when Store EFB Copies to Texture Only enabled
Donkey Kong Country Returns
Game ID? (right click the game in the game list, properties, info tab)
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
a63c4232eaa0f3c0b4715b7553f9f7ab (note that I compressed my game into a gcz file, so hash may be different from uncompressed iso)
What's the problem? Describe what went wrong.
When playing a level with Store EFB Copies to Texture Only, certain objects (most notably Donkey Kong's head) will flicker in and out of existence.
Unchecking Store EFB Copies to Texture Only fixes the problem (at the expense of making those objects appear pixelated, by that's to be expected). However, this option is off my default and is not automatically enabled by the game's ini file.
The ini for Donkey Kong Country Returns should automatically disable Store EFB Copies to Texture Only to prevent this problem.
What steps will reproduce the problem?
Start the game and enter any level.
I am running macOS, and thus by extension am using the openGL backend.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
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'm not not sure a fifo log will be useful, because they need EFB Copies to Texture Only to be enabled, which fixes the problem. That said, I have uploaded a log to Dropbox (it was too large to attach).
What are your PC specifications? (CPU, GPU, Operating System, more)
macOS 10.12.6 (Sierra)
Intel Core i5 6600K
Geforce GTX 1080 Ti
#4 Updated by JosJuice almost 3 years ago
Or, uh, I guess those instructions are hard to use on macOS if you don't have a build environment set up... It's also possible to manually do a binary search of the builds on the download list. It works like this:
Try the build that's right in the middle of 5.0 and the newest build. If that version works, try the build that's in the middle of that build and the newest build, otherwise try the build that's in the middle of 5.0 and that build. Continue that way, always testing the build that's in the middle of the newest known good build and the oldest known bad build. Using this method, you should be able to find the first broken build with roughly 12 tests.