#Dolphin on mac driver drivers#
#Dolphin on mac driver driver#

To explain myself better, the versions that have Vulkan are versions that are 'developer' versions, meaning that they have not been tested thoroughly and there may be problems, bugs, etc.

#Dolphin on mac driver driver#

Upon review of the steps followed and what has been used, I can tell that the problem is not really the driver or graphics adapter but the version that is being used. When using Vulkan with the latest (Developer) version, the emulator crashes. I finished with the testings and I have been able to replicate the problem. If you need any further details regarding my own device I am happy to provide them per the Intel System Support Utility at a later time. I've also noticed that depending on your Ubershader graphics configuration in these developmental builds, that Dolphin may not always crash but can still be prone to very poor performance. The previous stable release (5.0) without Ubershaders will not experience this crash. Recent developmental builds of Dolphin Emulator make use of a feature called 'Ubershaders', and it's such builds that experience these crashes. I noticed in xperia64's DxDiag.txt report that igc64.pdb was also identified in a problem signature, which appears to point to the same shader compilation issue. This crash continues to occur in Version 24.20.100.6229 / Build Date August 7, 2018.This crash has been occurring since Version 24.20.100.6194 / Build Date July 10, 2018.Build Date February 8, 2018, but this version does experience poor performance in scenarios that make use of shader compilation With a debugging build of Dolphin running with a Visual Studio debugger, this crash was isolated:.The crashing issue was reproduced using the Direct3D11 backend as opposed to Vulkan.Here are the main details from their issue tracker I reported this against Dolphin Emulator's own issue tracker around the same time, as xperia64 mentioned the developers believe this to be a driver issue. Hi, I would like to add that I have been experiencing a very similar issue with the same processor (an Intel Core m3-7ењ“0 with Intel 615 graphics) in a device known as a GPD Win 2. Ie: Cables&brand, cable type, dock, dongles/adapters, etcДЄttached

#Dolphin on mac driver drivers#

I can also test drivers and configuration settings on an Intel Core i5-7200U w/620 graphics and an Intel Core i7-7700k w/630 graphics if that would help as well. I can provide more logs and system information if required. When Dolphin supported Direct3D 12, it ran much faster than under OpenGL or Direct3D 11 as expected, but since that is no longer an option in current builds, we need Vulkan to work to provide the same performance. In addition, when I booted Ubuntu 18.04 on this same device, Dolphin was able to run correctly using Vulkan as the renderer, indicating that hardware is compatible.

I have confirmed that the Vulkan runtime is installed and functional on my system as other Vulkan programs run as intended. I am on Wind64-bit with graphics driver version 24.20.100.6194. Developers of Dolphin seem to have indicated this is likely a driver problem. Under Vulkan, Dolphin appears to completely crash.

Under OpenGL and Direct3D 11, the Starfield demo seems to render correctly. In terms of getting a sample program to load in Dolphin, I have found that this freely available, legal, GPL-licensed Starfield homebrew demonstrates the issue: Starfield - WiiBrew I figured this may be worth trying to bring up again, as recently Dolphin started working with Vulkan on mobile Adreno graphics, which in the past have been more problematic than Intel graphics. The memory leak issue described in this thread doesn't seem to happen any more: but the program outright crashes when loading any game or homebrew. I recently bought a device with an Intel Core m3-7ењ“0 with Intel 615 graphics, and it would seem that the iGPU is incompatible with the Dolphin emulator when using Vulkan as the renderer under Windows.