Compatibility Report

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.

$ 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.

I have written a guide to set up the game here. If you are dealing with the standalone game, this and this might be useful.

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 suffers from the "hang issue" with Proton 8.0-1 (unless you disable FSYNC and ESYNC)

Log file:
steam-311730.tar.gz

Specs

• O.S: Arch
• Kernel: 6.1.24
• GPU: RX 6700 XT (Mesa 23.0.2)

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.

Game still requires the no esync and no fsync workarounds to avoid freezing on a white screen on launch

Game still requires the no esync and no fsync workarounds to avoid freezing on a white screen on launch

Is there a way to enable NTsync-driver support for this case where esync and fsync are not working? This is still an issue with Proton 10 at least in this game.

@ipr that would require a custom build of proton as well as a custom build of the kernel itself, I would advise against it. To workaround the whitescreen issue in this game I'd suggest running it with PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%

@ipr that would require a custom build of proton as well as a custom build of the kernel itself, I would advise against it. To workaround the whitescreen issue in this game I'd suggest running it with PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%

It would probably also help if the no esync and fsync commands were applied by default for this title in proton like they are for flatout 3 and disgaea 4 complete for example

@ipr that would require a custom build of proton as well as a custom build of the kernel itself, I would advise against it. To workaround the whitescreen issue in this game I'd suggest running it with PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%

What I mean is if Valve would add that as an option to Proton? IIRC, NTsync was added to Wine so support would need to be ported over to Proton and have the option when esync/fsync can't be used (like in this case).

I think various distributions are already enabling the driver by default in kernel.

Happy to say this now works fine on Proton 11.0 (beta) without using extra flags.
Framerate is fine too.

In-game videos still show test pattern though.

Here on my end running this game with Proton 11.0 (beta) still requires PROTON_NO_FSYNC (PROTON_NO_ESYNC is no longer needed though). Tested on vanilla Arch, kernel 6.18.17.

@ipr @ranplayer @dariox86 proton 11 defaults to the new ntsync when the kernel counterpart is present as well, and it's expected for the game to launch normally with ntsync. The kernel part was upstreamed on 6.14, so if you're on an older version proton won't use it.

When it is present, the top of the proton log should say ntsync: up and running.

As for videos, at least the starting video with the waves before the main menu, and the initial video when you start story mode both work. If others show test patterns it is likely that not enough people have attempted to play them for steam servers to transcode the videos.

This is funny. I just found out ntsync is not loaded by default. I had to manually load ntsync:
# modprobe ntsync
After loading ntsync it does work under Proton 11.0 (Beta) with XanMod Kernel 7.0.0 on Parabola GNU/Linux-libre.

@dariox86 then the module isn't autoloaded on your end

@ranplayer it's likely the same on your end, what does this return? ls -l /dev/ntsync

@simifor the ntsync module was indeed not enabled by default. After enabling it (echo ntsync | sudo tee /etc/modules-load.d/ntsync.conf) and rebooting, all good. Thank you.

I am actually amazed I was wrong all along at thinking ntsync was just enabled by default.

I am actually amazed I was wrong all along at thinking ntsync was just enabled by default.

You need to load some modules that are not automatically detected. One way to make sure the module is loaded to add file like ntsync.conf into /etc/modules-load.d with just following line:

ntsync

Some kernel modules are not loaded otherwise.

You might need to do systemd daemon-reload after adding the file or just insmod ntsync manually.