Emulator Issues #9274
open
Mario Golf (PAL only) suffers black blinking in the menus and matches with OpenGL mode and non-real XFB
0%
Description
Mario Golf Toadstool Tour PAL
[GFTP01]
MD5: a7506d6a7e7cfbda7ee81c0482c4834b
What's the problem? Describe what went wrong.
I see black blinking in this game using OpenGL. Direct3D remains unaffected (It doesn't need to activate XFB).
What steps will reproduce the problem?
Play Mario Golf on OpenGL mode. Don't set XFB to real. Go to the menus and beyond.
Turbo makes the blinking more evident.
Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?
4.0-8717
I also tested it with a few weeks older build.
What are your PC specifications? (CPU, GPU, Operating System, more)
i5 4210M (2.6GHz) CPU, Geforce 820M GPU, 4GB RAM, Windows 10 x64
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
I could show you the screenshot of the blink, but I think no one wants to see a full black frame :P
Updated by JMC4789 over 8 years ago
If the accuracy option (RealXFB) works, then there's a chance that it's just needed for something the game is doing. A few PAL games do some serious shenanigans to get PAL50/60 output. Why it works in D3D? Possibly a bug, or luck.
Updated by intruso over 8 years ago
I noticed there are more games with this issue. I think all the games on OpenGL mode suffer this blinking.
I also found out that choosing my Intel GPU (HD 4600) instead of my NVidia GPU solves this issue.
I'm going to update this report to show this problem isn't limited to one game.
I opened a topic in the forum:
https://forums.dolphin-emu.org/Thread-black-blinking-with-opengl
Updated by JMC4789 over 6 years ago
- Subject changed from Mario Golf suffer black blinking in the menus and matches with OpenGL mode and non-real XFB to Mario Golf (PAL only) suffers black blinking in the menus and matches with OpenGL mode and non-real XFB
Updated by ZephyrSurfer about 3 years ago
Looks like the issue reporter said this was a driver issue with their card, OpenGL on Nvidia(361.43), on the linked thread above, so it works for them now with a later driver.
I doubt this is worth looking into further then.