The Vulkan registry contains formatted specifications of the Vulkan API, header files, API reference pages, the reference card, and related documentation. The registry also links to the GitHub repository where the sources for these documents can be found.
Graphics and compute shaders for Vulkan are defined using an intermediate representation called SPIR-V, for which specifications and headers are published in the SPIR-V Registry. There are a variety of compilers and other tools for generating SPIR-V code. We encourage developers to explore related Vulkan material starting at the top-level Vulkan landing page.
NVIDIA fully made their presence known in the video card market with the release of the GeForce 256 GPU (graphics processing unit) on October 11, 1999. It was considered as the first GPU worldwide and provided full support for DirectX 7. It also featured 32 MB of DDR memory. The Intel Pentium III Coppermine series was first introduced on. Place (import) graphics The Place command is the primary method used to insert graphics into InDesign because it provides the highest level of support for resolution, file formats, multipage PDF and INDD files, and color. To place graphics is also referred to as import images and insert pictures.
The GLSL Shading Language GitHub repository contains OpenGL Shading Language extensions to be used with an offline GLSL compiler generating SPIR-V code for use with Vulkan. These specifications were previously maintained in the Vulkan-Docs repository and published in the Vulkan Registry.
Pasting vector graphics straight into your InDesign layouts can be a huge timesaver, and is particularly useful when you’re still in the experimental, draft stages of a design, where you want to be switching up colors and effects constantly without the hassle of having to resave and relink freshly edited Illustrator images all the time. Get all of Hollywood.com's best Movies lists, news, and more.
Index to the Vulkan Registry page content:
- Vulkan Documentation and Extensions: Procedures and Conventions (the “Style Guide”)
- Vulkan 1.1 and Vulkan 1.0 Material
- Vulkan GitHub Repositories
- API and Extension Specification Repository
Vulkan 1.2 API Specifications
We currently publish the Vulkan API Specification in PDF and HTML forms. The single-file HTML documents are much slower to load than the corresponding chunked HTML documents, while the PDF is quickest to load and is suitable for offline use. Links into the specification from other documents and tools, such as the reference pages and the validation layers, currently target the single-file HTML document although we hope to target the chunked document eventually.
There are several versions of the Vulkan 1.2 Specification, as well as related Specifications and collateral material:
- Vulkan 1.2 Core API + all published Extensions(Chunked HTML)(PDF). (Single-file HTML) This Specification includes all registered Vulkan extensions which have been incorporated into the Specification Repository, including KHR, EXT, and vendor extensions.
- Vulkan 1.2 Core API(Chunked HTML)(PDF) (Single-file HTML)
- Vulkan 1.2 Core API + Khronos-defined Extensions(Chunked HTML)(PDF). (Single-file HTML) This Specification includes Khronos-defined KHR extensions such as the Window-System Interface Extensions used to post images to a display on different platforms and window systems.
Khronos Data Format Specification
The Data Format Specification (version 1.3) defines compressed texture formats used by Vulkan, and portions of that specification are incorporated into the Vulkan API Specification by reference.
Vulkan Documentation and Extensions: Procedures and Conventions
The Vulkan Documentation and Extensions: Procedures and Conventions document (colloquially, the “Style Guide”) defines mandatory and recommended conventions and best practices used in creating and modifying the API Specification and extensions. Authors wishing to write Vulkan extension specifications, or contribute to existing specifications, should familiarize themselves with and adhere to this document.
API Reference Pages
The Vulkan API Reference Pages describe how to use individual core API and extension commands. The goal is to define all commands and structures in the core API and extensions, although there may be some omissions. In addition to the format published here, it is possible to generate other formats from the reference page sources, such as PDF or Unix nroff man page sources.
- Vulkan API Reference Pages(HTML, one file per reference page)
Note: As of the 1.2.131 update, we have replaced the 1.1 reference pages with 1.2 reference pages.
The reference pages are generated by automatic extraction from the Specification source, and are not checked into GitHub. The set of pages linked above are generated from the 1.2 API Specification including all extensions, but sets of pages including arbitrary extensions can be generated in the same fashion as generating specifications including arbitrary extensions.
Vulkan 1.1 Material
We still maintain the Vulkan 1.1 Specification and related documents, which include:
- Vulkan 1.1 Core API + all published Extensions(Chunked HTML)(PDF). (Single-file HTML) This Specification includes all registered Vulkan extensions which have been incorporated into the Specification Repository, including KHR, EXT, and vendor extensions.
- Vulkan 1.1 Core API(Chunked HTML)(PDF) (Single-file HTML)
- Vulkan 1.1 Core API + Khronos-defined Extensions(Chunked HTML)(PDF). (Single-file HTML) This Specification includes Khronos-defined KHR extensions such as the Window-System Interface Extensions used to post images to a display on different platforms and window systems.
- The Vulkan 1.1 API Quick Reference is a compact document summarizing the Vulkan 1.1 API commands, structures, and enumerants. Note: The Quick Reference has not yet been updated for Vulkan 1.2.
- The InDesign sources for the 1.1 reference guide are also available, formatted as a .zip file.
Vulkan 1.0 Material
We still maintain the Vulkan 1.0 Specification and related documents, which include:
- Vulkan 1.0 Core API + all published Extensions(Chunked HTML)(PDF). (Single-file HTML) This Specification includes all registered Vulkan extensions applicable to Vulkan 1.0 which have been incorporated into the Specification Repository, including KHR, EXT, and vendor extensions.
- Vulkan 1.0 Core API(Chunked HTML)(PDF) (Single-file HTML)
- Vulkan 1.0 Core API + Khronos-defined Extensions(Chunked)(PDF). (Single-file HTML) This Specification includes Khronos-defined KHR extensions such as the Window-System Interface Extensions used to post images to a display on different platforms and window systems.
- The Vulkan 1.0 API Quick Reference is a compact document summarizing the Vulkan 1.0 API commands, structures, and enumerants.
- The InDesign sources for the 1.0 reference guide are also available, formatted as a .zip file.
Vulkan GitHub Repositories
API and Extension Specification Repository
The Vulkan-Docs repository contains the Asciidoctor source for the Vulkan core API specification, and for registered Vulkan API extensions.
All published extension specifications are included in the main git branch. Specifications and reference pages can be built with or without different combinations of extensions by appropriate invocation of the Makefile.
All versions of the Vulkan Specification can be generated out of the main branch.
Other branches in the repository are of historical interest only.
Registered and published extensions are listed below, grouped by Author/Vendor ID. The links are to extension reference pages; these pages are quick to load compared to the full Vulkan 1.2 Core API + all published Extensions Specification, and they link back to it if more information or context is needed. The list of links is generated based on the supported tags in xml/vk.xml in Vulkan-Docs, and may contain anomalies in the form of links to extensions marked as supported by a vendor, but whose specifications have not yet been merged into the Vulkan-Docs repository.
- KHR Extensions (Khronos)
- EXT Extensions (Multivendor)
- AMD Extensions (Advanced Micro Devices, Inc.)
- ANDROID Extensions (Google LLC)
- FUCHSIA Extensions (Google LLC)
- GGP Extensions (Google, LLC)
- GOOGLE Extensions (Google LLC)
- IMG Extensions (Imagination Technologies)
- INTEL Extensions (Intel Corporation)
- MVK Extensions (The Brenwill Workshop Ltd.)
- NN Extensions (Nintendo Co., Ltd.)
- NV Extensions (NVIDIA Corporation)
- NVX Extensions (NVIDIA Corporation)
- QCOM Extensions (Qualcomm Technologies, Inc.)
- QNX Extensions (BlackBerry Limited)
- VALVE Extensions (Valve Corporation)
Vulkan-Docs also contains the header files, API Registry, and reference page sources.
Header Files
For most developers, the C header files provided with a loader and/or driver package, such as the one defined in the loader and validation layers GitHub repository, are all that's needed. We also provide a canonical version of these headers corresponding to spec updates in the KhronosGroup/Vulkan-Headers repository. These headers also include a C++ header generated from the Vulkan-Hpp project.
This repository also includes a JSON file containing Valid Usage ID (VUID) tags (and corresponding valid usage statements) extracted from the specification sources. This is used only by the validation layer, at present.
All Vulkan headers provided by Khronos are ultimately generated from the Vulkan-Docs repository. If the headers in Vulkan-Headers aren't sufficient, you may clone the Vulkan-Docs repository and generate headers yourself, following instructions there. If you need to generate a customized version of the headers, modify the API Registry and scripts under xml/.
Note: there are two static headers included in Vulkan-Docs, vk_platform.h and vulkan.h. These are static headers that are not generated from the Vulkan-Docs repository.
API Registry
Vulkan defines an API Registry for the core API and extensions, formally defining command prototypes, structures, enumerants, and many other aspects of the API and extension mechanisms. The Vulkan Registry is used for many more purposes than most other Khronos API registries, and is the basis for generating the header files; Asciidoctor include files used in the Specification, and reference pages for interface definitions, parameter and member validity language, and synchronization language; and more.
The Registry is in an XML file called vk.xml and currently located in the Vulkan-Docs repository under xml/. This directory also includes a formal RELAX NG XML schema and scripts used to generate the various outputs.
Documentation of the XML schema is available.
Conformance Test Suite Repository
The VK-GL-CTS repository contains the source code for the Vulkan Conformance Tests. Note that while the CTS source code is freely available, you must be a Khronos Adopter and pay the Adopter Fee in order to use the Vulkan trademark for your implementation.
Loader and Validation Layers Repositories
There are several additional Khronos Github repositories containing Vulkan source code, libraries, and tools:
- The Vulkan-Headers repository contains a copy of the Vulkan XML API Registry and scripts for processing it, taken from the latest public specification update in the Vulkan-Docs project, and the corresponding generated Vulkan API headers.
- The Vulkan-Tools repository contains Khronos official Vulkan Tools and Utilities for Windows, Linux, Android, and MacOS.
- The Vulkan-ValidationLayers repository contains the Khronos official Vulkan validation layers for Windows, Linux, Android, and MacOS.
- The Vulkan-Loader repository contains the Vulkan loader that is used for Linux, Windows, MacOS, and iOS.
Sample Code Repository
The Vulkan-Samples repository contains sample code showing use of Vulkan, contributed by various Khronos members and other authors.
Other Repositories
Other Khronos repositories containing Vulkan material include:
- The Vulkan-Hpp repository contains code used to generate vulkan.hpp, a C++ binding for Vulkan. A version of vulkan.hpp is included in the Vulkan-Headers repository.
Providing Feedback on the Registry
Khronos welcomes comments and bug reports. To provide feedback on the Vulkan registry itself (such as reporting missing content, bad links, etc.), file an issue in the Vulkan-Web-Registry Github project.
For the Vulkan Specification or other documentation and tools, file an Issue on the appropriate GitHub Repository.
The Graphics Processing Unit (GPU), found on video cards and as part of display systems, is a specialized processor that can rapidly execute commands for manipulating and displaying images. GPU-accelerated computing offers faster performance across a broad range of design, animation, and video applications.
This means that you get a significant performance boost: InDesign runs faster and more smoothly than ever before.
To use GPU Performance, your Mac should have a minimum of 1024 MB of VRAM (2 GB recommended), and your computer must support Metal or minimum OpenGL version 4.0 or greater.
Metal capable GPU feature is not available to all users as it is being rolled out in a phased manner from 16.2 or later.
Supported machines
- iMac 4K
- iMac 5K
- MacBook Pro Retina
- Mac Pro connected to a HiDPI monitor
- Mac mini connected to a HiDPI monitor
To check for VRAM values:
- Mac 10.9: Choose Mac > About This Mac > More Info (Graphics information).
- Mac 10.10, 10.11: Choose Mac > About This Mac (Graphics information).
To find out if your computer supports the required OpenGL version (4.0 or later), see this Apple Support document.
HiDPI monitors are becoming the standard. With the high monitor resolutions, it is getting difficult for CPU to handle the rendering.
Also, InDesign’s default display performance has always been set to Typical Quality. Due to this you do not see the images placed in the document in their full fidelity. This was done to provide you with optimum performance when you perform operations like zooming, scrolling, panning etc.
This is where the GPU comes into play. Rendering on high-density displays is best handled by the GPU. GPU acceleration makes the rendering of the documents faster while zooming, scrolling, and panning. With the GPU enhancements, InDesign now shows images in their fullest fidelity without compromising the performance.
If your system has a compatible GPU card, InDesign renders the document using the GPU by default and sets the Display Performance to High Quality.
The enhanced performance from using the GPU in InDesign powers features like Animated Zoom which make zoom actions smooth and animated. Here is how it works:
Select the zoom tool (Z), and do one of the following:
- Press and hold down the mouse button (long press) to zoom in to the center. Press Option and hold down the mouse button (long press) to zoom out.
- Press and drag the pointer to the right to zoom in or to the left to zoom out.
- Press Shift to switch to marquee zoom mode.
After making sure your computer meets the system requirements for GPU Performance, follow these instructions to enable the feature in InDesign.
In the application bar, click the GPU Performance icon to display the GPU Performance settings in the Preferences panel.
Select (to enable) or clear (to disable) the GPU Performance check box and click OK.
When the GPU Performance feature is enabled, you can switch (Ctrl + E) between the GPU Preview mode and the CPU Preview mode.
- To switch to GPU Preview, choose View > GPU Preview.
- To switch to CPU Preview, choose View > Preview on CPU.
You can change GPU Performance feature settings in the Preferences panel.
Besides enabling or disabling GPU Performance, here are other GPU Performance settings you can modify in the Preferences panel:
Gpu Indesign Download
- Animated Zoom: Select this check box to make zoom actions smooth and animated.
Gpu Design Engineer
InDesign now uses the native macOS Metal API to improve performance. Metal provides near-direct access to the graphics processing unit (GPU), enabling you to maximize the graphics and compute potential of your apps.