The debug scripts dump the environment they have when they are generated. So if you generate the debug scripts while Proton is configured to use DXVK (the default), then the scripts will use DXVK. If you generate the scripts while using wined3d, then the scripts should use wined3d. So I think this is working as intended.
proton 5.13x1 2020-12DXVK_HUDx1 2020-12DXVK_HUD=fullx1 2020-12DXVK_LOG_LEVELx1 2020-12PROTON_LOG_DIRx1 2020-12PROTON_NO_D3D11x1 2020-12PROTON_NO_ESYNCx1 2020-12PROTON_NO_FSYNCx1 2020-12PROTON_USE_WINED3Dx1 2020-12PROTON_USE_WINED3D=1x1 2020-12STEAM_COMPAT_CLIENT_INSTALL_PATH="/mnt/old_drive/utku2/.local/share/Steam"x1 2020-12VKD3D_DEBUGx1 2020-12WINEDEBUGx1 2020-12WINEDEBUG="-all"x1 2020-12WINEDLLOVERRIDES="steam.exe=b;dotnetfx35.exe=b;mfplay=n;dxvk_config=n;d3d11=n;d3d10=n;d3d10core=n;d3d10_1=n;d3d9=n"x1 2020-12WINEESYNC="1"x1 2020-12
Proton 5.13 & 5.0, couldn't tested 4.11 due to time limitation
ubuntu 20.04
steam stable (Dec 7 2020)
Due to https://github.com/ValveSoftware/Proton/issues/66#issuecomment-544262665 (steam client disables
gallium nine standalonewhen game is launched through the steam client, it seems like this issue still persists) I have been using the scripts created by this method to launch my games. But I have realised thatPROTON_USE_WINED3Ddoes nothing when used in these scripts or inuser_settings.py, whileDXVK_HUDworks in both cases.I am reporting this issue because there are tutorials on the internet where DXVK is disabled through the
user_settings.pyTo test directx9 I have used trackmania nations forever
To test directx11 I have used Maximum action
Example on trackmania (directx9 game);
However as a workaround removing
;d3d11=n;d3d10=n;d3d10core=n;d3d10_1=n;d3d9=nfrom the line:WINEDLLOVERRIDES="steam.exe=b;dotnetfx35.exe=b;mfplay=n;dxvk_config=n;d3d11=n;d3d10=n;d3d10core=n;d3d10_1=n;d3d9=n" \in the script turns off DXVK(
run2is the modified file)