Announcement

Collapse
No announcement yet.

Vulkan 1.3.264 Released With Microsoft Layered Driver Extension

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Vulkan 1.3.264 Released With Microsoft Layered Driver Extension

    Phoronix: Vulkan 1.3.264 Released With Microsoft Layered Driver Extension

    Earlier this year I wrote about Microsoft working on their first Vulkan extension and today it finally debuted within the Vulkan 1.3.264 spec update...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Correct me if I'm wrong, but currently you can't even pick which HW device to use in Qt GUI (version 5 or 6) Vulkan.

    I hate when toolkits write a custom API on top of a standard cross-platform API "to make it better", only to introduce shortcomings and have more stuff to learn for the user.

    Comment


    • #3
      Everyone sucks ass at Microsoft, even favoring their Direct3D crap.

      Comment


      • #4
        A lot of hot air for a simple function that returns a pre-defined struct.

        as it should be expected that native drivers will provide more functionality and higher performance, since layering inherently adds overhead
        This is microsofts argumentation that they try to push down everyone else's throat. What they don't tell you is that, of course, their direct3d crap is *always* considered native. It's in plain text in the document: It only differentiates between "none microsoft" and "direct 3d" - not a hint about the driver being "native".

        Every programmer that has had to work on the windows platform for some time knows that microsoft drivers notoriously provide less functionality than others.

        Comment


        • #5
          What I don't understand is why dx12 would even appear in the driver list?

          Or are we talking about a system where a native Vulkan driver exists and a VulkanOnDX12 implementation.

          In that case the native Vulkan driver should be preferred, certainly.

          Comment

          Working...
          X