Copyright © 2015-2021 LunarG, Inc.
Vulkan Configurator allows overriding the layers configuration used by Vulkan applications at runtime.
A Vulkan application may configure layers when creating a Vulkan Instance. This layers configuration may be overridden using Vulkan Configurator globally or for a selected list of Vulkan applications.
Finally Vulkan Configurator allows using layers from user-defined directories.
- Change Log: The history of Vulkan Configurator releases.
- Bug reports: Open a GitHub issue when you encounter a bug.
- Roadmap: Follow Vulkan Configurator future developments.
- Contributing: Submit a fix or a feature to Vulkan Configurator.
Vulkan Configurator is delivered with the Vulkan SDK.
Using the Vulkan Configurator
Vulkan Configurator is a graphical user interface (GUI) that may be launched from the console using
The tool is distributed differently, depending on the platform:
- Ubuntu packages: Upon installing the
lunarg-vkconfigpackage, the tools will be available from the command line as
- Linux tarball: The vkconfig executable comes pre-built. Run vkconfig on the command line.
- Windows: The tool will be present on the start menu, in the Vulkan SDK menu. User can also invoke from a command line.
- macOS: The tool is provided as an application bundle. Run it by double-clicking the bundle from a Finder window.
Vulkan Configurator may be used with command line arguments to averride layers. Use
vkconfig --help in the console for more information.
Vulkan Layer: A layer is an optional library that can intercept Vulkan functions on their way from the Vulkan application down to the Vulkan drivers. Multiple layers can be chained together to use multiple layer functionalities simultaneously.
Vulkan Layers Configuration: A collection of Vulkan Layers executed in a specific order with specific settings for each layer.
Vulkan Explicit Layers vs Implicit Layer: An explicit layer has to be explicitly activated by the user from source in
vkCreateInstance, using Vulkan Configurator or
VK_INSTANCE_LAYERS environment variable. Implicit layers are enabled by their existence on the system by default.
Vulkan Meta-Layer: Meta-layers are a special kind of layer which is only available through the desktop Vulkan Loader. While usual layers are associated with one particular library, a meta-layer is actually a collection layer which contains an ordered list of other layers called component layers.
Vulkan Override Layer: The Vulkan Override Layer is an implicit meta-layer found on the system with the name
VK_LAYER_LUNARG_override. It is the mechanism used by Vulkan Configurator to override Vulkan applications layers. This layer contains:
- The ordered list of layers to activate
- The list of layers to exclude from execution
- The list of paths to executables that the layers override applies to. If this list is empty, the override is applied to every application upon startup.
Vulkan Layer settings: Per-layer settings loaded by each layer library and stored in the
vk_layer_settings.txt file. This file is located either next to the Vulkan application executable or set globally and applied to all Vulkan applications thanks to Vulkan Configurator. These settings are described here for VK_LAYER_KHRONOS_validation and here for other layers created by LunarG.
Vulkan Layers execution order overview
Vulkan Loader and Layers implementation overview
For detailed information, read the Architecture of the Vulkan Loader Interfaces document.
Vulkan Layers Settings
The layer settings are stored into the
vk_layer_settings.txt file and read directly by the layers.
When *Vulkan Configurator is used to override layers, the Vulkan application local
vk_layer_settings.txt file is ignored by layer ecosystem convention.
Vulkan Configurator does not make any system-wide changes to a system, but it does make user-specific changes. These changes are documented below:
Linux and macOS
Unix systems store files in the following paths:
$HOME/.local/share/vulkan/implicit_layer.d/VkLayer_override.jsontells a Vulkan application which layers to use
$HOME/.local/share/vulkan/settings.d/vk_layer_settings.txttells Vulkan layers which settings to use
Windows systems store files in the following paths:
%HOME%\AppData\Local\LunarG\vkconfig\override\VkLayerOverride.jsontells a Vulkan application which layers to use
%HOME%\AppData\Local\LunarG\vkconfig\override\vk_layer_settings.txttells Vulkan layers which settings to use
In addition, Windows system create registry entries in the following locations:
HKEY_CURRENT_USER\Software\Khronos\Vulkan\ImplicitLayerswill have an entry that points to the JSON file above
HKEY_CURRENT_USER\Software\Khronos\Vulkan\Settingswill have an entry that points to the text file above
HKEY_CURRENT_USER\Software\LunarG\vkconfigstores the application settings for
Environment Variables (Deprecated)
OS Environment Variables are the legacy approach to configure layers however they should be considered deprecated in favor of using
vk_layer_settings.txt either locally, next to the Vulkan Applications or globally, generated from Vulkan Configurator.