4953.223:0168:016c:warn:vkd3d-proton:d3d12_find_physical_device: Multiple adapters found with LUID 03f2.
Multiple GPUs feeding one monitor are always problematic, and in this case it just breaks our adapter selection code. Don't think we can really do much here.
4953.223:0168:016c:warn:vkd3d-proton:d3d12_find_physical_device: Multiple adapters found with LUID 03f2.
Multiple GPUs feeding one monitor are always problematic, and in this case it just breaks our adapter selection code. Don't think we can really do much here.
Would it be possible to sort adapter enumeration so discrete cards come before integrated, or do we already do that?
We're trying to match by PCI vendor/device IDs if we have multiple devices sharing an LUID. I don't know why this doesn't seem to be working here, would require more knowledge of the setup being used, but I'm also not sure how we'd ever really test something like this.
DXGI already enumerates dedicated before integrated.
My system has:
1 x 5070 Ti (the one I want to use for Proton)
2 x 5060 Ti (these are triggerin this error)
I am unable to select the 5070 using DXVK_FILTER_DEVICE_NAME=5070 %command% because of this.
Is there any workaround for this? Perhaps a way to force the 5070 to be GPU 0 so I can just let it use the default?
On multi-GPU Linux you can pick the render GPU (mesa device-select layer) but presenting is bound to the compositor's GPU — so you also need gamescope to own the the presentation.
Fix:
sudo pacman -S vulkan-mesa-device-select lib32-vulkan-mesa-device-selectvendorID:deviceID: vulkaninfo --summary | grep -E 'deviceName|deviceID'MESA_VK_DEVICE_SELECT=10de:XXXX gamescope -W 2560 -H 1440 -r 60 --prefer-vk-device 10de:XXXX -- %command%
proton experimentalx1 2024-07MESA_VK_DEVICE_SELECT=10de:XXXXx1 2026-08DXVK_FILTER_DEVICE_NAME=5070x1 2026-07VKD3D_CONFIG=''x1 2024-07VKD3D_SHADER_CACHEx1 2024-07VKD3D_VULKAN_DEVICE=0.x1 2024-07DXVK_FILTER_DEVICE_NAME=5070 %command%x1 2026-07
Instead of running on a discrete graphics card, the game runs on integrated graphics. The problem appeared after the developers switched to a new version of the Unreal Engine. The issue does not occur when running the game through DXVK with the -dx11 launch option. The problem also does not occur with VKD3D_VULKAN_DEVICE=0.
Software information
Dead by Daylight
System information
Radeon RX 7600 (same with Radeon RX 6400), Radeon Vega SeriesMesa 24.2.0-devel (git-260a5fc7b3)Proton Experimental (bleeding-edge)2.13Log files
steam-381210.log (cat steam-381210.log | grep vkd3d-proton)