@Xeers PROTON_USE_WINED3D**10** ? Such variable is not recognized by Proton. Do you mean PROTON_USE_WINED3D**11**?

try PROTON_USE_WINED3D=1

... But there is no video only audio - Graphical Glitches, Artefacts, when i use PROTON_USE_WINED3D=0 ## Reproduction - Lunch the ...

I was able to start the launcher without `PROTON_USE_WINED3D`, just installed `d3dx9_43 d3dcompiler_43` via protontricks and used `Proton ...

... It will only show with PROTON_USE_WINED3D. Unfortunately the OpenGL renderer is quite slow in-game and the DX11 ...

... I spun the game up using "PROTON_USE_WINED3D=1 %command% -nosplash -skipintro", then set the graphics to their defaults ...

> Ok, followed my own steps this morning, and they failed. > > I spun the game up using "PROTON_USE_WINED3D=1 ...

... However, I found that setting the proton env variable `PROTON_USE_WINED3D=1` at least got the game running every ...

@z5d69, try running with PROTON_USE_WINED3D=1 %command%.

... Since setting PROTON_USE_WINED3D and using primusrun (in my case) works, I suspect this is an issue with DXVK ...

... something to log output? If so how do I do it and keep this setting? PROTON_USE_WINED3D=1 %command%.

`PROTON_USE_WINED3D=1` using OpenGL removed the flicker

OpenGL in the graphics settings and `PROTON_USE_WINED3D=1` removed the flicker

`PROTON_USE_WINED3D=1 %command%` started use DirectD3D11, but wined3d use OpenGL, DXVK stopped working?

Game runs fine if `PROTON_USE_WINED3D` is set

It seems to work fine with `PROTON_USE_WINED3D=1`

> It seems to work fine with `PROTON_USE_WINED3D=1` Can confirm. Interestingly, before proton defaulted to DXVK, it didn ...

@StoneyFish you tried it with `PROTON_USE_WINED3D=1` as well ?

> @StoneyFish you tried it with `PROTON_USE_WINED3D=1` as well ? Yes

> > @StoneyFish you tried it with `PROTON_USE_WINED3D=1` as well ? > > Yes It does not crash. Just I have a ...

It happens when you run the game with PROTON_USE_WINED3D=1

... When launching the game using `PROTON_USE_WINED3D=1 %command%` it starts, but there are visual glitches, the performance is ...

Meant to say this PROTON_USE_WINED3D=1 %command% Need the =1

... in launch options, don't expect good performance with that GPU and Wine's D3D11 though. PROTON_USE_WINED3D %command%

... MESA_GL_VERSION_OVERRIDE=4.5COMPAT PROTON_USE_WINED3D=1 %command%

I can confirm this behaviour. PROTON_USE_WINED3D=1 doesn't help.

With nvidia 430.26 and without PROTON_USE_WINED3D=1 the issues seem to be gone. - Everything works fine as ...

Using the "PROTON_USE_WINED3D=1" launch option does fix the issue.

... All version (Experimental, 7.0-6, ...) Logs with "PROTON_USE_WINED3D=1": [steam-1200720.log](https://github.com/ValveSoftware/Proton ...

... Game would not launch without `PROTON_USE_WINED3D=1`, it does launch with it but displays the same image as ...

`PROTON_USE_WINED3D=1 %command%` no longer fixes the crashing for me :unamused:

> `PROTON_USE_WINED3D=1 %command%` no longer fixes the crashing for me Same... crashes on synchronizing.

@joro1881 Try using `PROTON_USE_WINED3D=1 PROTON_NO_ESYNC=1` as a launch option

... this results in the same message, confusingly. - Tried using launch option `PROTON_USE_WINED3D=1 %command%`: This stops the error ...

... The occasional freeze caused by the lobby list still persists. (I'm still starting the game with `PROTON_USE_WINED3D ...

Ok yeah with `PROTON_USE_WINED3D=1` and 5.0-7 it is indeed working!

`PROTON_USE_WINED3D=1` fixes crashing and on 5.0-9 the SFX are working!

@kisak-valve Using "PROTON_USE_WINED3D=1" fixed the stuttering dramatically, and made it playable. D3D WITH VSYNC DISBALED LOG ...

... ve just adjusted my launch options to this `PROTON_USE_WINED3D=1 taskset -c 0-3 %command%` and now the ...