Announcement

Collapse
No announcement yet.

Vulkan Looks All But Confirmed For 2016 Launch

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

  • Vulkan Looks All But Confirmed For 2016 Launch

    Phoronix: Vulkan Looks All But Confirmed For 2016 Launch

    It looks all but confirmed that Vulkan will launch in early 2016 rather than making it out this calendar year as originally planned...

    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
    There's one thing I don't understand: What's the point of keeping the Vulcan API in secret before official release?

    Comment


    • #3
      It would've been nice to be ready 2-3 months before GDC, so graphics chips makers can tout "Vulkan support" for their new GPUs.

      Comment


      • #4
        Originally posted by etam View Post
        There's one thing I don't understand: What's the point of keeping the Vulcan API in secret before official release?
        Probably because it's still in flow. They don't want people to be disappointed when a feature that was in the 0.9 draft gets eliminated from the 1.0 version.

        Comment


        • #5
          Let's see. 13 days left for Khronos to keep their word.

          Regardless of when it's launched I hope it's a well coordinated launch to make a big splash.
          Ideal scenario would be intel, AMD and Nvidia have launch day drivers ready for both windows and linux. And valve releases the dota 2 Vulkan beta on the same day.

          Comment


          • #6
            This is all starting to feel very OpenGL 3.0-like (promise a new clean spec, take several years, release the old spec with additions and deprecations all over, then actually release a kinda new spec with 3.1 a while later). I can understand the desire to get the spec right the first time and just have it grow off from there, but Khronos has been doing this for a while, and so they should know that something will go wrong and they'll have to mark it for deprecation in one release, then deprecate it and make the new way the standard in the next release to fix it.

            Any direction you go though should fix a major problem, which is making something then forcing GPU manufacturers to hack around bad behavior in your program and in their drivers to get it to function nicely.

            Comment


            • #7
              Originally posted by Krysto View Post

              Probably because it's still in flow. They don't want people to be disappointed when a feature that was in the 0.9 draft gets eliminated from the 1.0 version.
              That's not the case. Khronos confirmed during Siggraph (August) that the spec has long been frozen and is being transformed into textual form

              Comment


              • #8
                The info was already out.
                he Anandtech article about AMD GPUOpen mentions they were told Vulkan would be released in early 2016.

                Comment


                • #9

                  Comment


                  • #10

                    They're talking about their benchmarks.

                    Everytime someone writes Vulkan with a c a small kitten dies.

                    Comment

                    Working...
                    X