Announcement

Collapse
No announcement yet.

Vulkan 1.0.42 Released With A Slew Of New Extensions: Multi-Device, VR, Semaphores

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

  • Vulkan 1.0.42 Released With A Slew Of New Extensions: Multi-Device, VR, Semaphores

    Phoronix: Vulkan 1.0.42 Released With A Slew Of New Extensions: Multi-Device, VR, Semaphores

    The "GDC Vulkan update" has arrived with a number of new extensions!..

    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
    So with these changes not being big enough for a new minor version when do they call 1.1? Like what's the point in having a 3 point version system if you just push any and all changes into the 3 point and ignore the first two? They only needed a 2 point system if this was their plan, or a date based system with major releases being along the lines of 'Vulkan 2017" and minor versions being the month. But this is getting ridiculus.

    Comment


    • #3
      Let's see how this Vulkan thing turns out in a year or two. It started as a "lightweight" alternative to OpenGL and it's turning into a Bloated Piece of S***(TM) with propietary extensions everywhere.

      Comment


      • #4
        Originally posted by wargames View Post
        Let's see how this Vulkan thing turns out in a year or two. It started as a "lightweight" alternative to OpenGL and it's turning into a Bloated Piece of S***(TM) with propietary extensions everywhere.
        The extensions aren't "proprietary"... They are clearly public and part of the respective release. They are prefixed with the vendor's name solely because that vendor came up with the extension and it's always that way until it's adopted by Khronos officially, etc. Nothing is stopping AMDGPUPRO/RADV from supporting VK_NV_* extensions or vice-versa, and it already happens with just yesterday the VK_NV_dedicated_allocation landing for RADV.
        Michael Larabel
        https://www.michaellarabel.com/

        Comment


        • #5
          What means MVK? Metal Vulkan? Or is that a vendor?

          Comment


          • #6
            Well they are experimental. Maybe after a while when they get stabilized they rename them to KHR preffix and then release 1.1 version with them.

            Comment


            • #7
              Originally posted by theghost View Post
              What means MVK? Metal Vulkan? Or is that a vendor?
              MKV = MoltenVK https://moltengl.com/moltenvk/

              I guess...

              Comment


              • #8
                Why are there operating system specific extentions? Wouldn't it be better for extensions to be OS agnostic to make porting easier etc.?

                Comment


                • #9
                  Originally posted by gnarlin View Post
                  Why are there operating system specific extentions? Wouldn't it be better for extensions to be OS agnostic to make porting easier etc.?
                  For interop outside of Vulkan.... All other Linux apps are designed to work with POSIX FDs, Windows programs use Win32 handles.
                  Michael Larabel
                  https://www.michaellarabel.com/

                  Comment


                  • #10
                    Michael resterization, use-casesd
                    Last edited by tildearrow; 27 February 2017, 10:03 AM. Reason: add another typo

                    Comment

                    Working...
                    X