# Blogs Khronos Blog The Khronos Blog This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## OpenVX 1.3.2 Released: More Precise Errors, Better Consistency, and Groundwork for 2.0 DevFeed: [OpenVX 1.3.2 Released: More Precise Errors, Better Consistency, and Groundwork for 2.0]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-08-31T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [API](), [systems]() Tags: [api](), [blog](), [consistency](), [debugging](), [developers](), [error-handling](), [errors](), [openvx](), [release]() ### AI overview Khronos released OpenVX 1.3.2, adding more precise error codes, clearer image-handling rules, API enhancements, and terminology changes intended to improve conformance, portability, implementation, and debugging. The release is described as groundwork for OpenVX 2.0. ### Source excerpt Khronos released OpenVX 1.3.2, an update to the open, royalty-free standard that uses a high-level graph-based framework to deliver portable, efficient vision processing. This focused update strengthens error handling, improves conformance, and makes OpenVX easier for vendors to implement and for developers to debug -- laying the groundwork for the next major release, OpenVX 2.0. ## Khronos Sessions and Standards Updates at SIGGRAPH 2026 DevFeed: [Khronos Sessions and Standards Updates at SIGGRAPH 2026]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-08-21T13:00:00Z Content type: news Language: en Sources: [Blogs Khronos Blog]() Topics: [Graphics](), [OpenXR](), [webgpu](), [GPU]() Tags: [2026](), [3d](), [blog](), [gpu](), [graphics](), [openxr](), [webgpu]() ### AI overview Khronos presented more than 20 SIGGRAPH 2026 sessions on graphics, XR, 3D assets, rendering, real-time shading, and related open standards. Its Developer Day included updates from Vulkan, glTF, WebGL/WebGPU, OpenXR, ANARI, Slang, and the Machine Learning Council. ### Source excerpt SIGGRAPH 2026 in Los Angeles delivered a clear snapshot of the future of graphics and spatial computing--and Khronos was at the center of it. The organization presented more than 20 sessions spanning hands-on courses and in-depth Birds of a Feather (BOF) discussions on neural graphics, XR, 3D assets, rendering, and real-time shading. ## OpenXR Introduces Tiered Adopter Fees to Expand Its Ecosystem of Conformant Implementations DevFeed: [OpenXR Introduces Tiered Adopter Fees to Expand Its Ecosystem of Conformant Implementations]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-07-22T15:47:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [OpenXR](), [implementation](), [SDKs]() Tags: [blog](), [company](), [ecosystem](), [enterprise](), [fees](), [open](), [open-source](), [openxr](), [organization](), [payment](), [platform](), [platforms](), [products](), [property](), [technical]() ### AI overview Khronos is introducing OpenXR Adopter Program subscription and renewal fees based on company size. The change is intended to make official conformance more accessible to smaller organizations while preserving the existing technical requirements. ### Source excerpt New company-size-based fees make the formal OpenXR conformance process accessible to smaller implementers while preserving technical rigor. ## 2026 Real-Time Shading Ecosystem Survey Results DevFeed: [2026 Real-Time Shading Ecosystem Survey Results]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-07-21T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [releases](), [shaders](), [real-time](), [Programming](), [glsl](), [GPU]() Tags: [2026](), [blog](), [debugging](), [developers](), [glsl](), [graphics](), [porting](), [real-time](), [report](), [survey]() ### AI overview Khronos reports results from a 2026 survey of more than 400 shader developers, graphics programmers, rendering engineers, and tools creators. Shader debugging and profiling were the leading reported pain point, while cross-platform shader porting also affected a majority of respondents. ### Source excerpt Khronos releases the 2026 Real-Time Shading Ecosystem Survey Report, a summary of insights from over 400 shader developers, graphics programmers, rendering engineers, and tools creators. Conducted between June 16 and July 10, 2026, the survey captures a clear picture of how the real-time shading community works today -- and where standardization efforts can deliver the greatest impact. ## Khronos Sponsors Open-Source glTF Importer/Exporter for Autodesk 3ds Max DevFeed: [Khronos Sponsors Open-Source glTF Importer/Exporter for Autodesk 3ds Max]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-07-14T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [Open Source](), [3D](), [Tool](), [Documentation]() Tags: [3d](), [animation](), [apache](), [api](), [blog-glt](), [cameras](), [compression](), [documentation](), [gltf](), [lighting](), [mesh](), [open-source](), [plugin-development](), [plugins](), [render](), [standards]() ### AI overview The Khronos Group sponsored and released open-source glTF 2.0 importer and exporter plugins for Autodesk 3ds Max under the Apache 2.0 license. The plugins support round-trip glTF workflows, including scene content, materials, textures, compression, animation, lighting, and instancing. ### Source excerpt The Khronos Group has sponsored the glTF 2.0 Importer/Exporter for Autodesk 3ds Max open-source project under the Apache 2.0 license, and today has released the resulting glTF importer and exporter plugins, built to professional standards in collaboration with the community, and free for all to use. ## Vulkan Ray Tracing: Deprecating Host-Side Acceleration Structure Builds DevFeed: [Vulkan Ray Tracing: Deprecating Host-Side Acceleration Structure Builds]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-07-08T13:00:00Z Content type: article Language: en Sources: [Blogs Khronos Blog]() Topics: [Ray Tracing](), [GPU](), [Hardware]() Tags: [api](), [architecture](), [blog](), [complexity](), [deprecated](), [gpu](), [hardware](), [migration](), [ray-tracing](), [vulkan]() ### AI overview Vulkan is deprecating host-side ray tracing acceleration structure build commands in favor of a device-address-based path. Existing applications remain functional, while developers using host-side commands should plan migration to device-side equivalents. ### Source excerpt Vulkan is deprecating host-side ray tracing acceleration structure build commands in favor of a single, device-address-based path. This aligns Vulkan Ray Tracing with the direction of DirectX Raytracing, modern engine architecture, and hardware trends. In the six years since Vulkan Ray Tracing launched, the host-side path has seen limited adoption. Developers generally found it more cumbersome than helpful, while implementers had to maintain parallel host/GPU command models that increased complexity and created friction for future ray tracing API evolution. ## Khronos Launches Initiative to Extend glTF for Volumetric Media DevFeed: [Khronos Launches Initiative to Extend glTF for Volumetric Media]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-06-15T13:00:00Z Content type: news Language: en Sources: [Blogs Khronos Blog]() Topics: [3D](), [interoperability]() Tags: [3d](), [api](), [blog-gltf-volumetri](), [capture](), [extend](), [gltf](), [media](), [playback](), [standard](), [standards](), [streaming]() ### AI overview Khronos has established a Volumetric Media Subgroup within its 3D Formats working group to extend glTF for interoperability across volumetric capture, data formats, and content playback. The initiative invites organizations to help define the new capabilities. ### Source excerpt Any interested organizations are invited to join Khronos to help define new glTF capabilities to enable interoperable volumetric capture, streaming and playback ## Introducing glTF 2.1 with Complex Scenes DevFeed: [Introducing glTF 2.1 with Complex Scenes]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-06-11T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [3D](), [interoperability](), [Tooling](), [Streaming](), [Simulation]() Tags: [3d](), [announce](), [api](), [blog-glt](), [gltf](), [interoperability](), [release](), [streaming](), [tooling]() ### AI overview The Khronos 3D Formats Working Group announces plans for glTF 2.1, a focused and backward-compatible revision designed to support large, composed scenes. Proposed capabilities include multi-file scene graphs, spatial primitives, stable object IDs, progressive 3D streaming support, larger GLB files, and a formally deprecated multiple-scenes pattern. ### Source excerpt Since the release of glTF™ 2.0 in 2017, the format has matured into a rich ecosystem spanning mesh compression, texture optimization, 3D Gaussian splats, and more. Today, the Khronos® 3D Formats Working Group is excited to announce plans for glTF 2.1: a focused, backward-compatible revision of the core specification, built around a single motivation -- making glTF work as well for large, composed scenes as it already does for single assets. Every feature in this release addresses a real gap that today forces teams toward proprietary conventions, custom tooling, or workarounds that break interoperability. ## Vulkan SC SDK Released: An Integrated Toolchain for Vulkan Safety-Critical Development DevFeed: [Vulkan SC SDK Released: An Integrated Toolchain for Vulkan Safety-Critical Development]() Original publisher: [Read original article]() Author: Khronos Group (webservices@khronosgroup.org) Published: 2026-05-06T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [SDK](), [toolchain](), [Development](), [Linux](), [Windows](), [CMake]() Tags: [api](), [blog-vulkans](), [building](), [cmake](), [components](), [configuration](), [developer-experience](), [developers](), [development](), [download](), [ecosystem](), [getting-started](), [install](), [installation](), [integration](), [linux](), [sdk](), [toolchain](), [tools](), [vulkan](), [vulkan-sc](), [windows]() ### AI overview The Vulkan SC SDK is a unified installer for tools supporting safety-critical application development. It provides Linux and Windows installers, optional environment setup, CMake integration, pipeline cache compiler discovery, and components including the Vulkan SC loader, emulation and validation layers, device simulation, utilities, and samples. Version 1.0.21 is available on GitHub. ### Source excerpt Developers building safety-critical applications can now get started with Vulkan® SC faster than ever. The new Vulkan SC SDK is a simpler way to install and use a comprehensive set of tools and utilities to leverage the Vulkan SC ecosystem. With installers for Linux and Windows, the SDK makes it easy for developers to get up and running quickly, whether they are just getting started with Vulkan SC or building on existing deployments. ## OpenCL 3.1 is Here DevFeed: [OpenCL 3.1 is Here]() Original publisher: [Read original article]() Author: Khronos Group (webservices@khronosgroup.org) Published: 2026-05-04T07:01:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [cross-platform](), [Compiler](), [Open Source](), [toolchain]() Tags: [2026](), [api](), [blog-openc](), [compilation](), [compiler](), [compilers](), [cross-platform](), [directx](), [embedded](), [enumerate](), [opencl](), [optional](), [source](), [spir](), [vulkan]() ### AI overview The Khronos OpenCL Working Group has released OpenCL 3.1, moving field-proven capabilities into the core specification. The release mandates SPIR-V kernel ingestion for conformant implementations and expands cross-platform availability through a growing implementation, compiler, runtime, and framework ecosystem. ### Source excerpt On the eve of IWOCL 2026, the Khronos® OpenCL Working Group has released OpenCL™ 3.1, bringing widely deployed, field-proven capabilities into the core specification to expand functionality, including SPIR-V ingestion, that developers will be able to rely on across conformant implementations. The new specification arrives into a growing OpenCL ecosystem, with implementations from multiple silicon vendors, particularly in mobile and embedded markets, and higher-level frameworks including SYCL™ and chipStar increasingly targeting OpenCL as an acceleration backend. The open-source compiler and runtime ecosystem around OpenCL also continues to mature with layered implementations of OpenCL over Vulkan and DirectX 12 -- widening OpenCL's cross-platform availability, including on platforms without native drivers. ## OpenCL Cooperative Matrix Extensions Are Here DevFeed: [OpenCL Cooperative Matrix Extensions Are Here]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-04-29T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [AI Inference](), [GPU](), [C](), [LLVM](), [GitHub]() Tags: [api](), [arm](), [blog-opencl-spirv-machinelearning-llv](), [c](), [gpu](), [intel](), [llvm](), [opencl](), [qualcomm](), [spir](), [vulkan]() ### AI overview The OpenCL Working Group has published a working draft of the cl_khr_cooperative_matrix extension, developed with Arm, Intel, and Qualcomm. The extension brings cooperative matrix operations for ML inference to OpenCL, while a companion OpenCL C extension is also being developed. Community feedback is requested before the standards are finalized. ### Source excerpt The OpenCL Working Group has published a draft extension (cl_khr_cooperative_matrix) that brings cooperative matrix operations--a key technology for accelerating ML inference--to OpenCL, developed in collaboration with Arm, Intel, and Qualcomm. A companion extension to expose these capabilities directly in the OpenCL C language is also in progress, and the community is invited to review both drafts and provide feedback before they are finalized. ## New OpenVX Extensions Streamline Compute Workloads on Heterogeneous SoCs DevFeed: [New OpenVX Extensions Streamline Compute Workloads on Heterogeneous SoCs]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-04-13T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [Computer vision](), [Artificial Intelligence](), [API](), [Hardware](), [systems]() Tags: [ai](), [api](), [blog](), [compute](), [computer-vision](), [distributed](), [hardware](), [openvx](), [release]() ### AI overview The OpenVX Working Group has released the Target Kernel and Node Command extensions for computer vision and AI applications on heterogeneous SoCs. The extensions support remote compute execution and asynchronous runtime control, and their functionality is planned for inclusion as core features in OpenVX 2.0. ### Source excerpt New extensions address long-standing challenges in distributed computing and runtime control, delivering the final core features for OpenVX 2.0. ## Khronos Adds Middleware Insights to the OpenXR Extension Matrix DevFeed: [Khronos Adds Middleware Insights to the OpenXR Extension Matrix]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-04-07T13:00:00Z Content type: article Language: en Sources: [Blogs Khronos Blog]() Topics: [Extension]() Tags: [api](), [blog](), [component](), [developers](), [extension](), [improvements](), [insights](), [middleware](), [openxr](), [visibility]() ### AI overview The Khronos OpenXR working group expanded its Extension Matrix with self-reported support data from middleware providers. The update gives developers more visibility into extension availability across the XR stack, while support may still vary by runtime and device. ### Source excerpt The Khronos OpenXR working group has expanded its Extension Matrix to include self-reported data from middleware providers. Developers now have a clearer view of what's available across the broader XR stack. ## From Specification to Practice: Unlocking glTF's Full Potential DevFeed: [From Specification to Practice: Unlocking glTF's Full Potential]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-04-06T13:00:00Z Content type: article Language: en Sources: [Blogs Khronos Blog]() Topics: [3D](), [Development](), [Learning]() Tags: [3d](), [api](), [blog-glt](), [developers](), [education](), [gltf](), [resources](), [standards](), [tutorials]() ### AI overview The Khronos 3D Formats Working Group has launched an Education, Insights, and Outreach Subgroup to provide guidance, resources, and practical information for using glTF and related standards. The initiative expands earlier 3D Commerce education efforts across industries and will develop technical blogs, tutorials, videos, and other learning resources. ### Source excerpt 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-world information they need to unlock glTF's full potential. ## Video Encoding and Decoding with Vulkan Compute Shaders in FFmpeg DevFeed: [Video Encoding and Decoding with Vulkan Compute Shaders in FFmpeg]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-03-16T17:04:00Z Content type: article Language: en Sources: [Blogs Khronos Blog]() Topics: [FFmpeg (Fast Forward Moving Picture Experts Group)](), [GPU](), [shaders](), [Compression](), [coding]() Tags: [api](), [blog-vulkan-vulkan-vide](), [compression](), [ffmpeg](), [gpu](), [performance](), [shaders](), [video](), [vulkan]() ### AI overview This article explains how FFmpeg uses Vulkan Compute shaders to accelerate encoding and decoding of professional-grade video on consumer GPUs. It describes the parallel and serial stages of codec pipelines and how this approach complements Vulkan Video's fixed-function support. ### Source excerpt In this blog we explore how FFmpeg uses Vulkan Compute to seamlessly accelerate encoding and decoding of even professional-grade video on consumer GPUs -- unlocking GPU compute parallelism at scale, without specialized hardware. This approach complements Vulkan Video's fixed-function codec support, extending acceleration to formats and workflows it doesn't cover.