4 ms·

You mean VR optimizations that are not crucial. And I don't think the specification says it requires Win10, does it? It's an implementation issue.

by DiThi 10y ago

dogma1138 10y ago
WDDM 2.0 and LDA as a requirement that's windows 10.
- wolfgke 10y ago
  WDDM 2.0: https://en.wikipedia.org/w/index.php?title=Windows_Display_Driver_Model&oldid=763825491 https://en.wikipedia.org/w/index.php?title=Windows_Display_D... LDA: https://msdn.microsoft.com/en-us/library/windows/hardware/dn894177(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/hardware/dn...
- DiThi 10y ago
  I mean Vulkan specification and its extensions. By definition it can't require Windows 10 exclusive features. It may happen that the only implementations in existence today do have this requirement.
  - dogma1138 10y ago
    There are Kronos extensions that require Win32 (and many of those do not have other platform equivalent from dealing with unified memory, to DX11/12 integration and other features), Vulkans mGPU support in it's current form specifically mandates Windows 10 because it's based on how WDDM and Windows 10 allow you to link devices, so do some of the VR specific functions. Vulkan was a Camel before they introduces the new extensions road map, you know have KHR which are "official" cross vendor LTS extensions which can be still platform dependant (e.g. you can have win32 KHR extensions), then there are KHX extensions which are effectively a rapid deployment branch primarily sucking in vendor extensions that can be a good idea, then there are the vendor specific extensions. Now not only that it's a camel, it seems to fall back into the same tarpit that OpenGL had in which you could not guarantee compatibility between hardware vendors and platforms.
    - DiThi 10y ago
      Some extensions are by design platform-specific. But the mGPU one is not. It requires some OS features which in Windows can only be given by WDDM 2.0. But the specification itself doesn't require WDDM 2.0.

You mean VR optimizations that are not crucial. And I don't think the specification says it requires Win10, does it? It's an implementation issue.

by DiThi 10y ago

You mean VR optimizations that are not crucial. And I don't think the specification says it requires Win10, does it? It's an implementation issue.

dogma1138 10y ago

WDDM 2.0 and LDA as a requirement that's windows 10.

wolfgke 10y ago
WDDM 2.0: https://en.wikipedia.org/w/index.php?title=Windows_Display_Driver_Model&oldid=763825491 https://en.wikipedia.org/w/index.php?title=Windows_Display_D... LDA: https://msdn.microsoft.com/en-us/library/windows/hardware/dn894177(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/hardware/dn...
DiThi 10y ago
I mean Vulkan specification and its extensions. By definition it can't require Windows 10 exclusive features. It may happen that the only implementations in existence today do have this requirement.
- dogma1138 10y ago
  There are Kronos extensions that require Win32 (and many of those do not have other platform equivalent from dealing with unified memory, to DX11/12 integration and other features), Vulkans mGPU support in it's current form specifically mandates Windows 10 because it's based on how WDDM and Windows 10 allow you to link devices, so do some of the VR specific functions. Vulkan was a Camel before they introduces the new extensions road map, you know have KHR which are "official" cross vendor LTS extensions which can be still platform dependant (e.g. you can have win32 KHR extensions), then there are KHX extensions which are effectively a rapid deployment branch primarily sucking in vendor extensions that can be a good idea, then there are the vendor specific extensions. Now not only that it's a camel, it seems to fall back into the same tarpit that OpenGL had in which you could not guarantee compatibility between hardware vendors and platforms.
  - DiThi 10y ago
    Some extensions are by design platform-specific. But the mGPU one is not. It requires some OS features which in Windows can only be given by WDDM 2.0. But the specification itself doesn't require WDDM 2.0.