Steam client version (build number or date): Oct 2 2019, at 18:45:57. versions: 1570046470
Distribution (e.g. Ubuntu): Debian testing, and Debian unstable
Opted into Steam client beta?: [Yes/No] Yes (same happens on non-beta tho)
Have you checked for system updates?: [Yes/No] Yes
Please describe your issue in as much detail as possible:
I have my custom Vulkan layer and I use VK_LAYER_PATH to enable searching for it. It has both 32-bit and 64-bit versions in the path (in different directories). Similarly named Vulkan layer is present in system default search paths too. But I do use environment variable VK_LAYER_PATH to load force search path to check my version first. It works with all Vulkan apps, including native games, benchmarks, tools and with DXVK when using via lutris. They load properly my version of the layer first.
However Steam completely ignores this environment variable, and when I request to enable this layer (using VK_INSTANCE_LAYERS) games load the similarly named layer from system search path ignoring my VK_LAYER_PATH.
I am expecting the bug is somehow related to fossilize Vulkan layer injection done by Steam for capturing and caching Vulkan pipelines / shaders for offline analysis, redistribution and pre-compilation.
Your system information
Please describe your issue in as much detail as possible:
I have my custom Vulkan layer and I use
VK_LAYER_PATHto enable searching for it. It has both 32-bit and 64-bit versions in the path (in different directories). Similarly named Vulkan layer is present in system default search paths too. But I do use environment variableVK_LAYER_PATHto load force search path to check my version first. It works with all Vulkan apps, including native games, benchmarks, tools and with DXVK when using via lutris. They load properly my version of the layer first.However Steam completely ignores this environment variable, and when I request to enable this layer (using
VK_INSTANCE_LAYERS) games load the similarly named layer from system search path ignoring myVK_LAYER_PATH.I am expecting the bug is somehow related to fossilize Vulkan layer injection done by Steam for capturing and caching Vulkan pipelines / shaders for offline analysis, redistribution and pre-compilation.