> Vulkan can be used in classic win32 apps but not in "modern" UWP apps.
Why is this/how do they enforce that?
The Xbox is hardly a surprise, but then again you're only going to target that for games so it's less of a problem.
Why is this/how do they enforce that?
The Xbox is hardly a surprise, but then again you're only going to target that for games so it's less of a problem.
Technically Windows doesn't support Vulkan at all, but the openness of the win32 platform allowed Khronos to define a "backdoor" interface where the application ignores the Windows graphics stack and instead gets a Vulkan context by talking to the graphics driver directly. The UWP sandbox makes this impossible so you're stuck with the native Direct3D APIs.
The next Office for Windows 10 being store only is already an indication how things will go from now on.
https://github.com/KhronosGroup/Vulkan-Docs/issues/366
It doesn't exist now though for sure, so for all practical purposes UWP locks developers out of using Vulkan.