dtgreene: I get a warning that Vulkan support on Haswell is incomplete, so I didn't bother trying it
OK, well, I'm not really familiar with Intel that much any more since I no longer work for a company that bought me an Intel machine. According to the
OpenGL vs. Mesa matrix Intel has been ahead of AMD in the feature support list for at least a year or two, although lately it's reversed again. In particular, Vulkan used to be all greens for everyone, until they added 1.1 and unofficial stuff. In other words, I didn't expect that. On the other hand, "supported" is not the same as "supported well," although I would at the very least expect bug-free support. In any case, I have, in spite of my bad experiences with AMD support, insisted on AMD/Radeon for over a decade now. Makes it really hard to find decent laptops. I also tend to forget that Intel drivers for Mesa aren't the same as AMD's drivers for Mesa, even though they share a lot of code.
Also, wine never updates its warnings of that nature. It may be wrong, depending on which version of Mesa you're using. I had to add registry entries to bypass their outdated "mesa sucks" issues in the past. That's for the cases that didn't require outright code changes.
I do have an Intel device that sort of works that I got while waiting for a replacement for my laptop, but I can't use 32-bit wine on it right now due to distro stupidity. I may end up wiping it and trying a different distro. So much for a binary distro saving me time and aggravation. Not that I was going to put more effort into that machine, since its keyboard (and sometimes even its microSD card reader, which houses /usr) has become flaky and I still haven't added support for the cameras or touchpad, although neither are particularly necessary. Having my real laptop to work on has made me lose interest.