Emulator Issues #13142
open
Graphical glitches outside of Dolphin on Mac OS 12.6.2 after use of Dolphin 5.0-17995 with Vulkan driver
0%
Description
What's the problem? Describe what went wrong.
After running a GameCube ROM (does not seem to depend on any specific ROM) on my Mac OS 12.6.2 Monterey system with Intel CPU & Intel HD 515 GPU and exiting Dolphin, there will be graphical glitches in hardware accelerated parts of other applications , e.g., in Chrome, specifically in videos. These glitches look like scattered black boxes, that flicker in and out of view. The boxes are several pixels in width and height and seem to be quadratic. They seem to be aligned on vertical and horizontal paths.
The system is still usable as normal, but to get rid of these glitches, I have to reboot the machine.
What steps will reproduce the problem?
Use Intel Mac with Intel HD 515 graphics card and launch any GameCube ROM with Vulkan driver and otherwise default settings.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Probably, as the version I am using is very recent.
Is the issue present in the latest stable version?
Yes, it is present in version 5.0-17995.
What are your PC specifications? (CPU, GPU, Operating System, more)
Macbook with Intel Core m5 CPU and Intel HD Graphics 515 GPU. 8 GB of RAM.
OS: Mac OS 12.6.2 Monterey
Files
Updated by MayImilae over 1 year ago
- Operating system OS X added
- Operating system deleted (
N/A)
Can you give us some screen recordings of these bugs please? You can use the built-in screenshot tool to record the screen, or something like OBS.
Please give us screenshots at the very least.
Updated by Sethur over 1 year ago
MayImilae wrote in #note-1:
Can you give us some screen recordings of these bugs please? You can use the built-in screenshot tool to record the screen, or something like OBS.
Please give us screenshots at the very least.
I will try to do that. It's a bit tricky since these artefacts are appearing and disappearing very quickly.
Updated by Sethur over 1 year ago
I was just able to take a screenshot of the graphical artefacts while watching a YouTube video. The boxes were perfectly vertically aligned here and were flickering in and out of existence while the video was playing in the background.
As I said, the only option that I found that can fix this is a complete reboot of the machine.
Updated by MayImilae over 1 year ago
Yikes, web compositor bugs. So this is likely a macOS Intel Graphics driver issue from whatever Intel driver macOS has for you Intel HD Graphics 515 GPU, and that is then interacting badly with something in Chrome. Because there are multiple layers of things interacting with eachother to cause this, it's going to be an absolute pain to reproduce even for someone with the same hardware! It could be Chrome's fault for all we know. And worse yet, I don't know of anyone with that hardware in the project - the 12in MacBook was not exactly a popular gaming machine. Personally, I don't have an Intel Graphics 515 mac to test against, I have older (HD4000) and newer (Iris Plus Graphics 655)... which are 3 years older and 3 years newer, ironically.
EDIT: I've been told that that generation of Intel Graphics has known hardware bugs. Even more yikes.
So let's just start with basic troubleshooting. Does this happen on our OpenGL or Metal Graphics Backends?
Updated by Sethur over 1 year ago
MayImilae wrote in #note-4:
So let's just start with basic troubleshooting. Does this happen on our OpenGL or Metal Graphics Backends?
I tested this with the Vulkan render backend, which on Mac OS probably means that it's using Metal via MoltenVK, but I am not an expert on the specifics of the implementation. I could try if this is reproducible with the OpenGL and Metal backends as well.
Updated by Sethur over 1 year ago
I should maybe stress again, that this happens AFTER the Dolphin process was terminated, so the GPU seems to be in a compromised state at this point. I might be wrong, but applications should not be able to permanently change the state of the GPU after the respective process has ended, or should they? If not, then the fact that this is even possible would point toward a driver bug on Apple's side. There is probably still a way to not trigger this bug, though.
Updated by Sethur over 1 year ago
Update: I tried to reproduce the issue using the Metal renderer. This did not trigger the graphics artifacts described above, so it seems this is a Vulkan-only issue.