... Could you try launching with either `PROTON_NO_FSYNC=1 %command%` or `PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%` and see if ...

> It might be interesting to test if setting the game's launch options to `PROTON_NO_FSYNC=1 %command%` or ...

> Full command: > WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 PROTON_NO_FSYNC=1 %command% _Originally posted by ...

> and i set "PROTON_NO_FSYNC=1, PROTON_NO_ESYNC=1" in options to launch If you actually used a comma, don ...

... I disabled those options and i set "PROTON_NO_FSYNC=1, PROTON_NO_ESYNC=1" in options to launch, but the problem ...

... So I temporarily disable fsync/esync using the flags (PROTON_NO_FSYNC=1, PROTON_NO_ESYNC=1), launch the game, exit, then ...

... or performance regression with Proton 4.11 that consistently goes away with PROTON_NO_FSYNC=1, please post it here.

Sekiro doesn't load into game for me, but does with PROTON_NO_FSYNC=1.

#4690 – in Endzone - A World Apart, PROTON_NO_FSYNC=1 seems to reduce or solve hangup issues.

@FantasyPvP try putting `PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_DEBUG_COMMANDS=1 %command%` in the launch options. `PROTON_NO_ESYNC=1` isn't ...

... in steam I put : ``` PROTON_USE_WINED3D=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% /fullscreen 1920 1080 ``` any version of proton ...

Tried with `PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1`, no change in behavior.

@ryannathans Does launching with this make a difference? ``` PROTON_NO_FSYNC=1 %command% ```

Also tried using options `PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%`, no changes.

... Is this expected behavior? Shouldn't PROTON_NO_ESYNC=1 and PROTON_NO_FSYNC=1 also respectively imply WINEESYNC=0 and WINEFSYNC ...

@cybik Try the launch command `PROTON_NO_ESYNC=1`, also maybe try `PROTON_NO_FSYNC=1`

@mathew2214 By "enabling fsync", you mean `PROTON_NO_FSYNC=0` or `PROTON_NO_FSYNC=1`? Also, I am using the official Proton ...

... launch option "PROTON_NO_ESYNC=1 %command%" without the "" or try to use "PROTON_NO_FSYNC=1 %command%" or "PROTON_NO_FSYNC=0 %command%"

... valve Thank you very much for your reply. PROTON_NO_FSYNC=1 %command% worked for me and fixed my issue ...

@Diman0 Does it also crash during gameplay if you launch with `PROTON_NO_FSYNC=1 %command%` ?

... It appears proton 7.0-1 with `PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%` is quite stable.

... PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%

... 11 with stock-dxvk does not works too. PROTON_NO_FSYNC=1 is not helpful. I use 5.1.15 ...

... 11 with stock-dxvk does not works too. > PROTON_NO_FSYNC=1 is not helpful. I use 5.1.15 ...

For the video stuttering see if launching without fsync & esync helps. ``` PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% ```

looks not same problem. try PROTON_NO_FSYNC=1. since proton 4.11-5 has fsync problem for me.

... doesn't work for me on proton-4.11.6 at all. PROTON_NO_FSYNC=1 doesn't do anything.

... no effects PROTON_NO_FSYNC=1.

> You might get lucky running with `PROTON_NO_FSYNC=1 %command%` or `PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%` in the game ...

I realize that the issue is old and may be no longer relevant, but I confirm that `PROTON_NO_FSYNC ...

The game is actually much more stable with PROTON_NO_FSYNC=1 (on many Proton versions). Should I ping #2922?

> Replying to https://github.com/ValveSoftware/Proton/issues/4123#issuecomment-1165673768 Okay. Try: PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%

... PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% Looks like that it helped for a little, game still freezes after some ...

Can anyone who is reliably reproducing the disappearing textures issue try it with PROTON_NO_FSYNC=1 %command% launch option?

> Replying to https://github.com/ValveSoftware/Proton/issues/37#issuecomment-1224279597 Setting `PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%` as ...

> Can anyone who is reliably reproducing the disappearing textures issue try it with PROTON_NO_FSYNC=1 %command% launch option ...