THE FINALS (2073850)

[HurleybirdJr]

Compatibility Report

• Name of the game with compatibility issues: THE FINALS
• Steam AppID of the game: 2073850

System Information

• GPU: GeForce RTX 3080Ti
• Video driver version: NVIDIA 545.29.06
• Kernel version: 6.5.13-1-MANJARO
• Link to full system information report as Gist:
• Proton version: Proton Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Proton Log

steam-2073850.log

Symptoms

Reproduction

• Launch game on Steam
• Error pops up and closes game in about 5-10 seconds. (Occasionally asks for TOS age check)

[HurleybirdJr]

EAC installer seems to appear during launch, but Embark use an in-house anti-cheat on alongside it which "isn't ready for Linux" yet. A potential fix will come, but they've said it's not a priority at the moment.

[NTMan]

The game immediately after launch show message "System integrity violation. A disallowed game process memory modification was detected. Error code TFAV0010"

steam-2073850.log

[JGodin-C2C]

EAC installer seems to appear during launch, but Embark use an in-house anti-cheat on alongside it which "isn't ready for Linux" yet. A potential fix will come, but they've said it's not a priority at the moment.

Hello !
Where is the source for this ? i tried to find an official communication, but could not find any concerning the linux port.

[r0b3rtf1sh3r]

terrible. they cant just give a PSA or something regarding it and we stop asking

[polluxau]

terrible. they cant just give a PSA or something regarding it and we stop asking

If you check pins on there discord server it says they dont currently support linux

https://discord.com/channels/1008696016318513243/1009830578545246213/1183134141684920450

[Kagukara]

Looks like it might be working now.

https://www.reddit.com/r/linux_gaming/comments/194yurj/how_to_play_the_finals_on_linux/

[polluxau]

yep working under only proton experimental
rx 6700 10gb, ryzen 3700x

[alasky17]

FWIW - Currently folks with CPUs that have AVX512 support will need to add the clearcpuid=304 kernel boot option for the game to run (this avoids a crash very shortly after launch). There are some intermittent game crashes on the steam deck that are currently under investigation - if you are getting crashes on the deck, please try to capture a log by adding PROTON_LOG=1 %command% to the launch options.

[beh-10257]

@alasky17
not really steam deck but
steam-2073850.log

its basically stopping there I don't know I have an i5-10300H and NVIDIA GeForce GTX 1650 Ti Mobile
maybe that helps
anyway help is much appreciated

update: I just had to wait like the other comments have already said

[NoHidSe]

Replying to #7317 (comment)

I got this issue but i just let it sit for 5 minutes and it opened the game normally. My guess its just compiling shaders

[polluxau]

Replying to #7317 (comment)

Makes sense as his cpu is being pinned to 100% lol

[Pokepunch]

Seems to be working fine on Steam Deck now, although I had to delete my prefix first.

[sevmonster]

Working for me on Steam Runtime with Experimental. Had to add to the boot options as mentioned above.

Attempting to change voice input/output in the settings caused a hang.

[happysmack]

Works for me with either Steam default Proton or Experimental. Enabling the voice chat will cause either a hang or crash. Playing for a few hours I had 3 random crashes. No boot options added. If I tried -opengl, it would result in an error and not open.

[SopaDeMacaco-UmaDelicia]

All I've got is a black empty cmd window with EasyAnticheat_EOS_Setup.exe and then an error pops up saying failed to initialize dependencies.
Archlinux, Steam with Runtime. Ryzen 5800x3d.

[sevmonster]

All I've got is a black empty cmd window with EasyAnticheat_EOS_Setup.exe and then an error pops up saying failed to initialize dependencies. Archlinux, Steam with Runtime. Ryzen 5800x3d.

Make sure you have the Proton EasyAntiCheat runtime installed.

[SopaDeMacaco-UmaDelicia]

Make sure you have the Proton EasyAntiCheat runtime installed.

Yeah, I have it and other EAC games like Apex Legends and Fall Guys work nice. Feels like their own eac_eos installation script doesn't work properly.

[xpander69]

Works great here with proton-experimental and Ryzen 7 5800X3D, RTX 3080, with 545.29.06 drivers.
Just played 5 hours without any issues.
Arch Linux

[DaveKram]

FWIW - Currently folks with CPUs that have AVX512 support will need to add the clearcpuid=304 kernel boot option for the game to run (this avoids a crash very shortly after launch). There are some intermittent game crashes on the steam deck that are currently under investigation - if you are getting crashes on the deck, please try to capture a log by adding PROTON_LOG=1 %command% to the launch options.

Going to add that this works (to get past the initial crash upon startup). On Fedora 39.

