4 ms·
It's worth noting that all devices that you can buy with Windows on ARM - those running an ARM version of Windows 10/11 on a Qualcomm chip - don't have Vulkan d
by DCKing 5y ago
It's worth noting that all devices that you can buy with Windows on ARM - those running an ARM version of Windows 10/11 on a Qualcomm chip - don't have Vulkan drivers available. Just DirectX - and an OpenGL compatibility pack that runs OpenGL on top of Direct3D 12.
Those same GPUs have perfectly functional Vulkan drivers on Android. I don't know what the problem is.
Having Vulkan on Windows is more like a courtesy from Nvidia, AMD and Intel that Microsoft hasn't really blocked [1]. But it can't truly be relied on on Windows - other GPU vendors don't need to build it [2]. Presumably with that excuse, Microsoft has not allowed apps on the Windows Store that targeted a 3D API other than Direct3D - that stuff just would not work on Qualcomm devices and presumably other devices as well.
[1]: If they were committed to being assholes about it they could force change as part of the WHQL problem, but it doesn't look like they are that committed. I'm not sure what they are committed to though.
[2]: I.e. what if we get Windows laptops with Mediatek chips, or Microsoft and/or Apple revive some Bootcamp mechanism for Windows on Apple Silicon?
- gjsman-1000 5y agoLike you said - Microsoft is just completely passive regarding Vulkan on Windows. It's up to the GPU vendors and driver makers, as long as DirectX isn't threatened. And on Xbox, DirectX is your only option, so if you want a nice clean Windows to/from Xbox port, writing for DirectX just makes sense. As for #2, Qualcomm (according to new reports) has an exclusivity deal for Windows on ARM that is expiring soon. But Microsoft would have to work with Apple and allow drivers to be written for the M1. Craig Federighi of Apple said they would be fine with Windows on M1 but Microsoft wasn't at the time. Though, to be honest, even if the exclusivity deal expires, I don't see Microsoft being excited about Windows on the M1. It only serves to embarrass their own products.
- DCKing 5y ago> But Microsoft would have to work with Apple and allow drivers to be written for the M1. Yeah to be fair I don't actually think that's going to happen. Someone needs to bear the burden of developing/maintaining a Windows graphics driver for Apple Silicon, which is a huge task. (Other drivers too, but that's not quite the same expense.) Apple will almost certainly not pay for that, and Microsoft would have to be extremely committed to having their OS be sideloaded on a competitor's devices to do it. If either Apple or Microsoft does do it though, you can be pretty sure you won't be seeing any Vulkan drivers soon.
- selectodude 5y ago> Having Vulkan on Windows is more like a courtesy from Nvidia, AMD and Intel that Microsoft hasn't really blocked OpenGL lived in that same space for, what, a decade?
- DCKing 5y agoPrecisely. Somehow on Windows I feel OpenGL has always been regarded as more of a developer/professional thing, and Vulkan lives in a similar space. Microsoft would shoot themselves in the foot explicitly disallowing Vulkan, but it seems they do want to have it limited somehow to more niche interests (developers, certain enthusiasts) and Direct3D as the 3D API everyone commits to.