and I can see a moving 3D cube with VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json vkcube
However, most, if not all, games will seem to crash, presumably because they are running with AMDVLK despite setting those two environment variables in order to default to RADV. Removing those two variables and globally setting AMD_VULKAN_ICD=RADV seems to resolve the issue and games will run successfully with RADV upon rebooting, but I would like to use the RADV standard to load AMDVLK on a per-application basis via the VK_ICD_FILENAMES variable, and DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 does not seem to enable the ability to do that despite it being the expected functionality.
I have both AMDVLK and RADV implementations of Vulkan installed globally, and in my /etc/environment file, I have set
and via
env | grep -e 'DISABLE' -e 'ICD'
, I can seeWith
vulkaninfo --summary
, I correctly seeand I can see a moving 3D cube with
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json vkcube
However, most, if not all, games will seem to crash, presumably because they are running with AMDVLK despite setting those two environment variables in order to default to RADV. Removing those two variables and globally setting AMD_VULKAN_ICD=RADV seems to resolve the issue and games will run successfully with RADV upon rebooting, but I would like to use the RADV standard to load AMDVLK on a per-application basis via the VK_ICD_FILENAMES variable, and DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 does not seem to enable the ability to do that despite it being the expected functionality.
Results of inxi -Fxz