Skip to content

Remove Meta-Layers - add Layer Manifest File Format Version 1.2.2 #2079

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
charles-lunarg merged 1 commit into from
Oct 23, 2026
Merged

Remove Meta-Layers - add Layer Manifest File Format Version 1.2.2 #2079

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 0 additions & 23 deletions docs/LoaderApplicationInterface.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,6 @@
- [MacOs Dynamic Library Usage](#macos-dynamic-library-usage)
- [Bundling the Loader With An Application](#bundling-the-loader-with-an-application)
- [Application Layer Usage](#application-layer-usage)
- [Meta-Layers](#meta-layers)
- [Implicit vs Explicit Layers](#implicit-vs-explicit-layers)
- [Override Layer](#override-layer)
- [Forcing Layer Source Folders](#forcing-layer-source-folders)
Expand Down Expand Up @@ -359,28 +358,6 @@ information on layer ordering.
> * The `vkEnumerateDeviceLayerProperties` function


### Meta-Layers

Meta-layers are layers which contain an ordered list of other layers to enable.
This is to allow grouping layers together in a specified order so that they can
interact properly.
Originally, this was used to group together the individual Vulkan Validation
layers in the proper order to avoid conflicts.
It was necessary because instead of a single Validation layer, validation was
split into multiple component layers.
The new `VK_LAYER_KHRONOS_validation` layer pulled everything into a single
layer, dropping the need for meta layers.
While not necessary for validation anymore, VkConfig does use meta layers to
group layers together based on user's preferences.
More can be found out about this functionality through both the
[VkConfig documentation](https://github.com/LunarG/VulkanTools/blob/main/vkconfig/README.md)
and the section later on the [Override Layer](#override-layer).

Meta-layers are detailed more in the
[Meta-Layers](LoaderLayerInterface.md#meta-layers) section of the
[LoaderLayerInterface.md](LoaderLayerInterface.md) file in this folder.


### Implicit vs Explicit Layers

![Different Types of Layers](./images/loader_layer_order.png)
Expand Down
60 changes: 0 additions & 60 deletions docs/LoaderInterfaceArchitecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,68 +168,8 @@ VkConfig can be found by either installing the
[Vulkan SDK](https://vulkan.lunarg.com/) or by building the source out of the
[LunarG VulkanTools GitHub Repo](https://github.com/LunarG/VulkanTools).

VkConfig generates three outputs, two of which work with the Vulkan loader and
layers.
These outputs are:
* The Vulkan Override Layer
* The Vulkan Layer Settings File
* VkConfig Configuration Settings

These files are found in different locations based on your platform:

<table style="width:100%">
<tr>
<th>Platform</th>
<th>Output</th>
<th>Location</th>
</tr>
<tr>
<th rowspan="3">Linux</th>
<td>Vulkan Override Layer</td>
<td>$USER/.local/share/vulkan/implicit_layer.d/VkLayer_override.json</td>
</tr>
<tr>
<td>Vulkan Layer Settings</td>
<td>$USER/.local/share/vulkan/settings.d/vk_layer_settings.txt</td>
</tr>
<tr>
<td>VkConfig Configuration Settings</td>
<td>$USER/.local/share/vulkan/settings.d/vk_layer_settings.txt</td>
</tr>
<tr>
<th rowspan="3">Windows</th>
<td>Vulkan Override Layer</td>
<td>%HOME%\AppData\Local\LunarG\vkconfig\override\VkLayerOverride.json</td>
</tr>
<tr>
<td>Vulkan Layer Settings</td>
<td>(registry) HKEY_CURRENT_USER\Software\Khronos\Vulkan\LoaderSettings</td>
</tr>
<tr>
<td>VkConfig Configuration Settings</td>
<td>(registry) HKEY_CURRENT_USER\Software\LunarG\vkconfig </td>
</tr>
</table>

The [Override Meta-Layer](./LoaderLayerInterface.md#override-meta-layer) is
an important part of how VkConfig works.
This layer, when found by the loader, forces the loading of the desired layers
that were enabled inside of VkConfig as well as disables those layers that
were intentionally disabled (including implicit layers).

The Vulkan Layer Settings file can be used to specify certain behaviors and
actions each enabled layer is expected to perform.
These settings can also be controlled by VkConfig, or they can be manually
enabled.
For details on what settings can be used, refer to the individual layers.

In the future, VkConfig may have additional interactions with the Vulkan
loader.

More details on VkConfig can be found in its
[GitHub documentation](https://github.com/LunarG/VulkanTools/blob/main/vkconfig/README.md).
<br/>
<br/>


## Important Vulkan Concepts
Expand Down
Loading
Loading