Last 15.60 4901 Intel drivers with Vulkan 1.0.62 API crashes

Phawx · 02-09-2018, 07:26 AM #1

Hello,

I'm using GPD Win 2, which contains M3-7Y30 and running latest 15.60 (4901) drivers. These drivers have 1.0.62 Vulkan API support, but when using Vulkan backend in Dolphin, games immediately crash.

Is there anything I can provide? Are there logs or dumps that I can submit? I tried searching on Google referencing driver and Vulkan but didn't find anything.

Please advise.

**KHg8m3r** · 02-09-2018, 07:54 AM #2

In some cases downloading the Vulkan SDK will fix this issue. Use the link in this thread to download it:
https://forums.dolphin-emu.org/Thread-questions-regarding-vulkan-backend?highlight=vulkan+sdk

JonnyH · 02-09-2018, 08:03 AM #3

Please report driver bugs to the people who work on the driver (in this case, Intel) - assuming that the loader update (in the vulkan sdk) didn't fix things.

Also, make sure you're installing the drivers from the intel website - the windows update ones are often old, and/or are missing modules (Microsoft want to push DX, so they sometimes "accidentally leave out" other modules... like opengl and vulkan Smile

Phawx · 02-09-2018, 08:34 AM #4

(02-09-2018, 07:54 AM)KHg8m3r Wrote: In some cases downloading the Vulkan SDK will fix this issue. Use the link in this thread to download it:
https://forums.dolphin-emu.org/Thread-questions-regarding-vulkan-backend?highlight=vulkan+sdk

I've downloaded the SDK and installed. Still crashes.

It looks like Intel is already aware that it crashes on Dolphin as can be seen here:

https://communities.intel.com/thread/116950

But the thread is closed. I suppose I could open a new one but it seems like it's already a ticket on their side.

JonnyH · 02-09-2018, 10:22 AM #5

It may not be the same issue - there's any number of things that could happen to cause a crash. It could be they've fixed one, but there's still another, or inadvertently introduced a new issue, or even you are hitting a different issue due to some reason.

Or they've just not fixed that one Smile

But Intel are likely the correct people to inform, if this requires a new thread on their forums I guess that's the correct action...