Announcement

Collapse
No announcement yet.

Vulkan 1.1 Released As The First Major Update To This Graphics/Compute API

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

  • Vulkan 1.1 Released As The First Major Update To This Graphics/Compute API

    Phoronix: Vulkan 1.1 Released As The First Major Update To This Graphics/Compute API

    The Khronos Group has today announced Vulkan 1.1 as the first major update to this high-performance graphics/compute API since the initial Vulkan 1.0 release two years ago. And it's thankfully a hard launch with multiple vendors putting out Vulkan 1.1 conformant drivers today.

    http://www.phoronix.com/vr.php?view=26073

  • #2
    That is exciting! And I really need to continue the work on mesamatrix to display the improvements on Vulkan as well

    Comment


    • #3
      This is probably a dumb question, but what with Vulkan 1.1 supporting HLSL in some form - wouldn't this make the work for the guy writing DXVK easier?

      Comment


      • #4
        Great release, good stuff.
        It's very good they made Multiview to be a general purpose extension.
        Multiview could be great for reducing draw calls for a lot of stuff that uses cube maps.
        A more dedicated stereoscopic/VR extension might face neglect.

        Comment


        • #5
          Originally posted by Creak View Post
          That is exciting! And I really need to continue the work on mesamatrix to display the improvements on Vulkan as well
          Could you add ARB_compatibility in Other extensions?
          There is currently no ARB_compatibility entry visible anywhere in https://mesamatrix.net/.

          Comment


          • #6
            Originally posted by Karbowiak View Post
            This is probably a dumb question, but what with Vulkan 1.1 supporting HLSL in some form - wouldn't this make the work for the guy writing DXVK easier?
            Maybe yes maybe no. If DXVK wants to keep Vulkan 1.0 support might mean needing two shader compliers to get best performance.

            https://github.com/Microsoft/DirectXShaderCompiler/

            Above is interesting right. HLSL to SPIR-V is being included in Microsoft compiler its DXIL ot SPIR-V and back that is interesting problem as well.
            https://github.com/gongminmin/Dilithium
            Above is interesting.

            https://github.com/Microsoft/DirectX.../docs/DXIL.rst

            Targeting DX11 means you have to support dxbc2dxil.dll that beast allows DX11 program to use shaders for older versions of DX back to dx9. So there is room for a joint project working on shaders.

            Targeting DX12 is where you get to drop legacy.

            Also these extra SPIR-V features for simpler DX shader conversion will this come to opengl SPIR-V as well.

            Its been interesting that DXIL is open specification and the old dxbc is closed specification. Yes dxbc support is quite a big pain in tail.

            Comment


            • #7
              More than a year and a version later , my question here https://github.com/KhronosGroup/Vulkan-Docs/issues/294 , about a topic very important to the future of Vulcan and driver development still hasn't been answered
              Last edited by GunpowaderGuy; 03-07-2018, 12:20 PM.

              Comment


              • #8
                Originally posted by plonoma View Post

                Could you add ARB_compatibility in Other extensions?
                There is currently no ARB_compatibility entry visible anywhere in https://mesamatrix.net/.
                The problem is that ARB_compatibility is not listed in features.txt. it is mentionned in the header of the file, but it's not part of one of the OpenGL versions.

                Edit: if the devs agree to add it in Other extensions, then it'll be automatically listed here

                Comment


                • #9
                  Originally posted by GunpowaderGuy View Post
                  More than a year and a version later , my question here https://github.com/KhronosGroup/Vulkan-Docs/issues/294 , about a topic very important to the future of Vulcan and driver development still hasn't been answered
                  Idk if I can take you seriously when you spell Vulkan wrong.

                  Comment


                  • #10
                    A bit too soon. Rumor has it the world ends, once the version number exceeds the number of applications using Vulkan.

                    Comment

                    Working...
                    X