Elite Dangerous initially uses dGPU, but then tries to use iGPU, preventing the game from launching

BOTFerris commented 4 months ago

Please describe your issue as accurately as possible.

When launching the game (via Heroic), the game simply does not open. Using environment variable "VK_ICD_FILENAMES = /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/nvidia_icd.json" or "DXVK_FILTER_DEVICE_NAME=NVIDIA". This is due to DXVK initially using the dGPU, but then (as directly quoted by CommandMC, A contributor to Heroic.) "then for some reason the application creates another device (if that's the right term) and that for some reason uses your iGPU". The variables simply filters the "devices" to only use the dGPU, but that should happen automatically.

Software information

Elite Dangerous

System information

GPUs: GPU 0: Name: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] IDs: D=25a5 V=10de SD=153a SV=1025 Driver: nvidia GPU 1: Name: Intel Corporation TigerLake-H GT1 [UHD Graphics] IDs: D=9a60 V=8086 SD=1539 SV=1025 Driver: i915
Wine version: Wine-GE-Proton8-26
DXVK version: v2.3.1

Apitrace file(s)

N/A

For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

Log files

Please attach Proton or Wine logs as a text file:

When using Proton, set the Steam launch options for your game to PROTON_LOG=1 %command% and attach the corresponding steam-xxxxx.log file in your home directory.
When using regular Wine, use wine game.exe > game.log 2>&1 and attach the resulting game.log file.
[WITHOUT]9c203b6ed35846e8a4a9ff1e314f6593-lastPlay.log [WITH VAR]9c203b6ed35846e8a4a9ff1e314f6593-lastPlay.log

Blisto91 commented 4 months ago

Just to make a small clarification. Dxvk just orders the list of GPUs presented to the game so that the dGPU is the first one listed, but a game can choose to use another one if it wants to.

artemyto commented 3 months ago

Maybe this is worth retest on the latest master because of https://github.com/doitsujin/dxvk/pull/4212

doitsujin / dxvk