Emulator Issues #10911
closed(DEV BUILD) GameCube BIOS OpenGL Issue
0%
Description
Game Name?
GameCube BIOS
Game ID?
N/A
MD5 Hash?
N/A
What's the problem? Describe what went wrong.
When running a GameCube game with the BIOS enabled, the top half of the window becomes glitchy.
What steps will reproduce the problem?
Set the video backend to OpenGL.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Currently, I am running Dolphin 5.0-6364 (dev_ver).
Is the issue present in the latest stable version?
Currently using a development build, as described above.
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 attachments.
What are your PC specifications? (CPU, GPU, Operating System, more)
MacBook Pro (13-inch, Early 2011)
Operating System: macOS X El Capitan
Processor: 2.3GHz Intel Core i5
Memory: 4 GB 1333 MHz DDR3
Graphics: Intel 3000 Graphics 384 MB
Files
Updated by aid.noodle almost 7 years ago
EDIT: After some testing, games are also affected, however, 3D graphics simply flicker, unlike the GCN BIOS.
Updated by JMC4789 almost 7 years ago
- Status changed from New to Questionable
It's likely an issue with your drivers, as this doesn't happen on my NVIDIA, AMD, or Intel (on Windows.)
Updated by mstreurman almost 7 years ago
Does the corruption go away ingame if you do not use a Gamecube bios?
Updated by ilusias over 6 years ago
I have the same problem here,and my OS is macOS X El Capitan,too.
It is not a Windows ver's problem.
I found that something wrong dev. build 5951.
After dev. build 5951,the graphic problem will occurred.
Updated by ilusias about 6 years ago
Tested.
This problem fixed in build 8905.
Thanks.
Updated by OatmealDome about 2 years ago
- Status changed from Questionable to Fixed
User reported issue to be fixed.