liblsfg-vk-layer.so missing vkGetInstanceProcAddr export — layer fails to load

[Albedo-dev]

Environment

• OS: CachyOS (Arch-based), Linux 6.19.6-2-cachyos
• GPU: AMD RX 6700 XT (RDNA2)
• Driver: RADV (Mesa Vulkan)
• Vulkan: 1.4.328
• Package: lsfg-vk-git 2.0.0.dev.r19.f17e9ce-1 (AUR)
• Compiler: Clang 21.1.8

Issue

The Vulkan loader fails to find vkGetInstanceProcAddr in liblsfg-vk-layer.so,
so the layer never activates.

Vulkan loader errors

vulkaninfo | grep -i lsfg
ERROR: [Loader Message] Code 0 : loader_create_instance_chain: Failed to find 'vkGetInstanceProcAddr' in layer "liblsfg-vk-layer.so"
ERROR: [Loader Message] Code 0 : loader_create_device_chain: Failed to find 'vkGetInstanceProcAddr' in layer "liblsfg-vk-layer.so". Skipping
layer.
VK_LAYER_LSFGVK_frame_generation (Lossless Scaling frame generation layer) Vulkan version 1.4.328, layer version 2:

Diagnosis

The shared library does not export any Vulkan symbols:

$ nm -D /usr/lib/liblsfg-vk-layer.so | grep vkGetInstanceProcAddr
(no output)

The layer JSON is registered correctly in /usr/share/vulkan/implicit_layer.d/,
but the .so is missing the required entry point.

Steps to reproduce

1. Install lsfg-vk-git from AUR
2. Run vulkaninfo | grep -i lsfg
3. Observe loader errors

Expected behavior

The layer should load successfully and vkGetInstanceProcAddr should be exported

[PancakeTAS]

lsfg-vk uses the layer negotiation entrypoint and disables itself if not configured to load.
This is not a bug, this is intended behavior and the warning will be silenced in a future commit.

If you need help getting lsfg-vk to run, create a discussion post, not an issue.