Modified grub via /etc/sysconfig/grub, changed GRUB_CMDLINE_LINUX to add clearcpupid=304 at the end.

Ran

sudo grub2-mkconfig -o /etc/grub2-efi.cfg

Rebooted and launched the game. Using Proton Experimental.

How are you aware of disabling AVX512 would solve the crash? Would like to not disable this long term. Think it's a proton issue or The Finals issue?

[SopaDeMacaco-UmaDelicia]

Yeah, I have it and other EAC games like Apex Legends and Fall Guys work nice. Feels like their own eac_eos installation script doesn't work properly.

Ok, this is stupid. I managed to launch it. Looks like this game is using SDL and I had a global environment variable SDL_VIDEODRIVER=wayland to run native linux games in wayland-native mode. So to fix that, either delete that variable or add SDL_VIDEODRIVER=windows %command% to the launch options.

[SopaDeMacaco-UmaDelicia]

Attempting to change voice input/output in the settings caused a hang.

Yeah, if you turn on voice chat game hangs.

[Vinjul1704]

In general, the game seems to work, including online matches, however I noticed 2 issues:

The first one is that the game gets stuck and ultimately crashes during the initial black screen on my Intel Arc system. Launching it with -dx11 to force DirectX 11 over DirectX 12 (default) makes it work. With that, I didn't notice any graphical issues in game either, although there are some initial stutters that I assume come from shader compilation stuff?

Log with DX12: https://gist.github.com/Vinjul1704/032f920f99c11103bf4a7e015d757308

The second issue is the already mentioned voice chat freeze/crash. When enabling it, the game freezes after around 10 seconds. Enabling it via the actual game settings and not the quick toggle option in the ESC menu saves that in the config files and makes the game crash on startup afterwards. Deleting BootSettingsSaveGame.sav and EmbarkOptionSaveGame in AppData/Local/Discovery/Saved/SaveGames resets it (alongside other options).

Log with VC enabled during launch: https://gist.github.com/Vinjul1704/ce60690de5450a7d0f97cfe23dac0c11

Enabling it while the game is running results in a 1GB large log file, which seems to simply spam the "EXCEPTION_ACCESS_VIOLATION" error that's also seen in the above log file until the game actually freezes. If needed, I can upload that log file somewhere too.

System info:

• CPU: Intel Xeon E3-1270V5
• GPU: Intel Arc A380
• Distro: Arch Linux
• Mesa: mesa-tkg-git
• Kernel: customized tkg 6.7
• Proton: Experimental (Bleeding Edge)

[SraamaR]

Game works fine with Proton Experimental. I've encountered no problems except for the audio chat which hangs the game shortly after being enabled.

[chiefdinkan]

works fine in proton experimental for me in arch (Flatpak steam)

[kisak-valve]

The Finals

Issue transferred from #7405.
@UbuntuGaming posted on 2024-01-13T21:45:05:

Compatibility Report

• Name of the game with compatibility issues:
• Steam AppID of the game: 2073850

System Information

• GPU: AMD Radeon 7800 XT
• Video driver version: Mesa 23.2.1-1ubuntu3.1
• Kernel version: 6.7.0
• Link to full system information report as Gist: https://gist.github.com/UbuntuGaming/1d9c49fa1a0aecf8b0127c1580ed9ab1
• Proton version: Proton Experimental

I confirm:

• [] that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

