<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">

    <title type="text">Blogs Khronos Blog</title>
    <subtitle type="text"></subtitle>
    <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/" />
    <link rel="self" type="application/atom+xml" href="https://www.khronos.org/feeds/blog_feed" />
    <rights>Copyright (c) 2026, The Khronos Group</rights>
    <generator uri="http://www.expressionengine.com/" version="7.5.20">ExpressionEngine</generator>
      <id>tag:webservices@khronosgroup.org,2017-03-01:/blog/25</id>
      <updated>2026-04-09T18:33:34Z</updated>

    <entry>
      <title>Khronos Adds Middleware Insights to the OpenXR Extension Matrix</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/khronos-adds-middleware-insights-to-the-openxr-extension-matrix" />
      <published>2026-04-07T13:00:00Z</published>
      <updated>2026-04-09T18:33:34Z</updated>
      <author>
            <name>jphilips</name>
            <email>jeff@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="OpenXR"
        scheme="https://www.khronos.org/blog/category/openxr"
        label="OpenXR" />
      <content type="html"><![CDATA[
The Khronos OpenXR working group has expanded its Extension Matrix to include self&#45;reported data from middleware providers. Developers now have a clearer view of what&apos;s available across the broader XR stack.
      ]]></content>
    </entry>    <entry>
      <title>From Specification to Practice: Unlocking glTF&#8217;s Full Potential</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/from-specification-to-practice-unlocking-gltfs-full-potential" />
      <published>2026-04-06T13:00:00Z</published>
      <updated>2026-04-03T17:21:19Z</updated>
      <author>
            <name>jphilips</name>
            <email>jeff@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="glTF"
        scheme="https://www.khronos.org/blog/category/gltf"
        label="glTF" />
      <content type="html"><![CDATA[
The Khronos 3D Formats Working Group, which manages both the glTF and KTX standards, has launched an Education, Insights, and Outreach (EIO) Subgroup dedicated to equipping creators and developers with the guidance, resources, and real&#45;world information they need to unlock glTF&apos;s full potential.
      ]]></content>
    </entry>    <entry>
      <title>Video Encoding and Decoding with Vulkan Compute Shaders in FFmpeg</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/video-encoding-and-decoding-with-vulkan-compute-shaders-in-ffmpeg" />
      <published>2026-03-16T17:04:00Z</published>
      <updated>2026-03-16T18:24:45Z</updated>
      <author>
            <name>jphilips</name>
            <email>jeff@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="Vulkan"
        scheme="https://www.khronos.org/blog/category/vulkan"
        label="Vulkan" />
      <content type="html"><![CDATA[
In this blog we explore how FFmpeg uses Vulkan Compute to seamlessly accelerate encoding and decoding of even professional&#45;grade video on consumer GPUs — unlocking GPU compute parallelism at scale, without specialized hardware. This approach complements Vulkan Video&apos;s fixed&#45;function codec support, extending acceleration to formats and workflows it doesn&apos;t cover.
      ]]></content>
    </entry>    <entry>
      <title>Khronos Upgrades glTF Sample Assets and Render Fidelity Comparison Websites</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/khronos-upgrades-gltf-sample-assets-and-render-fidelity-comparison-websites" />
      <published>2026-03-12T13:00:00Z</published>
      <updated>2026-03-12T14:37:35Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="glTF"
        scheme="https://www.khronos.org/blog/category/gltf"
        label="glTF" />
      <content type="html"><![CDATA[

      ]]></content>
    </entry>    <entry>
      <title>New Vulkan Game Engine Tutorial: Build Your Own Production&#45;Ready Rendering Engine</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/new-vulkan-game-engine-tutorial-build-your-own-production-ready-rendering-engine" />
      <published>2026-02-25T14:00:00Z</published>
      <updated>2026-02-24T15:38:39Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="Vulkan"
        scheme="https://www.khronos.org/blog/category/vulkan"
        label="Vulkan" />
      <content type="html"><![CDATA[
The Vulkan Working Group at Khronos has published Building a Simple Game Engine, a new in&#45;depth tutorial for developers ready to move beyond the basics and into professional&#45;grade engine development. The series builds on the Core Vulkan Tutorial, guiding you through architectural principles and design patterns purpose&#45;built for Vulkan&#45;based rendering engines — helping you design clean, modular systems that scale with your project.
      ]]></content>
    </entry>    <entry>
      <title>Khronos at 25: Shaping Visual Computing with Open Standards</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/the-khronos-group-celebrates-25-years-shaping-the-future-through-open-standards" />
      <published>2026-02-10T14:00:00Z</published>
      <updated>2026-02-09T22:54:59Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <content type="html"><![CDATA[
In 2025, Khronos reached an impressive milestone: 25 years of member&#45;driven open standards development. The graphics, compute, and media landscape looked wildly different in 2000, when Khronos was formed, than it does today.  Era&#45;defining technologies such as smartphones, cloud computing, and the metaverse hadn’t yet emerged into the marketplace. The founders of Khronos were on the forefront of these emerging technologies. They knew that without flexible, consensus&#45;driven interoperability standards, these nascent technologies would be severely limited by fragmentation and duplication of efforts–and that, conversely, open standards had the potential to foster a marketplace of interoperable technologies that would allow innovation to thrive.
      ]]></content>
    </entry>    <entry>
      <title>Simplifying Vulkan One Subsystem at a Time</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/simplifying-vulkan-one-subsystem-at-a-time" />
      <published>2026-02-05T14:00:00Z</published>
      <updated>2026-02-05T20:33:34Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="Vulkan"
        scheme="https://www.khronos.org/blog/category/vulkan"
        label="Vulkan" />
      <content type="html"><![CDATA[
When those of us in the Vulkan® working group want to modify the API—whether it’s a new hardware feature to expose, a new use case we want to address, or even just a gap in the spec we want to address—we have one invaluable tool that we make heavy use of: extensions! Extensions are a wonderful way for us to get improvements to the Vulkan API out to developers without waiting for a new core version. They let vendors expose novel functionality and enable us to gather community feedback on new features before we firm them up into a core specification. Amazing! So we get new functionality out to developers quickly—what’s not to love!? Well…
      ]]></content>
    </entry>    <entry>
      <title>Vulkan Introduces Roadmap 2026 and New Descriptor Heap Extension</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/vulkan-introduces-roadmap-2026-and-new-descriptor-heap-extension" />
      <published>2026-01-23T14:00:00Z</published>
      <updated>2026-01-23T15:41:04Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="Vulkan"
        scheme="https://www.khronos.org/blog/category/vulkan"
        label="Vulkan" />
      <content type="html"><![CDATA[
The Khronos Vulkan API is in continuous development, and today the Vulkan Working Group has released two important updates to the API and ecosystem: an entirely new Descriptor system and the Vulkan Roadmap 2026 Milestone. These new features and more will be discussed at the forthcoming Vulkanised 2026 conference, taking place in San Diego on February 9&#45;11.
      ]]></content>
    </entry>    <entry>
      <title>Khronos Explores the Future of AI, Graphics, Spatial Computing, and Open Standards at SIGGRAPH ASIA 2025</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/khronos-explores-the-future-of-ai-graphics-spatial-computing-and-open-standards-at-siggraph-asia-2025" />
      <published>2025-12-15T14:00:00Z</published>
      <updated>2025-12-15T20:16:12Z</updated>
      <author>
            <name>jphilips</name>
            <email>jeff@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="Khronos General"
        scheme="https://www.khronos.org/blog/category/khronos-general"
        label="Khronos General" />
      <content type="html"><![CDATA[
SIGGRAPH ASIA is a pivotal gathering place for the global graphics community. This is where the industry pushes the boundaries of the state of the art and sets the direction for collaborative efforts. The Khronos® Group is presenting a future&#45;focused slate of BOF presentations and activities at SIGGRAPH Asia 2025, taking place in Hong Kong, December 15 &#45;18.
      ]]></content>
    </entry>    <entry>
      <title>VK_EXT_present_timing: the Journey to State&#45;of&#45;the&#45;Art Frame Pacing in Vulkan</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/vk-ext-present-timing-the-journey-to-state-of-the-art-frame-pacing-in-vulkan" />
      <published>2025-12-04T14:00:00Z</published>
      <updated>2025-12-16T22:46:52Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="Vulkan"
        scheme="https://www.khronos.org/blog/category/vulkan"
        label="Vulkan" />
      <content type="html"><![CDATA[
Real&#45;time graphics evolved quickly through the 1990s and 2000s, but developers struggled with one persistent bottleneck: precise control over when frames appeared on screen. Early APIs like OpenGL relied on opaque buffer&#45;swapping behavior that made smooth frame pacing difficult, often causing choppy motion even at high frame rates. Modern APIs introduced swapchains to improve throughput, yet still prioritized raw FPS over accurate presentation timing. Vulkan followed this pattern, offering strong pipelining but little insight into when queued frames would actually be shown. Early extensions such as VK_GOOGLE_display_timing and VK_KHR_present_wait moved the needle but lacked the precision developers needed. After years of iteration, the new VK_EXT_present_timing extension finally brings explicit, time&#45;based presentation control to Vulkan, marking a significant step toward consistently smooth frame pacing in interactive applications.
      ]]></content>
    </entry>    <entry>
      <title>Boosting Ray Tracing Performance with Shader Execution Reordering: Introducing VK_EXT_ray_tracing_invocation_reorder</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/boosting-ray-tracing-performance-with-shader-execution-reordering-introducing-vk-ext-ray-tracing-invocation-reorder" />
      <published>2025-11-18T14:00:00Z</published>
      <updated>2025-11-18T02:16:08Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="Vulkan"
        scheme="https://www.khronos.org/blog/category/vulkan"
        label="Vulkan" />
      <content type="html"><![CDATA[
Today, we’re excited to share that Shader Execution Reordering in Vulkan has advanced from a vendor&#45;specific extension, VK_NV_ray_tracing_invocation_reorder, to a multi&#45;vendor Vulkan extension, VK_EXT_ray_tracing_invocation_reorder. Now, this powerful optimization technique can be used across vendors and APIs with similar SER support in Microsoft’s Shader Model 6.9.
      ]]></content>
    </entry>    <entry>
      <title>Khronos Releases SYCL 2020 Rev 11 Specification with Eight New Extensions</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/khronos-releases-sycl-2020-rev-11-specification-with-eight-new-extensions" />
      <published>2025-11-17T14:00:00Z</published>
      <updated>2025-11-17T15:29:11Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="SYCL"
        scheme="https://www.khronos.org/blog/category/sycl"
        label="SYCL" />
      <content type="html"><![CDATA[
The SYCL Working Group at Khronos has been hard at work advancing the ecosystem for this open, royalty&#45;free, cross&#45;platform abstraction layer, which enables code for heterogeneous and offload processors to be written using modern ISO C++. Through active public development, SYCL continues to grow as developers contribute and provide feedback, shaping the future of this portable programming model. Recently, the SYCL Working Group announced the release of Revision 11 of the SYCL 2020 Specification, introducing eight powerful new extensions alongside numerous specification clarifications that demonstrate the Working Group&apos;s continued commitment to advancing the specification for the benefit of both developers and implementers. In this blog, we&apos;ll share what&apos;s new in the latest revision, as well as where to learn more about SYCL at Supercomputing and how to get involved with the community.
      ]]></content>
    </entry>    <entry>
      <title>New OpenXR Validation Layer Helps Developers Build Robustly Portable XR Applications</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/new-openxr-validation-layer-helps-developers-build-robustly-portable-xr-applications" />
      <published>2025-11-13T14:00:00Z</published>
      <updated>2025-11-11T17:31:10Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="OpenXR"
        scheme="https://www.khronos.org/blog/category/openxr"
        label="OpenXR" />
      <content type="html"><![CDATA[
The Khronos® OpenXR™ working group is pleased to announce the release of the Best Practices Validation Layer, now available in the OpenXR&#45;SDK&#45;Source repository. This new tool addresses a critical need in XR development: catching suboptimal API usage patterns that can lead to inconsistent behavior across different OpenXR runtimes.
      ]]></content>
    </entry>    <entry>
      <title>Advancing Scientific Visualization: Highlights from the ANARI Virtual Hackathon 2025</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/advancing-scientific-visualization-highlights-from-the-anari-virtual-hackathon-2025" />
      <published>2025-11-11T14:00:00Z</published>
      <updated>2025-11-12T15:51:17Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <category term="API"
        scheme="https://www.khronos.org/blog/category/api"
        label="API" />
      <category term="ANARI"
        scheme="https://www.khronos.org/blog/category/anari"
        label="ANARI" />
      <content type="html"><![CDATA[
The Khronos® ANARI™ Working Group recently wrapped up the ANARI Virtual Hackathon 2025, where developers, researchers, and visualization experts from around the world came together to explore what’s next for 3D rendering using the ANARI API. This year’s hackathon arrived at a pivotal time: the ANARI 1.1 specification has officially been ratified by the Khronos Board of Directors, marking a major milestone in the evolution of the industry’s first cross&#45;platform 3D rendering engine API. ANARI 1.1 expands capabilities across geometry, spatial fields, and performance enhancements, and advances how developers and domain experts can leverage high&#45;performance, vendor&#45;neutral rendering.
      ]]></content>
    </entry>    <entry>
      <title>Godot OpenXR Integration Project Update: Major OpenXR Features Now Production&#45;Ready</title>
      <link rel="alternate" type="text/html" href="https://www.khronos.org/blog/godot-openxr-integration-project-update-major-openxr-features-now-production-ready" />
      <published>2025-11-10T14:00:00Z</published>
      <updated>2025-11-07T22:57:57Z</updated>
      <author>
            <name>Khronos Group</name>
            <email>webservices@khronosgroup.org</email>
            
      </author>

      <content type="html"><![CDATA[
Earlier this year, we shared how the Godot OpenXR Integration Project, developed in close collaboration with The Khronos® Group, was advancing OpenXR™ development through real&#45;world testing and implementation. Today, I&apos;m excited to provide an update on the significant progress we&apos;ve made, with several major OpenXR features now production&#45;ready and available to developers worldwide.
      ]]></content>
    </entry>

</feed>