Announcement

Collapse
No announcement yet.

Vulkan 1.0.25 Moves To Single-Branch Model, Adds NVIDIA Extensions

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

  • Vulkan 1.0.25 Moves To Single-Branch Model, Adds NVIDIA Extensions

    Phoronix: Vulkan 1.0.25 Moves To Single-Branch Model, Adds NVIDIA Extensions

    The Vulkan 1.0.x release train has been slowing down a bit with not seeing releases every week now but sometimes it's now every other week...

    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
    Is not Vulkan supposed to be vendor neutral? Why do they add Nvidia specific extensions?

    Comment


    • #3
      Originally posted by wargames View Post
      Is not Vulkan supposed to be vendor neutral? Why do they add Nvidia specific extensions?
      Isn't the point of Vulkan to give more low level access to hardware? Don't see how you can do that without providing vendor specific extensions.

      Comment


      • #4
        I think we already had that discussion earlier. The key point is: Extension - its not part of the core Vulkan codebase. Its still not very elegant.

        Comment


        • #5
          They are not necessarily vendor specific, just originally proposed by that vendor, others are free to also implement them. Same as OpenGL.

          Comment


          • #6
            Extensions for Direct3D11 interop, pretty nice

            Comment


            • #7
              To a certain extent... If these extensions proliferate instead of being worked into the standard it will erode the cross-vendor, cross-platform standard. Also notice that two of the four vendor specific extensions are Win32 specific...
              Not a surprise to see such a fuck-everything-up-job from Nvidia.

              Comment


              • #8
                I hope I'm not the only one who fears that Vulkan will become the same vendor-specific extension hell that OpenGL was in the late 90's and early 2000's. Because that caused developers some major headaches and was a large part of the reason why Direct3D became as dominant as it did.

                Comment


                • #9
                  Originally posted by wargames View Post
                  Is not Vulkan supposed to be vendor neutral? Why do they add Nvidia specific extensions?
                  Yes, but just like openGL (again vendor-netural) it has vendor-specific extensions.
                  Usually the more liked ones become part of the standard as other vendors add support for them on their hardware too.

                  Comment


                  • #10
                    They did it again! NVIDIA is terrible!

                    The new standard is not yet established and NVIDIA is already trying to break out of it. They are deliberately creating the same mess of vendor-extensions that we have under OpenGL again. They have not learned anything.

                    Comment

                    Working...
                    X