Emulator

Unfortunately Intel's Vulkan driver on Windows sucks and I don't think there's anything we can do about this. I'll see if Stenzek has a different opinion than me.

@JMC4789 I semi-agree with you. Although I had my fair share of problems with Intel graphics, I had my problems on my desktop with Nvidia as well. It's just Windows that sucks tbh, but that's another topic. If you guys don't care about this it's fine, I'll just stay at this version or update and use DX12 but my point still stands: What are the odds that Intel f*cked something up a full year ago that they couldn't have fixed or atleast encountered after 16 updates?

What are the odds that Intel f*cked something up a full year ago that they couldn't have fixed or atleast encountered after 16 updates?

Make that 17.

I'm almost certain that this is a shader issue because when jumping between drivers, it sometimes crashes while compiling them on the newer drivers. What would be a good way to disable the drawing of shaders to rule that out? I don't really code but I can follow directions if you guys want to work with me.

If you disable shaders you just won't be able to see anything. Shaders are the core of how Dolphin emulates the behavior of GX.

@Techjar Yeah, I understand that I just wanna see if it would still crash without shaders. Which I guess based on your comment it shouldn't.

This issue was resolved for me in the latest driver releases by Intel. Try build 8280 or 8336 and see if they work for you also.

@ShadowMyst Still not working for me. Could you test the attached fifo file?

Sorry, not experienced enough to work with those directly. What intel gpu do you have?

It's actually pretty simple. Just download the file and open it in Dolphin. If it's working you should see a loop of the first second of the Wii warning screen. If it doesn't, just a black screen follow by a "Failed to submit command buffer" (if you've "Use Panic Handlers" active).

OS: Windows 10 1809
GPU: Intel Iris Plus 640

Give me a moment. Not certain what will happen on my end since I'm running 10th Gen Ice Lake with Iris Plus G7.

Works fine for me. Keeps looping. The issue appears to be how your specific GPU functions with the Intel drivers; not the drivers in general.

Interesting. It could very well be that the newer GPUs get more testing and thus this issue slipped through. Do you have any unusual settings set in Dolphin? Also are you running Windows 10 2004?

All my settings are kept at default, with the exception of having set 2 games to specifically turn off Arbitrary MipMapping for a decent performance boost (Rogue Squadron II and III). I tested your off under Windows 10 2004 and macOS 10.5.5.

I remember when I filed a similar report earlier this year that Stenzek said "Intel's driver up until recently would crash when booting because despite advertising support for dual-source blend, clearly hadn't tested any pipelines which used them because they'd kill it with a null pointer access."

Which method of shader compilation are you using? Synchronous, Asynchronous (Ubershaders) or Synchronous (Ubershaders)? Before it was fixed by Intel for the Ice Lake Iris Plus gpu, it would only occur for me on Synchronous and Asynchronous (Ubershaders); never on Synchronous (Ubershaders). Have you tried all 3?

Yep, I already went through all settings and the only setting which affects this is switching from Vulkan to another backend (or staying on 26.20.100.6861).

Definitely seems specific to the 640. Stenzek would be the final say though.

Also happening to friend of mine on 655 and latest Win10.

It might be better to say it is specific to the Gen 9/9.5 GPUs. Unless we hear from someone with an even older system.

I have an update for you Anuskuss. I just did a clean re-install of Win 10 on my MacBook Pro 2020 and was able to reproduce the issue there. So it affects Gen 10 as well. No clue why it didn't happen before, but I honestly can't remember what version of the intel drivers were installed on my prior BootCamp configuration.

I have turned on the Vulkan validation layer (Graphics -> Advanced -> Debugging -> Enable API Validation Layers) but there is not a single line in the log. Maybe it's not setup properly?

Turns out I had to install the Vulkan SDK to use the validation layer. After setting everything up and logging Host GPU only, I see these repeating lines in the log:

14:07:784 VideoBackends\Vulkan\VulkanContext.cpp:674 E[Host GPU]: Vulkan debug report: (Validation) Validation Error: [ VUID-vkAcquireNextImageKHR-semaphore-01286 ] Object 0: handle = 0xa,540,ac0,000,000,009, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0xe9,e4b,2a9 | vkAcquireNextImageKHR: Semaphore must not be currently signaled or in a wait state. The Vulkan spec states: If semaphore is not VK_NULL_HANDLE it must be unsignaled (https://vulkan.lunarg.com/doc/view/1.2.162.1/windows/1.2-extensions/vkspec.html#VUID-vkAcquireNextImageKHR-semaphore-01286)
14:07:784 VideoBackends\Vulkan\VulkanContext.cpp:674 E[Host GPU]: Vulkan debug report: (Validation) Validation Error: [ VUID-vkQueuePresentKHR-pWaitSemaphores-03268 ] Object 0: handle = 0x23,24a,6f1,b18, type = VK_OBJECT_TYPE_QUEUE; Object 1: handle = 0x8,3d4,ee0,000,000,00b, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x25,1f8,f7a | vkQueuePresentKHR: Queue VkQueue 0x23,24a,6f1,b18[] is waiting on pWaitSemaphores[0] (VkSemaphore 0x8,3d4,ee0,000,000,00b[]) that has no way to be signaled. The Vulkan spec states: All elements of the pWaitSemaphores member of pPresentInfo must reference a semaphore signal operation that has been submitted for execution and any semaphore signal operations on which it depends (if any) must have also been submitted for execution (https://vulkan.lunarg.com/doc/view/1.2.162.1/windows/1.2-extensions/vkspec.html#VUID-vkQueuePresentKHR-pWaitSemaphores-03268)

By the way, Intel has released (atleast) 30 driver revisions since 26.20.100.6861 so it's getting more and more unlikely that it's a driver regression. My theory about this being a case where Intel is doing something more strictly than AMD/Nvidia to provoke this error honestly sounds pretty likely to me.

This is not specific to Windows. I'm getting it on Artix Linux for the past couple weeks. It seems to be completely random. Anywhere between a few seconds to several minutes after starting a game it'll freeze with this message spammed endlessly until I close the emulator. It's practically guaranteed to happen within 15 minutes.

Can you test this on the latest dev builds? A lot of changes have been made to Vulkan recently that may help this.

Nope, stil bad. Thankfully, my new system has a real GPU and I don't have to deal with shitty Intel GPUs ever again.
However, my new system does have an Tiger Lake iGPU, and it still doesn't work, even though I'm on Linux now. So I was right, it's very likely not a driver issue (well Rena already sort of confirmed it, but they could've just tested the attached FIFO file instead of giving some vague scenario).