Open NTMan opened 6 years ago
PROTON_NO_ESYNC=1 %command%
This game seemingly works perfectly with this launch option. Won't start without it.
My PS4 controller's triggers weren't detected, but this seems to be a problem even on Windows. Was "solved" by changing "PS4 controller support" to "Generic controller support" in Steam's options.
Online works, I could find players and matches would start.
Thanks I confirm that PROTON_NO_ESYNC=1 %command%
helps.
But game still have issues:
1) Some cutscenenes impossible to see because of black window. Only background sounds are heard and subtitles and FPS counter.
2) And sometimes on cutscene missing some textures.
3) Artifacts from white squares.
Hello @NTMan, @z0z0z, since PROTON_NO_ESYNC=1
makes a difference, please run ulimit -Hn
and confirm that it gives a high value and not 4096.
Hello @NTMan, @z0z0z, since
PROTON_NO_ESYNC=1
makes a difference, please runulimit -Hn
and confirm that it gives a high value and not 4096.$ ulimit -Hn 1048576
I am was used this instruction: https://github.com/zfigura/wine/blob/esync/README.esync And bump FD limits in both files:
echo "DefaultLimitNOFILE=1048576" >> /etc/systemd/user.conf echo "DefaultLimitNOFILE=1048576" >> /etc/systemd/system.conf
Everything works as expected, but I have a black screen instead of the cutscenes. I tried everything. I don't know how you and this guy managed to have the cutscenes.
EDIT: OK, I did it. I will explain everything in the relevant section in ProtonDB.
Anyone got the cutscenes working with a 64bit prefix?
Anyone got the cutscenes working with a 64bit prefix?
I have never tried, but it works with a 32 bit prefix. It's on ProtonDB.
Game still hangs on a white screen with Proton 7.0. Only way to play it is by disabling esync and fsync (PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
), but raising the CPU usage. Logs:
steam-311730.tar.gz
Specs: O.S: Manjaro Kernel: 5.15 (futex2 patched) Driver: 510.60.02 GPU: GTX 970 4Gb
Game still suffers from the "hang issue" with Proton 8.0-1 (unless you disable FSYNC and ESYNC)
Log file: steam-311730.tar.gz
Specs
I can also confirm on my oled with latest proton Experimental build, it still gets stuck on a white screen unless I turn off esync and fsync. Downgrading to 5.13-6 on my end allowed me to boot with only "PROTON_NO_ESYNC=1", but it still froze a few seconds after the first 2 logos.
@kisak-valve I think this game might need the no esync and no fsync commands added in as a workaround for the time being if possible, since from my testing and others here, on protondb, and on the steam community hub, the game won't work on newer versions of Proton without it.
From my testing the game seemed to run fine enough even playing through some matches, but I haven't tested further beyond that.
@gofman Terribly sorry for the ping again, but I wanted to ask since I checked in the proton files and noticed, would it be possible to add the noesync and nofsync workarounds for this game. From my testing and checking around, this game will get stuck on a white screen without these commands.
Compatibility Report
System Information
I confirm:
steam-311730.log
Symptoms
The game show empty window and stuck.
Reproduction
Just launch the game.