• Crashes once loaded in game after a few minutes, Sometimes seconds.
• Sometimes crashes on loading in.
• Alt Tab crashes game if loading map.
• Audio lightly crackling.
• Sometimes when it crashes it takes the PC with it. (First game i've seen do this)

-Audio Input/Microphone crashes game (But i don't need this anyway)

steam-2073850.log.zip

Reproduction

Try to play the game on Ubuntu Mantic using Proton Experimental with Ryzen 3600, AMD Radeon 7800 XT.

More Info:

Created this thread as, I'm new (I have no idea if issues go in the same thread or you create new ones) & the issues i'm having seem to be different to everyone elses.

[polluxau]

Experiencing the same as above. Downgrading to Proton 8 makes it launch but shortly freezes thereafter.

Edit: Working workaround is to use UMU-Proton from here by manually installing the runner onto Steam, although an official Proton fix would be very much appreciated as UMU-Proton isn't widely accessible, and most people stick to regular Proton versions or GE.

Can confirm UMU-Proton works

Please be careful with that one as it hasn't been updated in a month so the spam clicking patch is not in it so you get kicked

[itsaerosphere]

Hello @itsaerosphere, can you check if https://gitlab.freedesktop.org/drm/amd/-/issues/3343 is relevant to your system? A quick test would be to reboot into an older kernel and see how the game behaves.

Huh. Looks like version 6.9 of the kernel got released today, which among other things fixes the exact issue I have that's described in the link given. Will report back when I have access to my computer.

EDIT 1: Arch just released Linux 6.9 on GitHub. I expect a version bump on the zen kernel too in a couple of hours. EDIT 2: Looked like the package maintainers would take longer than expected, so I tried the LTS kernel for fun. No dice, it gives me the same error. Looks like I'll have to wait, because I don't want to risk downgrading.

@kisak-valve I ended up fixing the issue by turning on above 4G decoding and rebar. I don't know why I didn't turn it on before but oh well, thanks for your help.

As for the 2.8.0 update, it also crashed on me on startup, but switching to Proton Experimental bleeding edge 8.0 fixed the issue for me, as noted by a helpful post on protondb.

[gofman]

The crash on launch after game update should hopefully be fixed in the just updated Proton Experimental ([bleeding-edge] branch).

[airpods69]

Logs for steam launch: https://filebin.net/cgka44zrnptyyrap

Running Proton Experimental and the game auto closes right after showing "Initializing" on the EAC screen.
Running on an Rx7700XT, Ryzen 7 7700X

I added the kernel parameter clearcpuid=304 but no luck.

Launch command: PROTON_LOG=1 DXVK_FILTER_DEVICE_NAME="AMD ATI Radeon RX 7700 XT / 7800 XT" %command%

[polluxau]

Replying to #7317 (comment)

You dont need to add that kernel parameter anymore or those launch commands

Do you have proton eac runtime installed?

[airpods69]

Do you have proton eac runtime installed?

@polluxau I do, I thought first that it autoinstalls but that isn't the case apparently. So manually installed the runtime, deleted the prefix, restarted steam and the pc and started again. Same results.

[polluxau]

Do you have proton eac runtime installed?

@polluxau I do, I thought first that it autoinstalls but that isn't the case apparently. So manually installed the runtime, deleted the prefix, restarted steam and the pc and started again. Same results.

Hmm that's odd, make sure the game is on a btrfs or ext4 partition, make sure your running a new enough mesa like 24.0.8 or higher and a new enough kernel like 6.8.9 atleast.

What distro are you trying this on? Im on arch with a ryzen 7600, 6700 and the game runs great so i wonder what the problem is, I'll have a look at the log

[airpods69]

make sure the game is on a btrfs or ext4 partition

the game is on an ext4 partition. mesa and the kernel should also be the latest one (I distrohopped yesterday).
I am running void linux.

The logs didn't seem to have anything error worthy atleast when I gave it a look but I could have missed out on something so two pairs of eyes on it would be great

[Blisto91]

Try changing your filter to just be DXVK_FILTER_DEVICE_NAME="7700 XT"

[airpods69]

Try changing your filter to just be DXVK_FILTER_DEVICE_NAME="7700 XT"

Hey there, I tried it. Still the same. I see initialization of anti cheat and then it dies.

[airpods69]

Seems like easy anti cheat does not install when running the script, brawlhalla works without any problems with easy anti cheat and I saw it install EAC for the game but did not see such for finals.

[warealdok]

Seems like easy anti cheat does not install when running the script, brawlhalla works without any problems with easy anti cheat and I saw it install EAC for the game but did not see such for finals.

try to use flatpak steam, eac broken on void
void-linux/void-packages#41388

[JustCauseWhyNot]

Compatibility Report

• Name of the game with compatibility issues: The finals
• Steam AppID of the game: 2073850

System Information

• GPU: RTX 4070s SUPER
• Video driver version: 550.90.07
• Kernel version: 6.9.3
• Link to full system information report as Gist:
• Proton version: 9.0-2, GE-proton-9.7, Proton experiemental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

I'm getting an error has encountered an unexpected error.

It gives me a memory dump

Dumping started...
This OS has outdated debugging utilities, please download an updated version:
https://download.microsoft.com/download/2/1/2/2122BA8F-7EA6-4784-9195-A8CFB7E7388E/StandaloneSDK/Installers/X64%20Debuggers%20And%20Tools-x64_en-us.msi
Code: C0000005
Address: 0000700000000000
RAX: 0000000000000000   RCX: 43e28b05dd7d4d00
RDX: 00000000e0670103   RBX: 00000000c0000001
RSP: 0000000000b9d7b0   RBP: 0000000000b9d840
RSI: 0000000000000000   RDI: 0000000000000000
R8:  43e28b05dd7d4d00   R9:  0000000000000107
R10: ffffffffc0000001   R11: 0000000000000217
R12: 0000000004ef0000   R13: 0000000001840078
R14: 0000000000000000   R15: 0000000000000000
If reporting this error, please include all of the above lines.
Failed.

Reproduction

Launch the finals, and then wait for it to crash.

the steam-2073850.log is to large for me to share. It's 88M. I've got clearcpuid=304 added as well. Here's my cat /proc/cmdline root=PARTUUID=211282f1-3d46-fe46-a898-e0aab6c110c7 ro clearcpuid=304 dokeymap looptype=squashfs loop=/image.squashfs cdroot I've also tried clearcpuid=avx512f, but it also didn't work to disable it. If I disable avx512 in my bios I get a kernel panic on bootup & I don't wanna try and fix it.

[lordcirth]

The game launches for me, but on trying to connect to a match, I get "Kicked from server" with the error code TFGE0025.

[gazben]

Same for me but with different error: TFGE0027

[naorlivne]

Had the same problem with experimental and switching the the bleeding edge branch of it resolved it

[tdljayden]

Replying to #7317 (comment)

Hello, I noticed you are on Gentoo and I just want to say that I am having the same bug as you after trying the same troubleshooting steps. This has been infuriating me for a while now because I have to boot into Windows to play this game. Any luck fixing it?

Btw, I tried the flatpak version and that doesn't work either. Unlike you, I am running an AMD GPU and Wayland and still running into the same issue. My CPU is a 5600x and does not support AVX512, so that cannot be the issue.

[JustCauseWhyNot]

Thats weird. I wonder what the issue is. I'd like to try the finals out. I thought for sure it was an avx512 issue.

[tdljayden]

Thats weird. I wonder what the issue is. I'd like to try the finals out. I thought for sure it was an avx512 issue.

Also, I have checked EAC logs and it says everything is running correctly. I always felt like the issue was that you needed patched glibc but it seems like it may be something proton-specific. I'm thinking it is a hacky workaround that proton uses that may not work on Gentoo, although I did find somebody on discord that got it working on Gentoo at some point but they didn't know what they did to get it working and have since moved on. I find it weird that I can't find any other instance of this error other than your post here.

[tdljayden]

Thats weird. I wonder what the issue is. I'd like to try the finals out. I thought for sure it was an avx512 issue.

UPDATE:

OK, I tried deselecting my customer kernel and instead using the precompiled -bin kernel and now it works. Strange, a certain kernel option is causing a crash on Gentoo...

[JustCauseWhyNot]

Huh. I wish I knew which option.

[tdljayden]

Huh. I wish I knew which option.

I think it may be an address space error as I remember a memory access violation error in the proton log. I wonder if a kernel option is causing wine to read from kernel space instead of user space?

[JustCauseWhyNot]

That's a reasonable guess. I've got no clue.

[gofman]

Huh. I wish I knew which option.

If there are config files for the working and failing kernel version can be found (ideally from the same kernel version with only difference in config) looking at the diff would be a good start.

[gofman]

If there are also custom kernel patches they are also interesting of course.

[tdljayden]

Huh. I wish I knew which option.

If there are config files for the working and failing kernel version can be found (ideally from the same kernel version with only difference in config) looking at the diff would be a good start.

Yes this was my thinking. I just uninstalled the working binary kernel in favour of a compiled kernel without any of my config changes. That also seems to work with the finals. I can create a new savedconfig from the default and then get the diff between that and the old config.

I've done some research into "wine memory access violation" and most of the fixes seem to be to do with using wow64 wine or with mixing 32 bit and 64 bit addresses.

[tdljayden]

In an online discussion about the behaviour of ABIs and wow64 with wine, somebody said they used the following kernel options.

• CONFIG_IA32_EMULATION
• CONFIG_X86_X32_ABI
• CONFIG_COMPAT_32
• CONFIG_COMPAT
• CONFIG_COMPAT_FOR_U64_ALIGNMENT

[tdljayden]

Replying to #7317 (comment)

Also, from your error, I'm fairly sure C0000005 was the same as mine and is to do with memory access violation.

[gofman]

Huh. I wish I knew which option.

If there are config files for the working and failing kernel version can be found (ideally from the same kernel version with only difference in config) looking at the diff would be a good start.

Yes this was my thinking. I just uninstalled the working binary kernel in favour of a compiled kernel without any of my config changes. That also seems to work with the finals. I can create a new savedconfig from the default and then get the diff between that and the old config.

I've done some research into "wine memory access violation" and most of the fixes seem to be to do with using wow64 wine or with mixing 32 bit and 64 bit addresses.

Such a guessing won't lead anywhere. Access violation is consequences, not a core problem. The easiest way (unless someone is going straight educated debug the thing on the failing kernel but this is not easiest) is to see the full difference between kernels, patches and configs.

[tdljayden]

Replying to #7317 (comment)

Yes but I can check if there are any differences in regard to memory management option diffs first as I imagine that to be the likely culprit