Hello @Byter09, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/150#issuecomment-493482229.
PROTON_NO_ESYNC=1x1 2019-05WINEPREFIXx1 2019-05WINEPREFIX=~/SteamLibrary/steamapps/compatdata/359320/pfxx1 2019-05
Compatibility Report
System Information
I confirm:
steam-359320.log
Symptoms
Reproduction
Create a new prefix with:
The reason for this can be found here: https://github.com/redmcg/wine/wiki#the-official-build-of-proton-42-runs-ed
After that start Elite Dangerous with
VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json" PROTON_NO_ESYNC=1 %command%The VK_ICD part is supposedly workaround to use radv instead of amdvlk as reported here to prevent exactly the problem I'm facing.
It does not matter though, even without any modified launch options the same problem occurs.
I believe, that the
VK_ICD_FILENAMESvariable is not being passed to the Elite Dangerous process itself from the launcher. I already used it in X4: Foundations and that worked great.