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.

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

steam-2073850.log

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.

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

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

Looks like it might be working now.

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

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

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.

@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

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1889795929

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

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1889848407

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

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

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.

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.

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.

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.

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.

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

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?

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.

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

Yeah, if you turn on voice chat game hangs.

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)

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

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

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?

I put together a couple of fixes that got it working on my A750 : https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27057

While I do not get any kind of EAC error anymore,
I am seemingly having server-/connection issues.
The game loads, and I get into the lobby, everything seems stable.
However no matter what mode I try to start (even practice (Shooting-range + Tutorial)) I get this error after, about 20-30 seconds of loading:

Error message: ↓

What I have tried:

various different versions of proton, different connection settings, closing apps/disabling firewalls, internet router configurations. etc. as well as turning off cross-play, trying different regions/languages.

Most of what I tried was based on help I got on the "The Finals" official discord server.
until someone recommended me to inform the proton-devs about the issue.

System Information

gist

The EAC for the finals seems to be fixed now. EOS being installed by Proton-Experimental allows to play - in theory.
Yesterday I played for about an hour, but today the game freezes after a few seconds to minutes. Did not manage to enter a game today, as it freezes latest during server search.

The EAC for the finals seems to be fixed now. EOS being installed by Proton-Experimental allows to play - in theory. Yesterday I played for about an hour, but today the game freezes after a few seconds to minutes. Did not manage to enter a game today, as it freezes latest during server search.

Turn off voice chat.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1890778085

Same issue similar setup but gtx 1070

Turn off voice chat.

Thought, I did that. Will check again. Thanks for the hint.

Edit: that was indeed the issue. Did not manage to disable in game nor did I find a config file. Removing and reinstalling reset the config, though.

one thing i have seen that isnt working correctly is the big displays on the maps arent showing anything that usually will show images of the characters instead it is just black

one thing i have seen that isnt working correctly is the big displays on the maps arent showing anything that usually will show images of the characters instead it is just black

I was wondering what the purpose of those screens are. They do work when there is an event as it shows the current map conditions.

one thing i have seen that isnt working correctly is the big displays on the maps arent showing anything that usually will show images of the characters instead it is just black

I was wondering what the purpose of those screens are. They do work when there is an event as it shows the current map conditions.

Yeah, i think its because those images are going through some proprietary image formats used while the other ones like in game events are just text used in the game engine so no problems there. proton-ge could fix this as they include image formats and codecs that valve doesnt use for legal reasons or valve will fix it with their own translation that they have been working on

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1891633263

Also i was able to get the game to crash after consistently playing after around a hour or so, ill have to grab a proton log sometime i wake back up

Also i was able to get the game to crash after consistently playing after around a 1 hour or so, ill have to grab a proton log sometime i wake back up

Yeah, I'm also getting crashes after playing 1-2 hours.

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.

It could be that clearcpuid=304 won't work correctly on specific systems and distros.

Instead what you might want to do is set clearcpuid=avx512f which is exactly the feature flag that 304 bit points to, but should be more stable.

You can inspect whether the AVX-512 support is enabled by inspecting /proc/cpuinfo which should have no mentions of avx512 flags.

Here's a script that can check it for you, it shouldn't return anything:
cat /proc/cpuinfo | grep avx512 | sort -u

Here are some articles:
https://www.phoronix.com/news/Linux-5.19-Better-clearcpuid
https://www.ibm.com/support/pages/how-disable-cpu-feature-flag-hle-hardware-lock-elision-rhel-x86-intel
https://github.com/torvalds/linux/blob/master/arch/x86/include/asm/cpufeatures.h

Is there any way to disable AVX512 just for the game? I have my system built with -march=x86-64-v4 and it unsurprisingly doesn’t boot with clearcpuid=304

Yeah, I'm also getting crashes after playing 1-2 hours.

Made a proton log with game crash. 2GB uncompressed.
Its a double archive because stupid git doesn't allow to upload 7z and gz is not efficient enough to keep it lower 25MB.
log.7z.gz
System:
Archlinux
Kernel 6.7
Mesa 23.3.3
Proton Experimental
CPU AMD Ryzen 5800x3d
GPU AMD Radeon RX7800XT

Proton Experimental does not run the game at all, including bleeding edge, doesn't even make a prefix itself it seems other than the empty folder for it (and having it created with another proton version and switching back doesn't run it either). Proton 8.0-4 runs the EAC part, seeing the console and the splash screen, but after that, nothing opens and have to force close. The Proton 8.0-5 release candidate and GE-Proton 8-27 does get me in-game, but I get this screen then closes itself:

I have the EAC runtime installed, it does nothing. I had it close on connecting like what everyone with an AVX512 CPU does, but I don't have such a new CPU, do I don't know why it happens on my end.
With Proton GE 8-27, the game didn't crash and let me create an account, but after that its that screen.

System:
Distro: Manjaro
Kernel: 6.6.8-2
CPU: AMD Ryzen 2700X
GPU: AMD Radeon 6800 (Mesa 23.1.9)

Thanks for pointing me in the right direction kisak, it looks like the issue I'm running into is identical to what @learning-thing is seeing. After reporting, I tried installing the game using the flatpak version of steam, and got the same error. It's probably worth mentioning that I have run into several other people seeing the same error, and Arch seems to be the one thing we all have in common.

@dizeeee I play on Arch under kde-unstable with no issues besides the occasional crashes, I doubt your choice of distro would affect that. Have you deleted your prefix before running?

@sevmonster I have several times. Just to be clear, it's the folder in compatdata with the matching app id right?

Just to be clear, it's the folder in compatdata with the matching app id right?

Yes it is.

Turns out my error was not Proton related. If you have Star Citizen installed, it adds an EAC workaround to /etc/hosts. Removing this line fixes the bug: 127.0.0.1 modules-cdn.eac-prod.on.epicgames.com

@SopaDeMacaco-UmaDelicia Thank you for the log! Amazingly, it seems to give a hint at what is wrong. Could you first check the output of cat /proc/sys/vm/max_map_count? We are guessing that it will be some "low" default like ~65000. It would be nice to confirm that before increasing the number (and please let me know if it is a much larger number). After checking that, I would advise for anyone who is running into crashes after 1-2 hours to increase the value of max_map_count to something higher like 2147483642.

@SopaDeMacaco-UmaDelicia Thank you for the log! Amazingly, it seems to give a hint at what is wrong. Could you first check the output of cat /proc/sys/vm/max_map_count? We are guessing that it will be some "low" default like ~65000. It would be nice to confirm that before increasing the number (and please let me know if it is a much larger number). After checking that, I would advise for anyone who is running into crashes after 1-2 hours to increase the value of max_map_count to something higher like 2147483642.

For me on arch it is 65530, i shall increase this to see if crashes go away

@SopaDeMacaco-UmaDelicia Thank you for the log! Amazingly, it seems to give a hint at what is wrong. Could you first check the output of cat /proc/sys/vm/max_map_count? We are guessing that it will be some "low" default like ~65000. It would be nice to confirm that before increasing the number (and please let me know if it is a much larger number). After checking that, I would advise for anyone who is running into crashes after 1-2 hours to increase the value of max_map_count to something higher like 2147483642.

Indeed, cat /proc/sys/vm/max_map_count shows 65530

The game is crashing for me 10-20 seconds after arriving in the main menu if I add PROTON_ENABLE_NVAPI=1 to my launch options. The game runs fine without it, but then I'm stuck with FSR2 instead of DLSS.
steam-2073850.log.tar.gz

well it seems voice chat is working now well at least its not causing the game to crash on proton experimental bleeding edge
can someone confirm this

I would advise for anyone who is running into crashes after 1-2 hours to increase the value of max_map_count to something higher like 2147483642.

well it seems voice chat is working now well at least its not causing the game to crash on proton experimental bleeding edge can someone confirm this

Will confirm both later today.

well it seems voice chat is working now well at least its not causing the game to crash on proton experimental bleeding edge can someone confirm this

Not really, just came from #6602 (how stupid im)

"
Just tried it, didn't work. It just hung up after the game launched into the main menu after a few seconds, using LCD Deck+Newest Stable Steam OS+Proton, tried dx11 startup parameter, Proton Experiment/Disable Compatibility tools; didn't work

EAC→Login→Main menu→Some second later-hung→Also sometimes later hung-popup→Clicked the ok button→Back to Steam's menu
"

I didn't played it before, therefore the default settings applied to my game, by default the vc are on, and in my case it just crash the game (knows the vc may cause issue, but didn't really thought the default game settings)

We uploaded a build to Proton Hotfix that has the fix for the voice chat crash, so you can select that for The Finals instead of experimental-bleeding-edge if you want. The crash on CPUs with AVX-512 support is still around, so if you are getting a crash quickly after the game window opens, please try the clearcpuid=304 workaround.

EAC→Login→Main menu→Some second later-hung→Also sometimes later hung-popup→Clicked the ok button→Back to Steam's menu

Had same issue after 1.5.0 update

We uploaded a build to Proton Hotfix that has the fix for the voice chat crash, so you can select that for The Finals instead of experimental-bleeding-edge if you want.

Switching to Proton Hotfix in game properties works, rm -r ..../SteamLibrary/steamapps/compatdata/2073850/ was needed.

@alasky17, you guys are awesome

Hello, for me the game works fine on a specific session of my computer but crashes in the main menu when I launch the game on another session of my computer. Odd. How can I get logs to check the problem?

Hello, for me the game works fine on a specific session of my computer but crashes in the main menu when I launch the game on another session of my computer. Odd. How can I get logs to check the problem?

In Steam, right-click on the game and go to Properties. There you can add PROTON_LOG=1 %command% to your launch options. The file will be created in your $HOME directory (or at least for me it is).

On another note: So it crashes in the main menu, you say? Are you on Nvidia and are you using DLSS? Because that is what's happening to me. The game runs fine unless I add PROTON_ENABLE_NVAPI=1 to my launch options. In that case it crashes 10-20 seconds after I arrive in the main menu.
I've attached my log file in a previous comment.

Is there any way you can remove the below recomended specs GPU warning when starting the game on Steam Deck? Could proton surpress this warning or is this something the devs would need to add an exception for?

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1898208603

I'm on AMD and the game works on another session so I think it's because of my session's config but I dont know why. I will try with proton logs later

Will confirm both later today.

So far I have had zero crashes with higher vm.max_map_count and voice chat enabled on Proton Hotfix. I didn't clear my prefix before switching from Experimental.

I just tested this with another stranger yes
audio chat works on the finals at least with proton experimental bleeding edge

Hello all I seem to be having an issue where playing crossplay with another person on Xbox does not allow either of us to join each other. I'm able to play by myself just fine. Is anyone else having this issue? Using proton experimental bleeding edge.

Hello all I seem to be having an issue where playing crossplay with another person on Xbox does not allow either of us to join each other. I'm able to play by myself just fine. Is anyone else having this issue? Using proton experimental bleeding edge.

Make sure both you and your friend have cross play enabled. I had the same issue.

So, I'm using a GTX1050TI and the game could run better, let's say... but I sense some performance issue from the game, am I correct?

Another Linux player said that the game was running poorly, but I've heard reports of bad optimization of the game.

This is not even a surprise, but I just want to make sure, because the game runs at almost 60FPS but it feels more like 25FPS or something like that.

I often get error when game starts loading into match:
Wine C++ Runtime Library

Assertion failed!

But after restart everything usually works.

(in my case cat /proc/sys/vm/max_map_count gives 2147483642)

EDIT:
My spec: Ryzen 7 6800HS, 16GB RAM, Nvidia RTX 3050Ti. Pop!_OS 22.04
Asus ROG Flow X13

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1902666656

Same here, you on nvidia, amd or intel?

Haven't been able to get past the EAC initializing screen despite having the EAC runtime installed. After displaying a black cmd window, it appears to get stuck forever.

Currently on Fedora Kinoite 39, Steam Flatpak, Proton Hotfix, Ryzen 5 2600, RX 6750 XT. Have tried setting SDL_VIDEODRIVER=windows as a launch option as suggested here (comment) with no success.

steam-2073850.log

Edit: Looks like I had some kernel parameter that was preventing EAC from doing its thing. Also checked Brawlhalla to make sure it wasn't just The Finals, and sure enough that also wasn't working. Fixed.

I have no idea what you guys did but the latest Proton Hotfix update fixed almost every framerate issue!
Now randomly the game, at every explosion, lags like hell or not, it depends on sheer luck, but for the rest, it's running much better now!

My game was fine for a few days, as of yesterday the audio has started crackling. Currently investigating.

i9-9900K, RX 6800 XT, 32GB RAM, Arch Linux (6.7.0-zen3-1-zen x86_64) on i3wm

Running with Proton Experimental.
The game gets past the EAC window for me but after a couple of seconds of a black screen I get a bunch of these popups and I have to kill the game.

Running the game with the -dx11 launch option works although I feel like the performance is less than ideal with it.

I did the

cat /proc/sys/vm/max_map_count

and I get 524288

I played 5 quick cash grabs and no problem.

Specs are:

I tried replicating the EAC but after 1.4.1 I have never had it before. I was having the Out of memory issue but in 1.5.1 I can no longer replicate the issue. All cases were tested with Proton Experiemental as shown at https://www.youtube.com/@xtremelinux

I got no problem in changing the max_map_count or any other parameter to create a scenario where the problem shows time and time again, mainly that Assertion Failed I am reading here.

With Update 1.5.5, mesa 23.3.4, proton experimental(bleeding edge) the frame timing and fps is no longer stuttery, almost buttery smooth and my fps has gone up by about 5fps so thats also good.

The finals ads images in maps are kinda showing up properly now but still a bit wonky

trying to install it on my desktop with a 3070, dual monitors, VRR, wayland, up-to-date from arch repos and having some weird issues. Primarily I'm getting the hanging issue on initial boot most reported in #6602 (with a few mentions here) but occasionally it will instead crash with an out of video memory error. Sometimes it will get to the photosensitivity warning instead of a black screen as well.

(transcribed for search engine indexing)
Out of video memory trying to allocate a rendering resource. Make sure your video card has the minimum required memory, try lowering the resolution and/or closing other applications that are running. Exiting...

I've viewed with nvtop and the VRAM never even looks like it's trying to be used. (no noticable rise) I've deleted the compatdata prefix (speaking of which it is still unfathomably annoying that Steam doesn't name them using the game name and instead uses the ID, I mean you could at least make a folder of named symlinks or something right? Anyway, I digress) and tried hotfix proton, GE proton, proton 8.5, etc. (deleting the prefix each time I switch) with no obvious change in results.

Not sure where to even go from here to be honest since from what I can tell everyone else has moved on from this error and it's not affecting anyone anymore.

edit : I went back around re-reading and it might be the clearcpuid=304 issue, but that's always just been mentioned as a general crash rather than the hang so I'm not sure. Speaking of which, what does that actually do to the system?

edit 2 :
steam-2073850.log

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1913396642

Post a proton log, i dont get this because im running amd

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1913396642)

Post a proton log, i dont get this because im running amd

added, I also tried clearcpuid=304 thinking that maybe the crash people talked about it fixing was the hang but no luck.

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1913396642)

Post a proton log, i dont get this because im running amd

added, I also tried clearcpuid=304 thinking that maybe the crash people talked about it fixing was the hang but no luck.

Well thats if your cpu supports avx 512

Have you increased your max_map_count on the distro you're using?

To increase it do this

Sudo nano /etc/sysctl.d/vm.max_map_count.conf

add

vm.max_map_count=2147483642

add

vm.max_map_count=2147483642

adding that doesn't seem to change anything

edit : I read through all of the hidden replies as well and found a mention of using the -dx11 flag which half solved it. It says that an unauthorized tool was detected running on the system (briefly) then it cuts to the age menu that has you type in your birthdate, and a few seconds later it crashes. (no pop up) In other words it seems like I'm being hit with all the issues that should already be solved since I'm now facing (what I assume is) the silent crash after a couple seconds on the main menu despite having already applied all of the fixes for that in trying to fix the previous issue.

@TheOverpassArsonist
I had that out of video memory crash once on my RTX 3080 when i tried to boot the game without PROTON_ENABLE_NVAPI=1 %command% , but since i added that back i haven't seen this issue. So maybe try that if you haven't yet, but might ofc be completely different issue.

@TheOverpassArsonist I had that out of video memory crash once on my RTX 3080 when i tried to boot the game without PROTON_ENABLE_NVAPI=1 %command% , but since i added that back i haven't seen this issue. So maybe try that if you haven't yet, but might ofc be completely different issue.

I'll have to try again now that I have a known way to get it working but I think PROTON-ENABLE_NVAPI is one of the things I tried and it didn't work, adding -dx11 is what did it for me. Based on the performance I'm guessing that's a sub-optimal patch rather than a real solution, but it worked good enough. (I got into the closed beta when I was back on windows for a bit due to technical issues and on the same exact hardware it ran way better, at least if my memory is right) The other issue with it detecting some 'unauthorized tool' is it's overspecific way of saying "EAC isn't happy with you" which was because it got reset to proton-GE at some point and proton-GE isn't EAC compatible. Switching to proton hotfix, deleting the prefix, etc. did fix it and make it playable, albiet it still ran poorly and had some weird glitches. (again, I'm guessing that those will be ironed out with time and they're not game breaking by any means. They could also be general performance regressions across all platforms, but it's way worse than I remember it being during the closed beta so it would have had to regress massively if that's the case)

Game used to run fine for me last week, hadn't played for a while but now there's just a black screen. After a while I can hear the lobby audio and randomly click, but it stays on a black screen. I'm using Proton Hotfix to run the game.

Edit: Trying to use DX11 using -d3d11 commandline parameter just crashes the game after few seconds of black screen

System info and runtime diagnostics: link
Proton log: steam-2073850.log
Proton log with -d3d11: steam-2073850.log

@kisak-valve Indeed, I did not have the 32-bit libraries for the NVIDIA driver. Installed it, made sure all were the same version and regenerated initramfs just in case. Black screen with audio after a few seconds when run without commandline parameters and a crash with -d3d11. Once again, running with Proton Hotfix. Also Palworld and NieR Replicant runs fine for me, issue only happens with the finals.

Proton log: steam-2073850.log
Proton log with -d3d11: steam-2073850.log
Updated runtime diagnostics: link

my game is crashing or dinnect me from the server when i start a match, that started to happen with the update, does anyone have this issue?

my game is crashing or dinnect me from the server when i start a match, that started to happen with the update, does anyone have this issue?

Not with crashing, but when i restarted my game once i was getting the disconnect when finding a game but restarting again fixed it.

Also it seems cpu usage has gone up by about 10% with this new 1.6 update, my cpu 3700x sits around 80 to 85% now when before it was sitting at 60% to 70%

So in return i get lower fps as im bottlenecked by my cpu

Id like to report recently installing
mesa 24.1 git and using proton experimental bleeding edge the majority of frame timing issues are gone and i got a nice boost in fps that now puts it on par with windows

These patches from mesa might be in 24 aswell but unsure of what patches i would be looking for but im guessing vkd3d-proton patches also improved performance & stability with the frame rate

Before 86fps max, 40fps lowest, 65fps average
After 105fps max, 50fps lowest, 83fps average :D

idk if this happens on amd and nvidia but under amd on latest mesa and proton using the cl-40 grenade launcher under medium class, the grenades when they hit the ground make the frame timing stutter everytime

same goes with mgl32 on heavy, grenades, rpgs, explosive mines
thing is it doesnt happen in training only in a match

edit: no longer happens on latest proton experimental(bleeding edge)

Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:3000 di:b9ed18
Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:4000 di:b9ed18
Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
[Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:5c di:b9ed18
Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[260841] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
warn_bad_vsyscall: 4 callbacks suppressed
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:3000 di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:4000 di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:5c di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18
Discovery.exe[270558] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:17079208c cs:33 sp:b9d8c8 ax:b9ecc0 si:d4ce40 di:b9ed18

What even.

Please oh please oh please fix the sensitivity being too low. This has been an issue since back 4 blood.

Please oh please oh please fix the sensitivity being too low. This has been an issue since back 4 blood.

Wdym? Are you running x11 or wayland?

Please oh please oh please fix the sensitivity being too low. This has been an issue since back 4 blood.

Wdym? Are you running x11 or wayland?

X11. Only proton-ge with its raw input patch will allow the sensitivity to get to a playable level. Otherwise is it too slow.

Please oh please oh please fix the sensitivity being too low. This has been an issue since back 4 blood.

Wdym? Are you running x11 or wayland?

X11. Only proton-ge with its raw input patch will allow the sensitivity to get to a playable level. Otherwise is it too slow.

I thought i felt a difference with proton-ge when it came to mouse input lol

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1890778085

Update

I would like to update this.
I moved to Debian 13 (Trixie/Testing) to see if it was the same on Debian
with the system default mesa installed (around 20 days ago) It would crash after few minutes (The same a Ubuntu) but with no Xorg crash, locks up for a few minutes instead.

After switching to mesa-devel (using VK_ICD_FILENAMES %command%) i haven't had a single crash.

Issues fixed by using mesa-devel (At the time it was on the way to being the 24.0 release):

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

Issues Left:

• Audio lightly crackling.

Other issues already mentioned, That i didn't notice at the time:

• The event boards around the map

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1951207954

id check your vm max map count for the crashing as the game likes to go over the default max map count on most distros and try running proton experimental (bleeding edge) or latest proton-ge as he also ships the latest experimental(bleeding edge)

Sudo nano /etc/sysctl.d/vm.max_map_count.conf

mine is

vm.max_map_count=2147483642

its normally like 6k or something which is too low for lots of windows games

i havent experiened alt tab crashes while loading, probs because i run kde plasma

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1951221263

Thanks for the tip🙂
I also use KDE, It is the best desktop environment
I already had this set on Ubuntu as i tried to install star citizen & i carried all the tweaks i made over to Debian

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1951225529

Do you have any swap memory being used? As i remember when i was using endeavor os and didnt set any swap at install it would crash, as my memory would get filled up, then the desktop would crash also lol

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1951231135

I have no swap at all, But i monitor my memory closely, When i get near 32GB, i'm buying 64GB. The most I've used so far is 24.5GB while trying to max my memory out lol

The problem was somewhere here: Either the system-mesa version, a dependency of system-mesa Or the toolchain system-mesa was built with (unlikely but possible) i built it using LLVM-17 with native-file. It works perfectly now.
I haven't gone as far as fully figuring out what actually caused the issues.

RX6600 - Steam Flatpak proton experimental

with latest proton-ge and testing latest proton experimental(bleeding edge), mesa 24, kernel 6.7.5

the only frame stutter i get is with a glitch grenade, frag grenade, flash grenade, cl40, rpg-7, mgl32
thing is these "stutters" only happen when those animations happen right in front of me, i shoot a rpg-7 far away it doesnt happen, same with grenade or flash grenade etc

id like to see if anyone else gets these frame stutters when firing grenades etc right in front of them either it be nvidia, amd, intel

frame stutter example

edit: decided to install my rtx 2060 and their is no stutters with these explosions, grenades or anything for that matter.
so either its a mesa issue or a vkd3d-proton issue

Edit again: fresh install, dont experience those frame stutters in game atleast i dont think, for now lol, also setting my amd gpu power profile to 3d_full_screen made my game feel a lot more responsive and smoother in game, used lact to switch the power profile

Please oh please oh please fix the sensitivity being too low. This has been an issue since back 4 blood.

Wdym? Are you running x11 or wayland?

X11. Only proton-ge with its raw input patch will allow the sensitivity to get to a playable level. Otherwise is it too slow.

are you running nvidia by any chance? as i just tried my rtx 2060 and noticed a big latency issue with my mouse

Please oh please oh please fix the sensitivity being too low. This has been an issue since back 4 blood.

Wdym? Are you running x11 or wayland?

X11. Only proton-ge with its raw input patch will allow the sensitivity to get to a playable level. Otherwise is it too slow.

are you running nvidia by any chance? as i just tried my rtx 2060 and noticed a big latency issue with my mouse

nvidia 3070

I think the finals broke compatibility on arch systems in 1.9.0 as using system steam under endeavour os with latest packages installed, the game will fail to join a match
Says like (server not responding)

if i use flatpak steam there is no issue joining a match

edit: nevermind it is working again lol

the game has been working perfectly for five days straight but all of a sudden out of nowhere

I don't know why this is happening now

It could be the system wide EasyAntiCheat that I needed to add to my system to get

Fall Guys (tm) to work

(I went through a whole ordeal with the Heroic Games Launcher)

I really hope that's not the issue because I want to be able to run both games

& not have to choose one or the other

i think its got to do with the finals own server side anticheat they use, if i switch proton versions too much that will happen, ill have to verify my in game files or restart my pc for that issue to not appear again

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1962797406

i think its got to do with the finals own server side anticheat they use, if i switch proton versions too much that will happen, ill have to verify my in game files or restart my pc for that issue to not appear again

Performance in general for this game is bad. It just dips randomly from 90+ down to 70

Performance in general for this game is bad. It just dips randomly from 90+ down to 70

mostly because of the destruction and that the game is very cpu dependent

i remember the open beta was way better, i was getting around 120fps under a rx 6700, ryzen 3700x but embark was having issues running it at that speed as it was crashing frequently so when the game fully released it got reduced and so the performance isnt that great.

the game still crashes on windows from a angel script error with the unreal engine so atleast that doesnt occur under proton

The game is crashing for me 10-20 seconds after arriving in the main menu if I add PROTON_ENABLE_NVAPI=1 to my launch options. The game runs fine without it, but then I'm stuck with FSR2 instead of DLSS. steam-2073850.log.tar.gz

@Zenzi0 (and anyone else who was getting crashes with PROTON_ENABLE_NVAPI=1) Could you retry this with Proton 9.0-beta and see if you are still getting a crash with PROTON_ENABLE_NVAPI=1? Folks are reporting that this is no longer an issue for them and we are trying to determine if it is safe to remove the override disabling NVAPI.

I didn't crash before either, but reporting anyway. Played 1 match and around 10 min in Practice range with no crashes to report with DLSS set to Quality.
Had to use PROTON_FORCE_NVAPI=1 to see the DLSS options though, with proton-experimental (9.0)
Ryzen 5800X3D, RTX 3080, 550.54.14 drivers

@alasky17 Sadly it doesn't seem to be better with Proton 9.0-beta. With Proton Experimental I had managed to enable DLSS and not crash with these launch options (and only these, any random option more and it would crash): PROTON_ENABLE_NVAPI=1 gamemoderun %command%
But when I went back today to check 9.0-beta for you I noticed I had FSR2 set in game options again. Maybe this happened when I switched to Proton-GE for a bit.
Anyway, it worked in the past with the launch options mentioned above but doesn't work right now (Proton Experimental or Proton 9.0-beta). Proton Experimental doesn't even give me DLSS as an option but runs fine otherwise. Proton 9.0-beta freezes as soon as I try to switch to DLSS. I tried clean prefixes by deleting the 2073850 folder. The log is for Proton 9.0-beta.
steam-2073850.log.tar.gz

Arch 6.7.6-zen1-zen
Nvidia 3080ti Driver version 545.29.06 (550 should be out of testing soon)

Edit: I didn't realize Proton Experimental was updated to 9.0 now. Maybe that's when DLSS broke for me again and got automatically set to FSR2.

Edit: Thanks to xpander69's comment below I am now aware that the launch option for DLSS in Proton 9.0 has changed. I didn't notice the change before that. Really, is there some better way to keep up with something like this than just having a look at what people are using on ProtonDB? That's what I've been doing.

Edit: I didn't realize Proton Experimental was updated to 9.0 now. Maybe that's when DLSS broke for me again and got automatically set to FSR2.

With proton-experimental (9.0) you need PROTON_FORCE_NVAPI=1 to see the DLSS option again in the game settings.

@xpander69 Thank you so much. That fixed it for me. I didn't notice it before and it's the first time I've heard about this change.
Is there a good way to keep up with which launch options are necessary/useful? It seems to me just having a look at ProtonDB isn't the best way, since a lot of the launch options mentioned there seem outdated.

@Zenzi0 Generally, the readme which shows up on https://github.com/ValveSoftware/Proton/ should have all the current ones. The default hasn't switched over from 8.0 to 9.0, so https://github.com/ValveSoftware/Proton/tree/proton_9.0 has the launch options for 9.0, and you can toggle the branches to see the launch options for the different Proton versions. PROTON_FORCE_NVAPI=1 isn't on there which might have been an oversight, and it is on my list to investigate and potentially add, but PROTON_DISABLE_NVAPI is there, replacing PROTON_ENABLE_NVAPI now that the default has changed, as you can see if you flip between the 8.0 and 9.0 branches.

Just to confirm, it sounds like enabling NVAPI is now working for you without issue on 9.0-x, and so we should remove the override to disable nvapi for The Finals. The crash you were seeing initially yesterday is apparently actually a problem with XeSS and should be fixed in bleeding-edge.

@alasky17 Yes, it is working without issue.

Game was working fine for me (with occasional crash) under Proton 8.0-5 up until two days ago.

game now starts to load.
it will go through processing the vulkan shaders
the first loading window and the EAC pops up
the second loading window pop up

and then..... it just stops.

no error message, nothing. Im just back to the steam client.

I looked at my logs from trying to start the game, and they were very, very, very long. this was the tail of the log file. The first portion of this repeats a few thousand times (why I only threw tail in here for now).

89320.017:0254:03c4:trace:unwind:execute_cfa_instructions 7f3092d26845: DW_CFA_undefined %rip
89320.017:0254:03c4:trace:unwind:dwarf_virtual_unwind next function rip=00007f3092d26850
89320.017:0254:03c4:trace:unwind:dwarf_virtual_unwind   rax=0000000000000000 rbx=00000001000ff820 rcx=0000000000000002 rdx=0000000000000000
89320.017:0254:03c4:trace:unwind:dwarf_virtual_unwind   rsi=0000000000000000 rdi=00005555574b5800 rbp=0000000000000000 rsp=000000010f676000
89320.017:0254:03c4:trace:unwind:dwarf_virtual_unwind    r8=0000000000000000  r9=0000000000000000 r10=00007f30892eaba0 r11=000000000000000b
89320.017:0254:03c4:trace:unwind:dwarf_virtual_unwind   r12=000000010f54f640 r13=0000000000000002 r14=00007f3092c947d0 r15=00000001000ff980
89320.017:0254:03c4:trace:unwind:dwarf_virtual_unwind function 7f3092d26850 base 0x7f3092d26845 cie 0x7f3092deaf20 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
89320.017:0254:03c4:warn:seh:dwarf_virtual_unwind backtrace: 0x7f3092d26850: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x126850.
89320.017:0254:03c4:trace:unwind:execute_cfa_instructions 7f3092d26845: DW_CFA_def_cfa %rsp, 8
89320.017:0254:03c4:trace:unwind:execute_cfa_instructions 7f3092d26845: DW_CFA_offset %rip, -8
89320.017:0254:03c4:trace:unwind:dwarf_virtual_unwind fde 0x7f3092e035e0 len 10 personality (nil) lsda (nil) code 7f3092d26845-7f3092d2685a
89320.072:00e4:0428:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
89320.091:0030:042c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
89320.092:0030:0430:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
89320.093:0030:0434:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
89320.093:0030:0438:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
89320.093:0030:043c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 175256 != 175255, skipping destruction (fork without exec?)

running on a system with a 3070 Ti, NVIDIA drivers 545.29.06. running Linux kernel 6.5.6-76060506-generic

Any thoughts?

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1967849435

Have you tested other proton versions like proton 9 beta? These have patches for the finals

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1967849435

Have you tested other proton versions like proton 9 beta? These have patches for the finals

Yes. My apologies. I forgot to say I've tried experimental, 9 beta, hot fix and 7. Same with all except hot fix, which just freezes and I have to kill the process.

Big displays shows a green pixelated texture instead of the video. Videos of in-game events like Alien Invasion, Meteors are showed correctly.
Tested with Experimental and Proton GE 8-32

Is the AVX512 issue something that can be reasonably fixed on Proton's side in the near future? I'd rather not disable support for it system-wide...

Game works for me but it crashes every time after exactly one hour. And I really mean exactly one hour, I start a timer when launching the game and can tell down to the minute when it will crash.
Then a crash report handler opens and offers making a memory dump, but when I do it it fails with Internal error #4: C0000210.

The log file is a tar.xz inside a tar.gz because otherwise it would be too large for GitHub and they don't accept xz files
steam-2073850.log.tar.xz.tar.gz

Edit: After posting this I noticed I had not loaded all comments in this thread and others reported the same issue already. I will have to try increasing /proc/sys/vm/max_map_count

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1974063361

Yes, increasing the vm max map count fixes this issue, most distros have this up high enough that the finals wont crash and other games that require it higher then default but for some like arch, opensuse, maybe some ubuntu distros it wont be high enough.

Its why the steamdeck has it super high by default

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1969932515

Yeah this seems to be something to do with how these images are being translated through steams own codec stuff, usually glorious eggroll can fix these things as he includes extra codecs for images and videos that valve cant include for legal reasons but he hasnt updated proton-ge yet so we will have to wait and see

Its odd as the training images work perfectly but not the in game ones, so i wonder what's happening that causes it to be like that

one issue iv encountered on plasma 6 with the finals is when you enter your first match, trying to aim is completely messed up and you have to tab out and tab back in a couple times till you can aim normally again

this charm has images being displayed on it but its not being displayed correctly, similar to the other big images that get displayed on the maps with the wrong colors aswell

@polluxau Could you see if adding WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command% as a launch option fixes the rendering colors?

@polluxau Could you see if adding WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command% as a launch option fixes the rendering colors?

for me the game crashes when entering a match or customizing my character with that launch command, but i asked a friend to try it and he gets black images on seoul and monaco

im running arch with 6.8 kernel and mesa 24, the friend is running opensuse tumbleweed with 6.7.9 mesa 23.3
both running proton experimental

edit: interesting for a split second when rejoining a match the lcd screens worked but then instantly goes back to the weird pink colors

edit again : i tried flatpak steam and the game doesnt crash with WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command% im getting the same result where the image is black

dont know why the game crashes under system steam with this launch command but doesnt under flatpak, weird.

@polluxau Thank you for testing that! The results neither entirely confirm nor deny my suspicion. Looks like more work is needed :)

New problem here:

my mouse keeps going up and can't move it down:

Here is a video:

https://github.com/ValveSoftware/Proton/assets/20603088/b5a9532a-9c03-4920-b482-a862d433d18d

I tried Proton 9 (beta), Proton Hotfix and also Proton GE even clearing the compactdata folder but same result

New problem here:

my mouse keeps going up and can't move it down:

Here is a video:
2024-03-24.21-01-08.mp4

I tried Proton 9 (beta), Proton Hotfix and also Proton GE even clearing the compactdata folder but same result

Wow, I though I messed up my compatdata, I have the same issue, which I fixed radically by going wayland native mode with proton-tkg(version based on fresh wine).

New problem here:
my mouse keeps going up and can't move it down:
Here is a video:
2024-03-24.21-01-08.mp4
I tried Proton 9 (beta), Proton Hotfix and also Proton GE even clearing the compactdata folder but same result

Wow, I though I messed up my compatdata, I have the same issue, which I fixed radically by going wayland native mode with proton-tkg(version based on fresh wine).

Where I can find proton-tkg? I was only able to find really old versions. And also, going wayland native mode require some commands or is default in proton-tkg?

Where I can find proton-tkg? I was only able to find really old versions. And also, going wayland native mode require some commands or is default in proton-tkg?

THIS IS BY NO MEANS A CORRECT SOLUTION, I JUST PREFER WAYLAND AND THIS SEEMS TO FIX MY EXPERIENCE.

Proton-tkg

How to install it you can read on the main page. To enable wayland you gotta add a registry key.
WINEPREFIX=/home/[YOURUSERNAME]/.steam/root/steamapps/compatdata/[YOURAPPID]/pfx/ regedit
Add string value "Graphics"="x11,wayland" on the path [HKEY_CURRENT_USER\Software\Wine\Drivers]. I would also suggest to set a correct dpi if you use scaling.
WINEPREFIX=/home/[YOURUSERNAME]/.steam/root/steamapps/compatdata/[YOURAPPID]/pfx/ winecfg In my case on 4k monitor I went from 96 to 192.

Add DISPLAY= %command% to the launch options.

I use version g435e0141 it works fine for me, I did not try newer versions.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2016941829

I did this with the latest build available of tgk and works well. Probably got even more performance due to wayland. Hope this will get fixed for everybody without doing all this thinkering.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2016929474

Iv had this bug, and that native Wayland under wine couldnt come sooner lol

I think this might be solved in plasma 6.0.3 as they fixed a mouse snapping issue in games under xwayland, will wait and see

i see with latest proton experimental, the images now work, thank you proton devs as always :)
and with plasma 6.0.3 the mouse no longer locks up which is also good

Also you don't need to disable avx 512 anymore!

Hello, The Finals keeps crashing for me randomly mid-game. I have already tried the advice from https://www.reddit.com/r/linux_gaming/comments/194yurj/how_to_play_the_finals_on_linux/ (i.e. PROTON_ENABLE_NVAPI=1 or PROTON_FORCE_NVAPI=1, gamemoderun, clearcpuid=304, using the lowest settings, trying both DLSS and XeSS) and also setting vm.max_map_count high. I have also tried various Proton versions (Proton Experimental bleeding edge, Proton 9.0 Beta, Proton Hotfix). I am using X11 on Ubuntu 22.04. I suppose my Mesa version is Mesa 23.2.1-1ubuntu3.1~22.04.2 (LLVM 15.0.7) (taken from vulkaninfo --summary. My GPU is an NVIDIA RTX 3060, using the 550 driver. If required, I can also share my Proton Log. Thank you in advance for any help!

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2027674402

Ok well for one use proton experimental (bleeding edge) for the latest patches from proton, that will give you the best compatibility for your hardware.

1. Mesa version doesnt matter on nvidia as your using the proprietary nvidia drivers

3.vm max map count fixes a wine crash that happens after a 1 hour or 2 of playing the game

4.make sure you have gamemode installed so that you can use that launch command

1. The clearcpuid isnt needed anymore aswell

So with that verify your game files

Set your launch commands to this

PROTON_ENABLE_NVAPI=1 gamemoderun %command%

And use proton experimental (bleeding edge)

If you still experience a crash post proton log

It can also be that since you're using ubuntu 22.04 the experience when playing games might not be the best as older packages are being used.

Something like a newer version of ubuntu might help with this

I can confirm that it now works for me (and it didn't before).
CPU: AMD Ryzen 7 7800X3D
Distro: Manjaro

The crash on systems with AVX512 support have now been fixed in Proton Experimental so anyone who have disabled it to work around the issue can revert it again.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2027679392

Hello, first of all, thank you for the quick answer! I tried it by following your steps, but it still crashed. You can find my log here (it's too big to upload on Github - lemme know if you want me to upload it elsewhere.)

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2016941829

I'm getting kicked with this version with the new update, and Plasma 6.0.3 isn't out yet :(

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2028026867

Verify your game files, this will usually happen when proton gets updated, it will keep disconnecting you until you verify or switch back to another proton version

Plasma 6.0.3 is out in extra-testing on arch repos so that's how i was able to test it out

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2028030127

Plasma 6.0.3 is out now in manjaro unstable ^^ and arch stable too

when will this get changed?
everything seems mostly fixed, do you have to wait for those patches to arrive in proton stable? or something else?

New problem here:

my mouse keeps going up and can't move it down:

Here is a video:
2024-03-24.21-01-08.mp4

I tried Proton 9 (beta), Proton Hotfix and also Proton GE even clearing the compactdata folder but same result

Are you using gamescope? This sounds like this bug, which was fixed by this commit.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2028955790

It was also a plasma 6 wayland bug

https://bugs.kde.org/show_bug.cgi?id=458233

It was fixed in 6.0.3

Compatibility Report

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

System Information

• GPU: AMD Radeon 7900 XTX
• GPU: Intel UHD Graphics 770
• Video driver version: mesa-dri-drivers 23.3.6, mesa-vulkan-drivers 24.1.0
• • Via Steam System Information: Driver Version: 4.6 (Compatibility Profile) Mesa 23.3.6
• Kernel version: 6.7.6-201.fsync.fc39.x86_64
• CPU: i7-12700k
• OS: Nobara 39
• DE: KDE Plasma 6.0.3
• Compositor: Wayland
• Proton version: Experimental, GE-Proton, 9 Beta

I confirm:

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

Symptoms:

Game defaults to using the iGPU instead of the dGPU unless the iGPU is disabled in BIOS.
Haven't seen this behavior in any other game that I am aware of.
Already filed a bug report with development team.
Current game version is 2.2.0.
Game will load entirely on the iGPU and will not deliver any work to the dGPU resulting in graphical corruption and artifacting plus framerates of approximately 5 fps.
"Graphical corruption and artifacting" in this case meaning that the model on initial menu load will show clipping and wrong animations. Plus any cutscenes or similar content will run slowly though the sound will be unaffected.

Troubleshooting/Alternate Proton Versions:

Unable to start game with a version of Proton lower than 9 - displays a fatal error that the game is only compatible with Win10 or later and closes.
Issue present on Experimental, 9 Beta, and GE-Proton.

Reproduction:

Start game with an iGPU and dGPU enabled and present in the same system.
Game will load entirely on the iGPU and will deliver framerates of approximately 5fps, plus game will respond slowly to inputs.

steam-2073850.zip

UPDATE - SOLUTION

Fixed the issue/the below workaround worked as per the following procedure.

https://www.reddit.com/r/linux_gaming/comments/16tqql7/how_would_i_disable_my_nvidia_gpu_for_a_specific/

"The proper way to select a particular GPU for Vulkan is to use MESA_VK_DEVICE_SELECT and MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE
Vulkan applications query the list of available GPUs, and by default there is no set enumeration order, and they can pick based on whatever criteria they wish.
Many distros' Steam packages create start menu/launcher shortcuts that tell it to prefer a discrete GPU if it can find one, and DXVK/VKD3D may also prefer dedicated graphics by default.

However those 2 environment variables are the official way to select/force a graphics card.

Changing VK_ICD_FILENAMES is wrong and only happens to work as a side effect of you only having 1 GPU from a given vendor. "

"Make sure that you have the mesa device selection layer installed from your package manager, and put the environment variables into the launch options for the game in steam

VARIABLE_NAME=value VAR2=value2 %command%

you will need to run "MESA_VK_DEVICE_SELECT=list vkcube" (or lspci) to find the pci bus address of the GPU you want to force, then in the launch options add

MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 MESA_VK_DEVICE_SELECT=0000:0000 %command%

replacing 0000:0000 with the address of your GPU"

In summary:

1. Ensure you have the mesa device selector package installed.

• 1a. A quick way to check is if you can run "MESA_VK_DEVICE_SELECT=list vkcube" or "MESA_VK_DEVICE_SELECT=list lspci"
• 1b. Cursory research indicates this is default as of Mesa 20.1or thereabouts

1. Find the appropriate device you want to use and note the PCI device ID on the left.

• 2a. It should say something like "VGA Compatible Controller: xxxxxx" where xxxxx is the name of the GPU in the description to the right of the device ID.
• 2b. Copy the PCI device ID. It will be something in the format of xx:yy.z

1. Input MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 MESA_VK_DEVICE_SELECT=xx:yy.z as Launch Options in Steam for that game along with any other options you want.

• 3a. It should then be running on the dGPU instead of the iGPU.
• 3b. EXAMPLE: MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 MESA_VK_DEVICE_SELECT=xx:yy.z %command%

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2027674402)

I tried all of these, and I still couldn't get the game to load past the initial load screens. If i switch over to bleeding edge, nothing happens and I can't load any other games until I reboot.

attached is a log i have attempting to load with the newest experimental. Please let me know if you see anything glaring.
steam-2073850.log.zip

I am also still waiting for someone to look at my log here

I am also still waiting for someone to look at my log here

Use services like pastebin please, never heard about this hosting site 🤔

Use services like pastebin please, never heard about this hosting site 🤔

File is too huge to be pasted into pastebin, so I have uploaded it on Google Drive as a .txt file so that you can see the file content without downloading it. Does that work for you? Otherwise, can you suggest me other hosting websites that you feel comfortable with?

File is too huge to be pasted into pastebin, so I have uploaded it on Google Drive as a .txt file so that you can see the file content without downloading it. Does that work for you? Otherwise, can you suggest me other hosting websites that you feel comfortable with?

I am sorry if I am spamming too much, but has anyone managed to look at my logs yet?

File is too huge to be pasted into pastebin, so I have uploaded it on Google Drive as a .txt file so that you can see the file content without downloading it. Does that work for you? Otherwise, can you suggest me other hosting websites that you feel comfortable with?

I am sorry if I am spamming too much, but has anyone managed to look at my logs yet?

75MB of logs? WUUUT? how? is that from Protonlogs launch parameter?
Are you starting the game with some parameters? It seems you don't have gamemode installed probably
Need to know: OS, hardware, launch parameters (try also with none), proton version (try Experimental)

75MB of logs? WUUUT? how? is that from Protonlogs launch parameter? Are you starting the game with some parameters? It seems you don't have gamemode installed probably Need to know: OS, hardware, launch parameters (try also with none), proton version (try Experimental)

Hey, thanks for the quick reply! I figured that the log is huge and yeah, I am starting the game with launch parameters. I have posted the things you asked for already so I will reference them:

1. Launch parameters I have tried and hardware / OS
2. Launch parameters I have tried number 2

I have gamemode installed, but gamemoded -t fails at one step. I couldn't find comments on the error and The Finals was able to launch even with the error, so not sure if it's relevant, but I can post the error as well. Also will try running without parameters again, but last time I did, I think it didn't start at all (edit: Nvm, it does, just need to get Steam to actually start logging...).

The logs are that big because of the same bits repeating constantly every second. My system does this too. I have had a few crashes too recently but before the big update it's been doing the same thing.

75MB of logs? WUUUT? how?

That's big? Mine are like 700 megs. All from just trying to load the game and getting as far as the first two splash screens......

75MB of logs? WUUUT? how? is that from Protonlogs launch parameter? Are you starting the game with some parameters? It seems you don't have gamemode installed probably Need to know: OS, hardware, launch parameters (try also with none), proton version (try Experimental)

Alright, also got a log without any launch parameters (except for logging ofc). Btw, I used Proton Experimental bleeding edge (I always do unless stated otherwise). Almost 100 MB this one, even though the game immediately crashed upon entering the first match. See here.

Also, here is the screenshot of my output for gamemoded -t:

On my side, the game load but crashes before the main menu.

Hardware specs

OS: Ubuntu 22.04.4 LTS
CPU: 12th Gen Intel i7-1260P (16) @ 4.700GHz
GPU: Intel Iris xe

The issue seems to be related to the missing msvproc.dll. Here's a part of the generatede steam-xxx.log (I can't join it as it is 45Mo)

1054.574:047c:0480:warn:debugstr:OutputDebugStringA "[0407/205549.145:ERROR:dxva_video_decode_accelerator_win.cc(1439)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)\n"
1054.574:047c:0480:warn:seh:dispatch_exception "[0407/205549.145:ERROR:dxva_video_decode_accelerator_win.cc(1439)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)\n"
[0407/205549.145:ERROR:dxva_video_decode_accelerator_win.cc(1439)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)

i decided to play the finals for around 8 hours straight and by the end the game had filled up my zram fully and started using my regular ram, dont know if this is a proton bug or the game itself doing this

i decided to play the finals for around 8 hours straight and by the end the game had filled up my zram fully and started using my regular ram, dont know if this is a proton bug or the game itself doing this

Thats a bug from the Finals and also the reason why the vm.max_map_count increasement is required.
The higher you set this value, the more you allow applications to have "huge memory leaks". Games which require this workaround simply have memory leaks, which should be fixed from the developers.

Here also info from Liam:
https://lore.kernel.org/lkml/ugjnhfiwuoslupkbmrrbbxxdosotzpqjfljebzj4dkuibmf6sr@kuew2qemsen4/T/#m1905a48f415bc6e8069a8fe53dec44bc311571f2

Setting the value that high as SteamOS is really not a good way doing it as default.

i distro hopped to bazzite and the lcd screens are borked, what codecs are being used for this? as i know fedora doesnt like to use a lot of the codecs that arch use because of open source and legal reasons also i think

Newest update to the game (2.6.0) broke anti-cheat installation, the developers said they updated their anti-cheat and even required secureboot on some installations (they weren't clear what they meant). I have secureboot enabled and working though.

The game tries to launch and install easy-anti cheat, but fails, and therefore can't launch. It worked fine with the game version before this one.

Newest update to the game (2.6.0) broke anti-cheat installation, the developers said they updated their anti-cheat and even required secureboot on some installations (they weren't clear what they meant). I have secureboot enabled and working though.

The game tries to launch and install easy-anti cheat, but fails, and therefore can't launch. It worked fine with the game version before this one.

Im playing it right now, working great, have you verified your files or deleted your prefix then verified?

Im playing it right now, working great, have you verified your files or deleted your prefix then verified?

Are you sure you are able to finish the round? After the update it has started kicking me from the game 5-10 mins into the round. I haven't been able to finish a game since. It's kicking me from the server with a message stating "Disallowed tool detected".
I wonder whether said tool is Proton. Or it could be my VPN (MullvadVPN). That had not been a problem before the update v2.6.0 though.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2090645247

Same for me.

Latest update (2.6.0) broke anticheat - able to connect and play a round or two but then get kicked off stating I got invalid software installed, don't have any VPN installed on the machine

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2090645247

Yup having the same issue after the update. Not using any shady apps or VPN tried changing protons and turning off apps all for nothing. Sent a support ticket to the finals devs... Hope they'll fix it ugh

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2090645247

Yep iv been playing for 6 hours now straight, playing in plat lobbies with my friends, havent been kicked, using latest bleeding edge, mesa 24.0.5, on bazzite, with mangohud also enabled

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2090764010

I've managed to complete non competitive games without issue only to get kicked a round into the new att-def mode or the ranked one, maybe they are more strict on competitive modes?

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2090772683

well i also played that new mode with my friends without issue, idk, verify, use latest experimental bleeding edge, if it keeps happening upload a proton log with PROTON_LOG=1 %command%

The massage I keep seeing after 2.6.0 update almost every round, noting installed on the machine that should trigger it, I'm on the latest experimental

Updating to add I've also tried experimental bleeding edge and the issue persists

the finals discord community has found a bug in the anticheat or something else that is occuring, if you use a semi auto gun like a rifle or revolver and spam shots for a minute, the game will kick you as a disallowed tool, i did this in training as someone else said to do and it worked

so please for now, dont use semi auto guns if you want to play the game without getting kicked

the finals discord community has found a bug in the anticheat or something else that is occuring, if you use a semi auto gun like a rifle or revolver and spam shots for a minute, the game will kick you as a disallowed tool, i did this in training as someone else said to do and it worked

so please for now, dont use semi auto guns if you want to play the game without getting kicked

Noticed as well that the game kicks me for using LH1. I thought I was tripping and the whole idea of it seemed really weird and dumb but its true. Used proton 9.4 today. Had no kicks at all, played for 2 hours straight even on att def mode until I took LH1 into my hands. After a minute or 2 got kicked mid game.

I wonder what causing this problem? Hopefully the devs will fix it.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2092811937

we are guessing its something to do with the anticheat detecting maybe some type of autoclicker when we click to fast lmao, i guess this was one of embarks ideas to stop cheating with autoclickers on semi auto guns, thing is tho it doesnt occur on windows so something must be triggering it by accident in proton, that would be my guess but could be something else happening aswell

I just played a few hours, then changed to semi auto or melee, can verify that I consistently get kicked for CPS (clicks per second) reasons and get the disallowed tool message, but have no issues if I don't have many CPS. I don't know where the logs are for the specific tool they are referring too, would be nice to know what they actually flagged.

Also, my previous issue, I can verify that the game is running after doing a verification of the game files, I had just done it recently as well, but it didn't occur to me that it's some kind of setup script that needs to be reran as well.

It's definitely the click per second, even when spectating click the mouse fast enough to switch who you're viewing and you get kicked. it makes semi-auto/melee weapons unusable but full auto where you hold the button down can still be used, once I switched to FCAR I'm able to finish games without a kick (provided I don't spam the mouse button otherwise)

I have been following along the bug thread on The Finals Discord and have tried to replicate it myself and I can confirm that there is some sort of anti-macrokey detection that reads mouse button inputs. So by simply spamming the mouse button (Left mouse button in this case) you will get kicked. So to avoid this for now, you need to use software to spoof/map the left mouse button as a keyboard key instead. Since it only reads mouse clicks, it won't kick you if you have binded the firing action on a key.

https://github.com/ValveSoftware/Proton/assets/52935906/480aa18f-b8c2-4023-ae74-9eac5efb1756

^ Here I am holding down mouse button. After the two reloads, I start spamming the left mouse button until I get kicked

https://github.com/ValveSoftware/Proton/assets/52935906/e283ec85-ba03-4a6b-a7fa-22b25f683f47

^ A repost of a video from the discord bug thread. Here they have mapped the left mouse button on the comma key, spamming it for about 1 minute (cropped it here to save space) and didn't receive a kick

Edit: The latest Proton Experimental ([Bleeding-edge] branch) has a patch for this issue. So clear the wine prefix for The Finals and run it under Bleeding edge instead of going for the key mapping workaround.

So to avoid this for now, you need to use software to spoof/map the left mouse button as a keyboard key instead.

Is it somehow possible to map a mouse button to a key and map activating that key to the mouse button? Or would that just no work because it's physically a mouse button.

If you like using semi-automatic weapons you can use a workaround using xinput that will rebind your left-mouse-button to scroll-wheel-up preventing the strange spam detection.

no extra tools on a default Ubuntu install or most Xorg desktop environments

⚠️ This will fire-rate limit automatic weapons to semi-automatic

XP-54 will be semi-automatic 😎

Get your mouse ID from xinput

$ xinput --list                                                               
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Endgame Gear XM2we Gaming Receiver        id=8    [slave  pointer  (2)]
⎜   ↳ Endgame Gear XM2we Gaming Receiver Keyboard       id=9    [slave  pointer  (2)]

In my case the mouse ID is 8

Then using xinput set-button-map command to change the order of the mouse buttons to use

xinput set-button-map <DEVICE_ID> 4 1 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

left-mouse-button => scroll-wheel-up
middle-mouse-button => left-mouse-button ( needed for menu-selections )

❕In-game

• Bind Primary Fire to your new left-mouse-button (scroll-wheel-up)
• Bind an alternative Primary Fire as the swap will not allow hold actions - for gadgets like the 'Defibrillator'

To revert simply run the command with the ordering as normal.

xinput set-button-map <DEVICE_ID> 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

The just updated Proton Experimental ([bleeding-edge] branch) has a tentative fix for the discussed kick problem. It doesn't fix it completely, if to mash hard and for a long time it may still kick you, but maybe it will be much less of an issue now. Reporting back how much the fix helps or not is welcome.

Proton Experimental's [bleeding-edge] branch is available to select in Proton Experimental properties, BETAS tab; Proton Experimental should be selected as Compatibility tool for the game). If the Steam was already running it is best to restart it to make sure the just updated Proton is picked up. Note that it is not recommended to use as a default tool for everything, [bleeding-edge] contains untested changes.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2094486231

it seems to have fixed it for me, i spammed a v9s for around 5 minutes and i didnt get kicked from training, maybe ill need to do it for longer for it to happen lol

@gofman Yupp, it really seems to be fixed on Proton Experimental ([bleeding-edge] branch)! Played multiple games using the Famas and didn't get kicked once. Even went to the practice range and spammed like a mad man and didn't get kicked. I have heard from some that it is still possible to get kicked but you have to spam the mouse button continuously for multiple minutes for that to happen, which is something no one would practically do in a match. Before I would be kicked in seconds..

Very happy to see it fixed this quickly!

@gofman Yupp, it really seems to be fixed on Proton Experimental ([bleeding-edge] branch)! Played multiple games using the Famas and didn't get kicked once. Even went to the practice range and spammed like a mad man and didn't get kicked. I have heard from some that it is still possible to get kicked but you have to spam the mouse button continuously for multiple minutes for that to happen, which is something no one would practically do in a match. Before I would be kicked in seconds..

Very happy to see it fixed this quickly!

Same for me, no issues with bleeding-edge anymore

THE FINALS™ (2073850) BLEEDING EDGE PROTON (4).pdf

This PDF document contains step 🪜 by step 🪜 instructions to resolve the issue but I also included the images & information below:

• Following these steps

• To enable the easy anti-cheat runtime inside of Steam

• To enable the bleeding edge branch of proton experimental

• To delete the THE FINALS™ 2073850 wine prefix comp data folder

• (clear the wine prefix in the compatdata-folder)

So what you need to do is

1. Close the game and make sure it is not running
2. Delete the prefix, its going to be recreated later
3. Run the game and the prefix will be created with the bleeding edge
4. For later reference, if you switch back to normal prefix, do the same thing of clearing prefix

• {if you are using a FlatPak it will be in a different location entirely}
• ~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata

the reason why its important to clear the prefix is to avoid bugs:

such as the one you encountered being kicked from the match.

It should be all fine, no worries about your account.

The macro-detection (the "cheating" that i mentioned) just kicks you from the game, does not get you banned :)

• Completely resolves the issue for me

I'm getting 5-10 fps in Pop_OS 22.04. Also, my resouces are not getting fully utilized, like only 13-14% of cpu and 0% gpu , I'm using Proton experimental bleeding edge and a NVIDIA card ,gtx1650

When the game starts then cpu usage gets up to 100%, but Gpu remains 0% all the time.

I'm getting 5-10 fps in Pop_OS 22.04. Also, my resouces are not getting fully utilized, like only 13-14% of cpu and 0% gpu , I'm using Proton experimental bleeding edge and a NVIDIA card ,gtx1650

When the game starts then cpu usage gets up to 100%, but Gpu remains 0% all the time.

To me it sounds like you haven't configured the game to use your video card, a few months ago an update broke it abilty to properly detect video cards on linux so now you need to pass your video card in the params (otherwise it uses the CPU onboard one which results in 0 graphic card usage and huge CPU usage like you describe as well as slow framerate), mine looks like DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 4060" %command% but you'll need to enter your own device name to match instead

I'm getting 5-10 fps in Pop_OS 22.04. Also, my resouces are not getting fully utilized, like only 13-14% of cpu and 0% gpu , I'm using Proton experimental bleeding edge and a NVIDIA card ,gtx1650
When the game starts then cpu usage gets up to 100%, but Gpu remains 0% all the time.

To me it sounds like you haven't configured the game to use your video card, a few months ago an update broke it abilty to properly detect video cards on linux so now you need to pass your video card in the params (otherwise it uses the CPU onboard one which results in 0 graphic card usage and huge CPU usage like you describe as well as slow framerate), mine looks like DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 4060" %command% but you'll need to enter your own device name to match instead

Where do I have to pass this parameter? Launch options?

https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2098472172 yes

[#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2098472172) yes

Thanks, it worked

https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-1902781208

Edit: Looks like I had some kernel parameter that was preventing EAC from doing its thing. Also checked Brawlhalla to make sure it wasn't just The Finals, and sure enough that also wasn't working. Fixed.

Do you happen to remember what you did? I'm having the same symptoms with some EAC games.

Compatibility Report

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

System Information

• GPU: AMD Radeon 6950XT
• Video driver version: mesa 24.0.7
• Kernel version: 6.8.9-zen
• Link to full system information report as Gist: https://gist.github.com/itsaerosphere/d357648202f7629dd43b35ff6c78c5aa
• Proton version: Proton Experimental

I confirm:

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

steam-2073850.zip

Symptoms

I haven't been able to open the game much since yesterday. I've been getting wine/proton assertion errors to the likes of "!status && vkCreateGraphicsPipelines" between 2 and 15 times at once and smth else about vulkan ray tracing on the rare time I do manage to get to the main menu and try to start a match.

Some troubleshooting lead me to believe it has to do with shader pre-caching since the crash always happened at that specific time in the game's loading sequence. Disabling Steam's own pre-caching seemed to have fixed it... until it broke right after. Re-installing the game, verifying file integrity and deleting compdata all had varying levels of success, but the crash always eventually reared it's head not long after.

Reproduction

1. Launch the game via steam using the above configuration and without any launch options.
2. Have the game do shader pre-caching while it's loading.
3. Watch as 2-15 wine/proton errors pop up simultaneously complaining about the vulkan graphics pipeline (or something)

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.

I'm getting 5-10 fps in Pop_OS 22.04. Also, my resouces are not getting fully utilized, like only 13-14% of cpu and 0% gpu , I'm using Proton experimental bleeding edge and a NVIDIA card ,gtx1650
When the game starts then cpu usage gets up to 100%, but Gpu remains 0% all the time.

To me it sounds like you haven't configured the game to use your video card, a few months ago an update broke it abilty to properly detect video cards on linux so now you need to pass your video card in the params (otherwise it uses the CPU onboard one which results in 0 graphic card usage and huge CPU usage like you describe as well as slow framerate), mine looks like DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 4060" %command% but you'll need to enter your own device name to match instead

@naorlivne @Majistor What type of GPU setup do you have? Please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report. Looking into if there is anything we can do to improve this :)

Could you also please get logs with PROTON_LOG=+win,+x11drv,+xrandr,+system %command% both with and without the DXVK command so that we can look at the failing state and see what is happening?

The game got an update today and now it crashes for me when launching shortly after going fullscreen.
steam-2073850.log.tar.gz

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.

Same, also crashing here with all official Proton versions.

Windows users are also having crashes so its not just us, and its probs the same unreal error just that window isnt popping up for us

GE-proton-9-2 works, so does using proton experimental with the bleeding-edge-8.0 beta, newer version crash at startup, unfortunately both versions also have the rapid-mouse-click-get-kicked bug in them

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

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

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.

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

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%

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2135243886

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

Do you have proton eac runtime installed?

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.

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

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

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

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.

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.

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

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:

• [x] that I haven't found an existing compatibility report for this game.
• [x] 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.

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

Same for me but with different error: TFGE0027

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

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2179076243

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.

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.

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.

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

Huh. I wish I knew which option.

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?

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

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.

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

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.

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

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2179076243

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

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.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2192275669

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

I'm having the same issues that everybody else seems to be having

The game worked flawlessly out of box season 1 and season 2

But when season 3 happened I got these really bad lag conditions where the FPS would drop to one in the game

I thought there was corruption in my files so I nuked my wine prefix

I also uninstalled the game

I also uninstalled the bleeding edge of proton experimental

I reinstalled proton experimental

I reinstalled the game

And then after the pre-compiling shader pipeline

The screen would freeze the finals logo that usually moves on the bottom frozen

And the FPS would drop to one

And then the game would crash

It doesn't matter if I'm in X11 or Wayland

I have the most up-to-date drivers

I'm running a threadripper 1920x so it doesn't even support AVX512

Even though I have that disabled in the grub kernel options

I did all of the things that they asked you to do in all of the Reddit posts and everything on ProtonDB

I Increased the default vm.max_map_count value

And I've tried all sorts of different game launch options as suggested on protonDB

I'm really pulling out my hair because the game works flawlessly and fine out of box from season 1 and season 2

So I don't know what changed or what's different now to make it so it is completely not working

I can post my proton logs if that would be helpful to anyone here

Hello,
For me, on Debian 12 with native linux Steam + compatibility forced Proton Experimental (same with Force Compatibility unchecked), the game starts fine. I can browse the menus without issues (main, character customization, settings, etc.), but I get error TFGE0025 whenever trying to start a practice match. The error shows after the match is found, when the game tries to connect to it.
Regards.

Hello,
For me, on Debian 12 with native linux Steam + compatibility forced Proton Experimental (same with Force Compatibility unchecked), the game starts fine. I can browse the menus without issues (main, character customization, settings, etc.), but I get error TFGE0025 whenever trying to start a practice match. The error shows after the match is found, when the game tries to connect to it.
Regards.

Hardware?

Running this game on Linux has been very frustrating.
When it works, it runs flawlessly - better than it does on my Windows install.

However, whenever I launch it there's a 50% chance of getting the error whist the shader pipelines are compiling:

Out of video memory trying to allocate a rendering resource. Make sure your video card has the minimum required memory, try lowering the resolution and/or closing other applications that are running. Exiting...

If I manage to get the shaders pre-compiled (which takes an annoying amount of time) - then there's a 50% chance of actually getting into a game.

I will be met with the TFGE0027 error when I try to join a game - if I join a ranked game, I get this error and then end up with a matchmaking ban!

So in my experience, the game will work about 20% of the time.
And each failed attempt takes 2-3 minutes, since the shaders need to be compiled every time.

I've tried various suggestions, but I'm starting to think this all just stems from EAC, making it difficult to troubleshoot.

Some of my configurations:

3070TI with latest Nvidia propietary driver.
AMD Ryzen 5800x3D
32Gb RAM
Ubuntu 22.04.4
Proton Experimental

Launch options:
PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 gamemoderun %command% -dx12

Hello,
For me, on Debian 12 with native linux Steam + compatibility forced Proton Experimental (same with Force Compatibility unchecked), the game starts fine. I can browse the menus without issues (main, character customization, settings, etc.), but I get error TFGE0025 whenever trying to start a practice match. The error shows after the match is found, when the game tries to connect to it.
Regards.

Hardware?

Hello,

Motherboard: ASUSTeK Computer Inc. P9X79
Memory: 32GB
CPU: Intel Core i7-4930K x 12
GPU: NVidia GeForce RTX 2070 (8192 MB VRAM; Proprietary driver 550.90.07)
Storage: 4TB SSD eSATA

Regards

My issue w/ TFGE0027 is really weird. I get it once per reboot. My current workaround is to join training, get kicked, restart game, and then usually it works just fine.

My issue w/ TFGE0027 is really weird. I get it once per reboot. My current workaround is to join training, get kicked, restart game, and then usually it works just fine.

are you using proton experimental or proton-ge as this has the fixes for that error im pretty sure, what keyboard and mouse are you using also and any software that creates clicks or hotkeys rapidly as i think it can trigger that error aswell

I'm on experimental bleeding edge. No kb/m macros.

lcd screens are broken for me again lol, cleared prefix, tried latest proton-ge, using experimental(bleeding edge), arch, mesa 24.1.3, kernel 6.9.9, rx 6700, ryzen 7600

Video playback issue was introduced by Proton wine commit 195d925 undoing it seems to be a temp fix 🙂

Video playback issue was introduced by Proton wine commit 195d925 undoing it seems to be a temp fix 🙂

Seems like they reverted the change :D

https://github.com/ValveSoftware/wine/commit/15fc460839c13788030a416651716b869e28bd65

Thanks proton devs as per usual 🙃

Fwiw I've been trying to reproduce but I'm not completely sure how to, I have added a different fix for the original issue which should hopefully not break The Finals this time, and I'm interested to know whether it indeed indeed does, for people who were seeing broken videos.

Fwiw I've been trying to reproduce but I'm not completely sure how to, I have added a different fix for the original issue which should hopefully not break The Finals this time, and I'm interested to know whether it indeed indeed does, for people who were seeing broken videos.

One sec gonna test

edit: it is not showing correctly on the latest version of bleeding edge, if there is a newer change let me know ill retest(as im addicted to this game lol)

I actually managed to reproduce the regression, and it seems to me that the new fixes that I pushed earlier to bleeding-edge are actually fixing it. Maybe make sure that Proton Experimental bleeding-edge is up to date?

i have tested the latest bleeding edge and i tested without clearing prefix, screens arent working

after clearing the prefix same thing

after deleting experimental(bleeding edge) and redownloading it same issue for me

this is on a clean install of cachyos also, rx 6700, ryzen 7600, kernel 6.10

here is a proton log also
https://drive.google.com/file/d/1YPojtUzTibKdvHwjToNzWtN2vtmbzP4s/view?usp=sharing

Videos are working again on my system, I had to go back and check i had the right commit, I did get the right one.

Also here's a patch for the static crackling audio that can be heard throughout the game, most noticeable on the menu.
pulse.txt

@polluxau Weirdly we are no longer reproducing the video failures with the latest bleeding-edge. Could you try running this in a terminal just in case h264 got re-locked?
steam steam://unlockh264/

If that doesn't help - could you get 2 logs, one with the failing videos with experimental-bleeding-edge and one with the working videos with experimental (non-bleeding-edge, no beta selected)? Ideally, it would be great if you could use this user_settings.py file dropped into your common/Proton - Experimental folder instead of PROTON_LOG=1. I've added some extra logging in there. You will need to rename the file from user_settings.py.txt to user_settings.py - I renamed it to be able to upload here.
user_settings.py.txt

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2234208183

doing steam steam://unlockh264/ makes it work again! thank you!

i rlly appreciate it :)

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2234208183

did some more testing as the h264 unlock command stopped working for me

here is the log for bleeding edge that you asked for from the user_settings.py that you gave me
https://drive.google.com/file/d/1C2SMV76T2LFon_QEw6_wjo097IY2JU9u/view?usp=sharing

also i tested proton 9, that has the old video issue, where the video is all different colors and lots of corruption with the video

with proton-ge-9-9 the video is working for me, ge-9-9 came out 3 weeks ago

here is the log for proton-ge-9-9
https://drive.google.com/file/d/19b8qFAJnJ3GVktmjQ307q6USBOLMyCLe/view?usp=sharing

one that did work with normal proton was proton hotfix

log for proton hotfix, i couldnt get into a match anymore because the servers started kicking me lol
https://drive.google.com/file/d/1u_PZiHtAMBqknvdbAJ_T5PUJfVQYcm9N/view?usp=sharing

the lcd screens are working again on latest bleeding edge! thank you :)

the game is no longer working with the newest update, here is my log

https://drive.google.com/file/d/1TcNHRRSgI8qHyzBzWjpY7IkKPFLcScpi/view?usp=sharing

+1 for the newest update breaking the game :(

Yeah, can confirm that the latest update has broken the game, it now refuses to launch.

Log: https://drive.google.com/file/d/1p9BuHdAeyGdRVT9ZAOVGym_bZC9vGfL7/view?usp=drive_link

Latest update crashes and quits to desktop instantly

Latest update crashes and quits to desktop instantly

Same

+1 last update broke it

yep, last update 3.6.0 is completely broken with no known fix yet. seems to be literally everyone on linux

Running on Ubuntu 24.04 - Steam Proton Experimental, removing the modified file from the update;

Modified – Engine/Binaries/Win64/CrashReportClient.exe (+448 B)

Stops the game crashing on launch and lets you access the menus (but be careful as a fatal error box will loom and the game may hang and suggest force closing - ! but ignore the warnings ! )

It then does crash anyway after a period of time.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2248719034

Interesting. I've just tried copying over the old crash reporter from the 3.4.0 game version, which does not solve the issue with this game update (same behavior unfortunately). Guessing there has been a change in the main binary (Discovery.exe) in how it communicates with the crash reporter (CrashReportClient.exe) which doesn't play nicely with Proton.

Not working here either
System

• EndeavourOS
• Linux 6.10.0-arch1-2
• AMD Ryzen 5 3600
• NVIDIA GeForce RTX 2080 Rev. A (driver package: nvidia-dkms 555.58.02-1)

Tried with

• Proton Experimental
• Proton 9.0-2
• GE Proton 9-10

(with shader pre-caching disabled)

My log seems superficially identical tho notably I have this assertion at the very end (with any Proton Version):

1560.514:056c:0570:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\libvkd3d-shader-1.dll" at 00006FFFFCE60000: native
1560.514:056c:0570:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\libvkd3d-1.dll" at 00006FFFFD0B0000: native
1560.514:056c:0570:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\wined3d.dll" at 00006FFFFD130000: builtin
1560.514:056c:0570:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\d3dcompiler_47.dll" at 00006FFFFD2E0000: builtin
1560.517:056c:0570:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x8800.
1560.518:056c:0570:err:msvcrt:_wassert (L"iff->condition.node->data_type->dimx == 1",L"../src-vkd3d/libs/vkd3d-shader/tpf.c",5240)
1560.518:056c:0570:trace:seh:raise (22)

Crashes when trying to launch the game. I can confirm that deleting the CrashReportClient.exe allows the game to launch, but it does ultimatly crash a minute or two later. I have attached two logs.

• Garuda Linux x86_64
• Linux 6.10.0-zen1-2-zen
• AMD Ryzen 9 7900X
• NVIDIA GeForce RTX 4090 nvidia-dkms 555.58.02

Note: These files are large, 1GB+. I am hosting them on my CDN.
Log 1: No game modification: steam-2073850.log.zip
Log 2: CrashReportClient.exe deleted. steam-2073850.log.zip

That should hopefully work now with the just updated Proton Experimental [bleeding-edge] branch (not tested though). [bleeding-edge] branch is available in Proton Experimental tool properties, Betas tab (and Proton Experimental should be selected as Compatibility tool for the game). If Steam is running it is better to restart to make sure it picks just updated Proton version.

It boots! I'll report back if any new crashes occur, thanks for the patch!

Can confirm the bleeding-edge branch on Proton Experimental works flawlessly.

good job proton devs :D

iv been playing it for about 4 hours now without any crashes or needing to close it :>

Works now, good stuff - no crashes +rep :clap:

Thank you for the fast fixing time! Works perfectly again.

Using Bleeding Edge - I can confirm that this has fixed the launch issues, but we're back to occasional crashes and the LCD screens not rendering correctly

Edit: I'd say the crashes are so frequent it's very problematic. I cannot get through a tournament without at least one.

Hello Proton team,

This hotfix got Finals to load and appear to work for me. Now, I can join a match and shortly after it is a full application freeze, needing to force-quit the game. (Underlying OS is still fine, it's not a 'system' freeze) I was previously on proton experimental and it worked great, something is slightly off with the hotfix beta
steam-2073850.log.tar.gz
.

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

System Information
GPU: GeForce RTX 3070
Video driver version: NVIDIA version 535 stable (535.183.01-0ubuntu0.22.04.1)
CPU: Intel i9-10850K (20) @ 5.200GHz
Kernel version: 5.15.0-117-generic
OS - Linux Mint 21.3 x86_64
DE: MATE 1.26.0
Resolution: 1920x1080, 1920x1080
Proton version: Proton Experimental (bleeding-edge beta)

-Log attached

Echoing some of the other responses here. Using the latest bleeding edge, I can get the game to boot - but I can scarcely make it through a match without the app crashing - requiring a force-close.
Strangely, when the crash occurs, I can still hear the in-game voice chat - but it is otherwise unresponsive.

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

System Information
GPU: GeForce RTX 3070TI
Video driver version: NVIDIA version 535 stable
CPU: AMD 5800X3D
OS - Ubuntu 22.04
Resolution: 2560 x 1440
Proton version: Proton Experimental (bleeding-edge)

steam-2073850.zip

I've attached the log file. Hopefully this helps.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2256669619

I moved from 21 to Mint 22 and it stopped crashing on bleeding edge. It looks like you are already on ubuntu 22.04 so I'm interested what they can find in your log

Previous to today, Proton Experimental - Bleeding Edge was working fine, but now it looks to have updated. After it updated, it is causing the same crashes as it did before. I start the game, EAC script runs, game opens to loading screen, and crashes shortly after.

OS: CachyOS Linux x86_64
Kernel: Linux 6.10.2-2-cachyos
CPU: 13th Gen Intel(R) Core(TM) i7-13700K (24) @ 3.40 GHz
GPU 1: Intel UHD Graphics 770 @ 1.60 GHz [Integrated]
GPU 2: NVIDIA GeForce RTX 3070 [Discrete]
Proton Version: Proton Experimental - Bleeding Edge

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2258855471

Updated like the game or the runtime or something else? I was playing it also on cachy os for 6 hours playing it lol

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2258861267

Proton Experimental - Bleeding Edge updated. I was able to play earlier just fine as well. Seems like others are experiencing the same thing on the discord now that this updated.

Hello @Zach67, please add PROTON_LOG=1 %command% to the game's launch options, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

I'm not the original poster, but I'm getting this issue on the bleeding-edge version.
Here's some logs:
steam-2073850.zip

And a gist for the Runtime Diagnostics: https://gist.github.com/Conbag93/724eeec49bef115f53c59f46ebd24f40

System Information
GPU: GeForce RTX 3070TI
Video driver version: NVIDIA version 535 stable
CPU: AMD 5800X3D
OS - Ubuntu 22.04
Resolution: 2560 x 1440
Proton version: Proton Experimental (bleeding-edge)

Experimental [bleeding-edge] is a development version where commits go directly without any sanity check. Sorry, it was accidentally broken but now the previous version is restored and it should hopefully work like before after restarting Steam / updating [bleeding-edge] once again. I hope quite soon the fix for The Finals will be in Experimental proper (default branch) and there will be no need to suffer with [bleeding-edge].

Experimental [bleeding-edge] is a development version where commits go directly without any sanity check. Sorry, it was accidentally broken but now the previous version is restored and it should hopefully work like before after restarting Steam / updating [bleeding-edge] once again. I hope quite soon the fix for The Finals will be in Experimental proper (default branch) and there will be no need to suffer with [bleeding-edge].

I can confirm that this has fixed the launch issues - although I'm still suffering from the random crashes I shared earlier.

I just tried this game on a Maxwell GPU, (a GTX 970) here's my findings:

• Reflex didn't appear unless I spoof a Pascal GPU (or anything newer than Maxwell) in DXVK-NVAPI
• Rendering of the map is heavily broken, appearing dark grey almost everywhere there's a destructible wall. Other objects render correctly.

-dx11 works around the incorrect rendering and also runs smoother when shaders aren't compiling on draw, however due to Reflex not working for DXVK yet it won't work in this game without DX12.

I just tried this game on a Maxwell GPU, (a GTX 970) here's my findings:

* Reflex didn't appear unless I spoof a Pascal GPU (or anything newer than Maxwell) in DXVK-NVAPI

* Rendering of the map is heavily broken, appearing dark grey almost everywhere there's a destructible wall. Other objects render correctly.

-dx11 works around the incorrect rendering and also runs smoother when shaders aren't compiling on draw, however due to Reflex not working for DXVK yet it won't work in this game without DX12.

per Finals a 970 is absolute minimum spec it'll run on, and I'd expect that to be with some minimal settings and drawbacks, that GPU is a decade old.

With the recent 3.8 patch, the game seems to crash again.
After removing PROTON_ENABLE_NVAPI=1 from my launch options it works and can be readded, when it's done compiling shaders.

After the last hot fix I have been getting crashes nearly every game. It makes it very unplayable, can any tell me if it is a proton problem or something else? Thanks, keep up the good work proton team!

the-finals-crash.zip

Well I thought that fixed it but today I have had crashes almost every game again. I also forgot to mention that text chat doesn't work. Before when a crash would happen my desktop would hang but it doesn't anymore. Here are my logs:

crash.zip

From what I can see there are a lot of errors with could not LoadLibrary: msvproc.dll: Module not found.. Not sure if that is the right thing though, thanks!

Edit: After playing power shift nonstop today I had 0 crashes so I wonder if it is something to do with world tour that causes the crashes?

Update: Moved back to proton-hotfix and now I have no problems.

For me nowadays after game update 3.9.0 on Proton Experimental, the game randomly freezes within a match. I managed to pinpoint the exact offending line in the console output produced by steam, it shows me this:

Win64/Discovery.exe: ../src-wine/dlls/ntdll/unix/virtual.c:1907: create_view: Assertion `!((UINT_PTR)base & page_mask)' failed.

The file generated by PROTON_LOG=1 launch parameter was way too bloated for me to identify any other offending line. I extracted the last 33k lines (out of ~1,7m) of my latest play session in hopes that they will prove any use.

steam-2073850.extract.log

Computer Information:

CPU Brand: AMD Ryzen 7 7700X 8-Core Processor
Speed: 5573 MHz
16 logical processors
8 physical processors
Linux Mint 21.3 (64 bit)
Kernel Version: 6.8.0-40-generic
X Window Manager: Mutter (Muffin)
Steam Runtime Version: steam-runtime_0.20240610.91380
Driver: NVIDIA Corporation NVIDIA GeForce RTX 4080 SUPER/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 550.90.07
OpenGL Version: 4.6
Monitor Refresh Rate: 74 Hz
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Primary VRAM: 16376 MB
RAM: 31732 Mb

It also seemed if I didn't include PROTON_USE_EAC_LINUX=1 in my launch parameters, the game kicked me out of every match with the TFGE027 error code before connecting to any. This wasn't an issue before... Wish I understood why it works now. I couldn't find any documentation regarding this option.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2294876422

Can you please try bleeding edge and retry?

Game isnt crashing for me on cachy os, kde plasma, mesa 24.2, rx 6700, iv played for around 3 hours straight

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2294876422

Consider mint22 Wilma, the new kernel runs the game perfectly. This is the long term Mint release, 21.3 support is ending

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2294876422)

@polluxau Alright, I figured out how to do that. About 25 mins, everything went smooth then it froze again. Got a bigger log this time, 130k lines and a rhyme to go along.
steam-2073850.extract.log

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2294876422)

@16bitfighter Not a solution for me unfortunately, I did try upgrading and did not have the greatest experience; it broke some of the other software I use. I will wait a little longer to try again. Still thanks for your concern.

Win64/Discovery.exe: ../src-wine/dlls/ntdll/unix/virtual.c:1907: create_view: Assertion `!((UINT_PTR)base & page_mask)' failed.

What does 'cat /proc/sys/vm/max_map_count' say? It is probably around 64k? In that case it is better to increase that to some 500000000.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2294898329

Im pretty sure mint 21 vm max map count is too low, this fixes the crashes because there is more virtual memory available for the game to be used, if your using mint 22 then this is already solved

Replying to comment

@gofman Seems that was it: the variable was set too low, 65536 or 64kb as you inferred. So I set it to 20 times that by running sysctl -w vm.max_map_count=1310720 as root.

After that, I've played without any more freezes. Even Proton Experimental works fine, without the bleeding edge and whatnot.
However this fix doesn't persist after a reboot just like that, but at least it works.

Thanks!

Does anyone know a reliable fix for the TFGE0027 issue yet? It seems to happen completely randomly and require a variety of game restarts, system restarts, and prefix wipes to make it go away. Yes, my EAC runtime and launch options are set up correctly. This is the only game with this problem and it's extremely common among some of the regular players from what I've observed.

It's gotten bad enough to the point where after almost 2 hours of troubleshooting today, I couldn't get around it when I would normally have completed two or three World Tours by that time.

EndeavourOS x86_64
Steam Families Beta
Proton Experimental bleeding-edge (all branches and all recent proton versions have this problem)
Zen/Liquorix Kernel
X11, Trinity Desktop Environment
nvidia GeForce RTX 4070, latest driver from Arch repositories

Normally I will play power shift 2 times then move to quick cash. After being kicked from all of those games I relaunch the game it it works fine. Game chat still doesn't work for me even on bleeding-edge so I wonder if there is some network problems?

@bonkmaykrQ The issue is related to the anti-cheat, to fix it you need to enable secure boot. they added this requirement back in the middle of season 2.

I bet everything that the TFGE0027 error is related to the anticheat. The game would kick me out of any match with that exact code before connecting to them if I didn't include PROTON_USE_EAC_LINUX=1 in my launch options.

@bonkmaykrQ perhaps a more detailed log would prove useful in detecting the source of the issue for you. Also you should indicate which launch options you use, or really anything you've tried; it's pretty vague when you just say you have "set up your runtimes and launch options correctly".

I'm using Fedora 40 with secure boot enabled, also has PROTON_USE_EAC_LINUX=1 %command% set. However when starting game, it keeps reporting need secure boot to be enabled and exits. Anyone have the same problem?

The Finals stuck at EAC anti cheat initializing and keep asking for secure boot enabled (2073850)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/8033.
@Headcrabed posted on 2024-08-28T17:34:04:

Compatibility Report

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

System Information

• GPU: AMD Radeon RX 7800 XT
• Video driver version: Mesa 24.1.6
• Kernel version: 6.10.6-200.fc40.x86_64
• Link to full system information report as Gist: https://gist.github.com/Headcrabed/b0e81a6a01ff7655072d020014e3af37
• Proton version: 9.0-2 (GE-Proton9-11 won't work either)
• OS: Fedora 40

headcrab@Headcrab-PC-Lnx:~$ fastfetch
             .',;::::;,'.                 headcrab@Headcrab-PC-Lnx
         .';:cccccccccccc:;,.             ------------------------
      .;cccccccccccccccccccccc;.          OS: Fedora Linux 40 (KDE Plasma) x86_64
    .:cccccccccccccccccccccccccc:.        Kernel: Linux 6.10.6-200.fc40.x86_64
  .;ccccccccccccc;.:dddl:.;ccccccc;.      Uptime: 17 mins
 .:ccccccccccccc;OWMKOOXMWd;ccccccc:.     Packages: 2430 (rpm)
.:ccccccccccccc;KMMc;cc;xMMc;ccccccc:.    Shell: bash 5.2.26
,cccccccccccccc;MMM.;cc;;WW:;cccccccc,    Display (LG ULTRAGEAR): 2560x1440 @ 180 Hz in 31″ [External]
:cccccccccccccc;MMM.;cccccccccccccccc:    DE: KDE Plasma 6.1.4
:ccccccc;oxOOOo;MMM000k.;cccccccccccc:    WM: KWin (Wayland)
cccccc;0MMKxdd:;MMMkddc.;cccccccccccc;    WM Theme: Breeze
ccccc;XMO';cccc;MMM.;cccccccccccccccc'    Theme: Breeze (Dark) [Qt], Breeze [GTK3]
ccccc;MMo;ccccc;MMW.;ccccccccccccccc;     Icons: breeze-dark [Qt], breeze-dark [GTK3/4]
ccccc;0MNc.ccc.xMMd;ccccccccccccccc;      Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK3/4]
cccccc;dNMWXXXWM0:;cccccccccccccc:,       Cursor: breeze (24px)
cccccccc;.:odl:.;cccccccccccccc:,.        Terminal: konsole 24.8.0
ccccccccccccccccccccccccccccc:'.          CPU: AMD Ryzen 9 7950X (32) @ 5.88 GHz
:ccccccccccccccccccccccc:;,..             GPU: AMD Radeon RX 7800 XT [Discrete]
 ':cccccccccccccccc::;,.                  Memory: 6.13 GiB / 30.97 GiB (20%)
                                          Swap: 0 B / 8.00 GiB (0%)
                                          Disk (/): 175.83 GiB / 1.86 TiB (9%) - btrfs
                                          Local IP (enp11s0f1np1): 192.168.1.128/24
                                          Locale: zh_CN.UTF-8

I confirm:

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

Symptoms

When starting game, EAC anti cheat keep asking me to enable Secure Boot, However it is enabled and works with no problem in windows. And setting PROTON_USE_EAC_LINUX=1 has no effect. BIOS is also upgraded to newest version available.

headcrab@Headcrab-PC-Lnx:~$ mokutil --sb-state
SecureBoot enabled

steam-2073850.log
Steam Runtime Diagnostics Output

Reproduction

Just download and start the game under Fedora 40.

I'm using Fedora 40 with secure boot enabled, also has PROTON_USE_EAC_LINUX=1 %command% set. However when starting game, it keeps reporting need secure boot to be enabled and exits. Anyone have the same problem?

I'm also on Fedora 40, but this doesn't happen to me, secure boot is disabled, it doesn't seem to cause any issue and I can play the game normally.
I just get kicked sometimes but it also happens on Windows.

I use GE-Proton9-11 if that helps and I'm on an AMD Ryzen™ 5 5600 × 12 with an AMD Radeon™ RX 7600 Graphics card.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2315730178

Thanks for reply. I'll try GE-Proton.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2315730178

Sadly it still won't work.

I'm using Fedora 40 with secure boot enabled, also has PROTON_USE_EAC_LINUX=1 %command% set. However when starting game, it keeps reporting need secure boot to be enabled and exits. Anyone have the same problem?

I'm also on Fedora 40, but this doesn't happen to me, secure boot is disabled, it doesn't seem to cause any issue and I can play the game normally. I just get kicked sometimes but it also happens on Windows.

I use GE-Proton9-11 if that helps and I'm on an AMD Ryzen™ 5 5600 × 12 with an AMD Radeon™ RX 7600 Graphics card.

Even re-installing Fedora doesn't work either.

I'm having these major frame stutters every 2-3 seconds, DX12 and DX11 have the same issue

OS: openSUSE Tumbleweed x86_64
Host: B650 AORUS ELITE AX ICE
Kernel: 6.10.5-1-default
Packages: 3637 (rpm), 24 (flatpak) Shell: bash 5.2.32
Resolution: 2560x1440
DE: Plasma 6.1.4 wayland
WM: kwin
Theme: Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [GTK2/3]
Terminal: konsole
CPU: AMD Ryzen 9 7950X3D (32) @ 5.759GHz
GPU: NVIDIA GeForce RTX 4070 Ti
Drivers: 560.35
Memory: 12437MiB / 31536MiB

steam-2073850.zip

Hello.
No change for me. Always get error TFGE0025 when a match is found in training mode, with and without PROTON_USE_EAC_LINUX=1 %command% on Proton Experimental.
I did not try other modes or other proton version.
Regards.

I bet everything that the TFGE0027 error is related to the anticheat. The game would kick me out of any match with that exact code before connecting to them if I didn't include PROTON_USE_EAC_LINUX=1 in my launch options.

@bonkmaykrQ perhaps a more detailed log would prove useful in detecting the source of the issue for you. Also you should indicate which launch options you use, or really anything you've tried; it's pretty vague when you just say you have "set up your runtimes and launch options correctly".

My apologies. I am phoneposting at the moment from a dairy queen so I can't give it to you verbatim, but I have EAC enabled, NVAPI enabled, followed by gamemoderun %command%; pkill xpointerbarrier

The pkill is there because I use xinput and xpointerbarrier as a workaround to avoid input problems when in game, I use a very very old version of KDE.

@DAUNTIN I will try to enable secure boot. I normally have no use for it and so I don't go through the hassle of setting it up, but I will do so tonight.

I use linux-zen 6.10 on Arch if that matters.

Okay so that didn't work.
@DAUNTIN, the error message was 0027, NOT 0025. Are you sure you didn't get those confused?

To be clear, no other EAC game has any similar issue that I know of.

yes @bonkmaykrQ the error code was 0027, not 0025
When I didn't enable secure boot I would periodically get the error code 0027 and would have to restart my game to go away. After enabling secure boot I got it once and then it never showed up again, I've been playing like this for 3 weeks. To be more specific I never got kicked from a game. it only would show on the boot screen of the game.

to make sure secure boot is enabled use sudo mokutil --sb-state and it should say SecureBoot enabled

Also if you have 2 or more Steam accounts you are playing the game with, can cause 0027 to show up.

this is my system info from my other post to help compare my hardware to your
OS: openSUSE Tumbleweed x86_64
Host: B650 AORUS ELITE AX ICE
Kernel: 6.10.5-1-default
Packages: 3637 (rpm), 24 (flatpak) Shell: bash 5.2.32
Resolution: 2560x1440
DE: Plasma 6.1.4 wayland
WM: kwin
Theme: Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [GTK2/3]
Terminal: konsole
CPU: AMD Ryzen 9 7950X3D (32) @ 5.759GHz
GPU: NVIDIA GeForce RTX 4070 Ti
Drivers: 560.35
Memory: 12437MiB / 31536MiB

Sorry I can't help you more, this has been my experience so far.

@DAUNTIN
Secure boot is working, I chainload EFISTUB from rEFInd and if that doesn't work I load a .nsh script from /boot/ using the EFI shell. All binaries are signed with my own signature.

[bonkyboo@bonkmaykr-endeavour ~]$ sudo mokutil --sb-state
SecureBoot enabled
[bonkyboo@bonkmaykr-endeavour ~]$ sudo sbctl verify | grep "not signed"
(no output)

I noticed you're using Linux and not Linux-zen, I'll try booting the stock kernel and see if that helps.

i continue to see the game leak memory on arch with a amd rx 6700 gpu

overtime it doesnt let go of the memory of previous matches and so it just builds up till the game crashes which takes roughly 5 hours

on windows it will stay at 6gb of memory and never rlly goes above, i played for 3 hours but on linux if i play for 3 hours it will reach around 11gb of memory

i thought it was a mangohud issue at first but that isnt the case after testing through out the day

im also running experimental, kernel 6.10.10, mesa 24.2.2

EDIT: Doing more testing, after using x11 on kde plasma, gnome wayland, switching to my rtx 2060, the game is still leaking memory

EDIT AGAIN: moved to fedora kinote and its not happening anymore, rlly weird on what is causing this leak with this game only on arch for me :/

EDIT AGAIN AGAIN: when running flatpak steam the memory leak doesnt happen, it only happens on system steam on both fedora and arch

does anyone else get this issue if they play the finals for longer then 3 hours?

Having this game loading problem with its builtin EAC runtime, with a pop-up window Easy Anti-Cheat Launch Error said Failed to load the embedded resources.

Tried adding load parameter SDL_VIDEODRIVER=windows and/or PROTON_USE_EAC_LINUX=1, don't work.

OS: Arch Linux x86_64
Host: ASUS TUF Gaming A15 FA507RM_FA507RM (1.0)
Kernel: Linux 6.10.9-arch1-2
DE: KDE Plasma 6.1.5
WM: Kwin (wayland)
CPU: AMD Ryzen 7 6800H
GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q (driver: 560.35.03)
Memory: 14.62GiB
Swap: 10.0.GiB

Below are logs collected with ONLY one parameter PROTON_LOG=1.

steam-2073850 (proton 9.0-2).log

steam-2073850 (proton experimental).log

steam-2073850 (proton-experimental bleeding-edge).log

steam-2073850 (proton-hotfix).log

EDIT: change game language to English in Steam's per-game settings solved this, maybe this game's EAC files have some issue?

Since the 3.14.0 update, starting the game with gamemoderun PROTON_USE_EAC_LINUX=1 %command% -dx11 crashes. Without -dx11, it is starting, but then every map has some weird brown-ish fog on the lower sections and some broken textures (which I had before).

OS: Fedora Linux 40 (Workstation Edition) x86_64
Kernel: Linux 6.10.10-200.fc40.x86_64
DE: GNOME 46.5
WM: Mutter (Wayland)
CPU: Intel(R) Core(TM) i5-8600K (6) @ 4.30 GHz
GPU: NVIDIA GeForce GTX 1070 [Discrete]
Memory: 14.82 GiB / 31.27 GiB (47%)
Swap: 2.95 GiB / 8.00 GiB (37%)

Anything I could try to get this resolved?

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2372526586

Bro is playing a horror version of THE FINALS 💀

Vkd3d might have an issue with your gpu maybe? Since a 10 series gpu doesn't support the Vulkan extensions for vkd3d but maybe it could be fixed unsure

And with dx11/dxvk this is something that isn't rlly official by the finals so it makes sense that it's crashing, unsure if the dxvk team could fix that either but who knows, I'm not a developer so don't listen to me lol 🫠

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2372542624)
And with dx11/dxvk this is something that isn't rlly official by the finals so it makes sense that it's crashing, unsure if the dxvk team could fix that either but who knows, I'm not a developer so don't listen to me lol 🫠

Well -dx11 is something I used, until they did the Engine update.

Unfortunately the season update did not help with this... So I am unsure how to fix this.

Unfortunately the season update did not help with this... So I am unsure how to fix this.

There has to be a program interfering I am sure of it, sometimes I can play without any issue and other times the game won't let me connect. Not sure if there's a program on my computer being seen as "cheat" by AC. I am using GPU Recorder software on X11 maybe that is interfering with the anticheat I wonder.

I tried x11/xorg and Wayland, they bot behave the same. The problem is, that I don't know when this issue started happening, because the dx11 crashes forced me back to the normal Vulkan. So it might be easier to tackle that issue instead of whatever Vulkan has.

Having this game loading problem with its builtin EAC runtime, with a pop-up window Easy Anti-Cheat Launch Error said Failed to load the embedded resources.

EDIT: change game language to English in Steam's per-game settings solved this, maybe this game's EAC files have some issue?

If you solve this by change languages, then this is likety due to the game's EAC requesting fonts that not provided by wine/Proton:

<SteamLibrary-folder>/steamapps/common/The Finals/EasyAntiCheat/Localization/<locale-code>.cfg are files for EAC localization. Some of them don't quotes for fonts because they were already embbeded into EAC executeable file; the others use "system fonts" (in this scenario, fonts provided by proton) in this format:

windows_fonts:
{
	light = "<font_light>.ttf";
	regular = "<font_regular>.ttf";
	bold = "<font_bold>.ttf";
};

In order to make EAC correctly work, paste fonts quoted in <locale-code>.cfg (of course, the language you use) to: <SteamLibrary-folder>/steamapps/compatdata/2073850/pfx/drive_c/windows/Fonts, then you are good to go.

Languages affected are: ar_sa (Arabic), ja_ja (Japanese), ko_kr (Korean), th_th (Thai), tr_tr (Turkish), zh_cn (Simplified Chinese), zh_tw (Traditional Chinese)

So I have this weird problem where after I complete the first round and go into the second my fps tanks to around 60 (normally 170). It stays this way until I relaunch the game and is something I only notice in ranked not even in world tour. I am using a nvidia gpu, archlinux and bleeding edge proton. Here are my logs:

steam-2073850.zip

For anyone still having the TFGE0027 issue, I've found that running the game on an NTFS drive greatly increases the chances of the problem occuring.

I've also written this summary of common issues and known fixes/workarounds, I invite anyone with suggestions to add to it: https://bonkmaykr.xyz/content/discovery_lin.htm

For anyone still having the TFGE0027 issue, I've found that running the game on an NTFS drive greatly increases the chances of the problem occuring.

I've also written this summary of common issues and known fixes/workarounds, I invite anyone with suggestions to add to it: https://bonkmaykr.xyz/content/discovery_lin.htm

I have noticed that if you move your mouse when a match is loading, it shows me the error. so not moving the mouse fixes that! Once the match banner ie which map we are loading to is shown moving the mouse no longer creates a problem.

I'm having these major frame stutters every 2-3 seconds, DX12 and DX11 have the same issue

OS: openSUSE Tumbleweed x86_64 Host: B650 AORUS ELITE AX ICE Kernel: 6.10.5-1-default Packages: 3637 (rpm), 24 (flatpak) Shell: bash 5.2.32 Resolution: 2560x1440 DE: Plasma 6.1.4 wayland WM: kwin Theme: Breeze-Dark [GTK2], Breeze [GTK3] Icons: breeze-dark [GTK2/3] Terminal: konsole CPU: AMD Ryzen 9 7950X3D (32) @ 5.759GHz GPU: NVIDIA GeForce RTX 4070 Ti Drivers: 560.35 Memory: 12437MiB / 31536MiB steam-2073850.zip

Same here on rtx 3080...

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2437618411

Hey have you checked how much power it was using when it was stuttering. The issue I had was similar, but I believe the stuttering is because of the GPU weirdly getting power limited.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2447397735

Try this, should fix it:
https://www.protondb.com/app/2073850#huonYJWweC

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2447397735)

Try this, should fix it: https://www.protondb.com/app/2073850#huonYJWweC

Thank you for your reply but it does not work for me, the game still crash

I tried to switch the game from French to english and now it crash with a message :

But I can't do the memory dump.

OS: Arch Linux x86_64
Host: ASUS TUF Gaming A15 FA507RM_FA507RM (1.0)
Kernel: Linux 6.10.9-arch1-2Linux 6.12.1-arch-1-1
DE: KDE Plasma 6.1.56.2.4 WM: Kwin (wayland)
CPU: AMD Ryzen 7 6800H
GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q (driver: 560.35.03565.57.01 nvidia-open)
Memory: 14.62GiB
Swap: 16GiB

The game will freeze and crash when "RAY TRACING - NVIDIA RTX Global Illumination" in graphic settings set to any dynamic one. Set it to static (disable rtxgi) the game running fine.

Is it a game issue or vkd3d-proton or nvidia driver issue?

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2513604573

Are you able to get a Proton log for when it does this?

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2513975821)

sorry for forget of logging. higher graphic setting and/or longer game time will more likely trigger this freeze.

original log file is too big, compressed here:
steam-2073850.tar.gz

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2513975821)

sorry for forget of logging. higher graphic setting and/or longer game time will more likely trigger this freeze.

original log file is too big, compressed here: steam-2073850.tar.gz

I don't see anything really standing out in the log, can you reproduce the issue again and show the dmesg?
(journalctl -k | tail -8 > log.txt should be enough, just need to see if your NVIDIA GPU's logging an Xid error code at all)

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2515909853)

journalctl -k | tail -8 > log.txt only show me with these:

Dec 04 13:31:21 LAPTOP-NPL4IC5Z kernel: umip: wine_threadpool[5069] ip:7000005e04ec sp:22e8fc40: For now, expensive software emulation returns the result.
Dec 04 13:31:23 LAPTOP-NPL4IC5Z kernel: umip: wine_threadpool[5062] ip:7000005e04ec sp:1dd9fc40: SMSW instruction cannot be used by applications.
Dec 04 13:33:19 LAPTOP-NPL4IC5Z kernel: umip_printk: 113 callbacks suppressed
Dec 04 13:33:19 LAPTOP-NPL4IC5Z kernel: umip: wine_threadpool[5682] ip:7000005e04ec sp:179bef950: SMSW instruction cannot be used by applications.
Dec 04 13:33:19 LAPTOP-NPL4IC5Z kernel: umip: wine_threadpool[5682] ip:7000005e04ec sp:179bef950: For now, expensive software emulation returns the result.
Dec 04 13:33:21 LAPTOP-NPL4IC5Z kernel: umip: wine_threadpool[5456] ip:7000005e04ec sp:ba15f950: SMSW instruction cannot be used by applications.
Dec 04 13:33:21 LAPTOP-NPL4IC5Z kernel: umip: wine_threadpool[5456] ip:7000005e04ec sp:ba15f950: For now, expensive software emulation returns the result.
Dec 04 13:33:23 LAPTOP-NPL4IC5Z kernel: umip: wine_threadpool[5056] ip:7000005e04ec sp:1934fc40: SMSW instruction cannot be used by applications.

just in case, full dmesg is here:
dmesg_current.log

This game still leaks memory like crazy on my amd rx 6700, ryzen 7600 on arch, kde plasma wayland, takes around 5 to 6 hours to happen but it gets pretty stuttery when it happens, until it crashes, the finals takes a full 12gb of ram, doesnt go any further after being able to play the whole day without restarting which was around 10 hours

I tested to see if it's a Wayland KDE plasma problem and it happens on the cinnamon desktop also under x11, started at in menu 5.78GB, first match after in menu 7.24GB, second match after in menu 8GB, and just keeps going till the game will crash, it should be clearing itself but it aint, on the otherhand windows clears it perfectly everytime so i never reach the full capacity of my ram which is 32GB, trying flatpak steam also doesnt solve the problem and its not mangohud causing the issue either

i tried forcing dxvk on the game also the other day and it also has the memory leak, i also used vlk and the amdgpu-pro drivers which doesnt solve the issue either

It also happens on my rtx 2060 on the latest drivers from arch

Please oh please oh please fix the sensitivity being too low. This has been an issue since back 4 blood.

Wdym? Are you running x11 or wayland?

X11. Only proton-ge with its raw input patch will allow the sensitivity to get to a playable level. Otherwise is it too slow.

I realized this is a really delayed reply, but is this still a problem for you on Proton 9.0-x?

steam's game recording is broken for this game even overlay works

tried launch game with gamescope, it can record but cannot grab cursor, use --force-grab-cursor will cause screen tearing and frame drop

launch steam with gamescope and big picture mode, then launch the game, the in-game view is limited due to cursor range limited to window size

edit: after all these attempt, I reverted to default config mangohud %command% and now it works. I might look into logs later

edit later: occured again... need some time to fetch logs

edit after some attempts: wipe the in-game overlay data in steam's per game settings let it to record again...

It seems that on Intel Arc systems the crosshair is way too big and spans across the entire screen. I've seen another report of this in THE FINALS discord and they were also using an Intel Arc GPU leading me to believe that this issue could be exclusive to Intel ARC. Attempting to change video, resolution, or crosshair settings doesn't change anything.

On Windows everything works as expected.

GPU: Intel Arc A770
Video driver version: Mesa 25.0.0-devel (401b400de3f2d84bfb3436b7fed0fa90cf70b8e4)
Kernel version: 6.12.9
Link to full system information report as Gist: https://gist.github.com/yemouu/48ee0229619c4278556650bf97de388d
Proton version: Proton Experimental

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2592059739

Is it possible you could make a Mesa bug report for this? Given my computer runs THE FINALS fine and doesn't have this bug, (RTX 3060 Ti, previously an RX 5700 XT) it's highly likely a bug with ANV.

I made the bug report on mesa here

Since the S5 Update the game has been crashing quite often, anybody else facing this? Some others who are using fedora 41

steam-2073850.zip

I got the log for it and i could not find something that could cause the issue, atleast not myself.
I have tried all the known fixes from disabling RT to increasing the max VM memory. neither of them have fixed.
Already gave a report to embark about this as i suspect it may be related to the general bug this game has currently with crashing. But i can be sure about that

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2592059739

Should be fixed with https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33070

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2596247622

Just tested this and yep, it fixes the issue. Thanks!

Severe FPS Drops and Performance Degradation 😍

Symptoms

Initially (Stable 90 FPS):

• GPU Usage: 98%
• CPU Usage: 45%
• Frametime: Steady 10ms (max 12ms)

When FPS Drops (e.g., to 35 FPS):

• GPU Usage: 69%

• CPU Usage: 85%

• Frametime: Fluctuates around 15ms, causing stuttering and instability.

• FPS drops occur instantaneously from 90 to ~30 FPS, persist for a few seconds, and then recover as if nothing happened.

Observed On:

• GPUs: Both AMD and NVIDIA.
• Linux Distros: Arch, Pop!_OS, CachyOS, Fedora.
• Setups: Various configurations, including AMD and Intel CPUs.

Attempts to Fix:

1. Deleted shader cache and disabled Steam shader pre-caching — No improvement.
2. Added gamemoderun and forced DX12 — Minor improvement, not resolved.
3. Switched Proton and Wine builds — No significant difference.
4. Checked GPU power caps using nvidia-smi (NVIDIA) and monitoring tools for AMD.

Steps to Reproduce:

1. Launch The Finals on a Linux distro using Proton.
2. Play the game; FPS drops occur randomly across all settings and persist for a few seconds before recovering.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2598859337

Yes I am having an issue that sounds very similar to this since today. It is usually triggered by spawning in most of the time and seems to occur in bursts with the lag getting so bad it freezes and then returns to normal. When its not stuttering like this, the framerate is flawless for a while but then it slowly becomes a stuttery mess. While it is stuttering, I have noticed my overall CPU usage spike from 80 all the way 100% and my GPU usage significantly decreases.

I also get these issues but only today. Yesterday things were working all good.

If i look at amdgpu_top the graphics pipe etc. drop from 60-80% suddenly to 30%. It's like some weird powersaving mode out of nowhere.

Edit: The game FPS counter looks like this during the hiccup

CPU bottleneck? Something weird is going on.

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.80
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
driverInfo = Mesa 24.3.3

Edit2:

Took a screenshot of mangohud during the game. I tested in practice range, and I have most settings on low because I want more fps.

I ran steam through terminal and during the first slowdown this appeared

Fossilize INFO: Overriding serialization path: "/mnt/ba9ce604-52eb-4152-8b2e-0941036b2ddc/SteamLibrary/steamapps/shadercache/2073850/fozpipelinesv6/steamapprun_pipeline_cache".
[0118/023838.983:ERROR:dxva_video_decode_accelerator_win.cc(1447)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)
[0118/023838.984:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled
Fossilize INFO: Overriding serialization path: "/mnt/ba9ce604-52eb-4152-8b2e-0941036b2ddc/SteamLibrary/steamapps/shadercache/2073850/fozpipelinesv6/steamapprun_pipeline_cache".

On subsequent slowdowns there was nothing

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2598859337

If I have time today, I'll test the game out here as I don't remember getting this problem on my machine.

As a side-note, if you're not using hardware acceleration in Steam, try closing the Steam Window while the game is running and see if things improve, I found my framerates occasionally got worse if I left it open.

(I have hardware acceleration off due to a bug on NVIDIA that causes Steam to corrupt rendering)

EDIT: Also see if the spikes happen when using Reflex on NVIDIA drivers.

I can confirm this issue has popped up for me out of nowhere today as well. I'm on Arch Linux, using Proton Experimental, GPU is RX 6700XT and CPU is 3700X. Doubt this issue is NVIDIA related.

Using mesa-git btw (so mesa 25.0).

Did an update push to the game today? Didn't notice.

I seem to be getting the same issue.
CPU: 5950x
GPU: 6800xt
Arch Linux @ 6.12.8-zen1-1-zen

[  695.113054] umip_printk: 115 callbacks suppressed
[  695.113058] umip: wine_threadpool[6918] ip:70000055e13c sp:8c081f920: SMSW instruction cannot be used by applications.
[  695.113064] umip: wine_threadpool[6918] ip:70000055e13c sp:8c081f920: For now, expensive software emulation returns the result.
[  697.209718] umip: wine_threadpool[3807] ip:70000055e13c sp:67adfc30: SMSW instruction cannot be used by applications.
[  697.209725] umip: wine_threadpool[3807] ip:70000055e13c sp:67adfc30: For now, expensive software emulation returns the result.
[  699.217415] umip: wine_threadpool[5555] ip:70000055e13c sp:50e40f920: SMSW instruction cannot be used by applications.

seems to be popping up in the kernel logs and seems to be the direct cause of the frame drops at least in my case.

EDIT:
After further investigation I tried adding clearcpuid=514 to my kernel paramters inspired by #2927. Unfortunately while that did resolve the messages in the kernel log it did not fix the severe framedrops (accompanied by low GPU utilisation). It may still be software emulation as reported as before but not reporting it.

EDIT2:
No logs seem to be generated when the spike hits (terminal output of steam).
I do see

Fossilize INFO: Overriding serialization path: "/home/nick/.local/share/Steam/shader_cache_temp_dir_d3d11_64/fozpipelinesv6/steamapprun_pipeline_cache".
fsync: up and running.
Fossilize INFO: Overriding serialization path: "/home/nick/.local/share/Steam/shader_cache_temp_dir_d3d12_64/fozpipelinesv6/steamapprun_pipeline_cache".

Which matches @p0ryae, but I only have gotten it on launching the application and not when any spikes hit. There is no mention of msvproc.dll or paththrough.

EDIT3:
Rolling back proton to 8.0-5 does not resolve the issue, infact seems to cause a hard freeze after launch. It seems to print

[ 1252.139423] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d26e60
[ 1252.144232] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:cca456
[ 1252.161437] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d78438
[ 1252.166883] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d67af1
[ 1252.173073] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d6a846
[ 1252.181403] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d6dd0f
[ 1252.197259] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d75625
[ 1252.203934] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d6c7d6
[ 1252.208555] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d6972e
[ 1252.213484] Discovery.exe[14827] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:1707c3e2c cs:33 sp:b9d268 ax:b9e680 si:b9e680 di:d69725

followed by the umip logs reported from before.

The latest version of proton experimental seems to also print the Discovery.exe logs before the firm umip logs but does not print it on any group umip logs after that so I am unsure if it is related.

Horrible Horrible lag seemingly overnight for no apparent reason. Went from 120fps yesterday to 13 fps today.

I also just suddenly started experiencing this today.

Every time it appears to happen when one would expect the game to dispose of textures.

I noticed there was a shader update today, and Fedora got a mesa update yesterday.

AMD 7900xtx

Update:

Downgrading to mesa-dri-drivers-24.2.4-1.fc41.x86_64 did not resolve the issue, nor did switching to Proton-9.0 from Experimental.

I think it has something to do with Fossilize and msvproc.dll? The following log is generated constantly (usually when the spike hits):

Fossilize INFO: Overriding serialization path: "/home/porya/.local/share/Steam/steamapps/shadercache/2073850/fozpipelinesv6/steamapprun_pipeline_cache".
[0117/183510.061:ERROR:dxva_video_decode_accelerator_win.cc(1447)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)
[0117/183510.062:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled
Fossilize INFO: Overriding serialization path: "/home/porya/.local/share/Steam/steamapps/shadercache/2073850/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/home/porya/.local/share/Steam/steamapps/shadercache/2073850/fozpipelinesv6/steamapprun_pipeline_cache".

Edit: Thanks to @nonl4331 for cross-checking. Issue might need a full proton log instead of steam logs then.

No such luck doing the basic debugging:

• Revert kernel version
• Revert mesa version
• Switching from Experimental to Proton-9.0

Looking in proton logs, the application is throwing a ton of errors, and proton is complaining about a missing module. Here is the proton logs with the stack traces captured at a point where the game dropped to 5fps.

Key information from PROTON_LOG=1 being

944.859:01c8:03b0:warn:vkd3d-proton:vkd3d_acceleration_structure_convert_inputs: Application is using IndexBuffer = 0 and IndexFormat != UNKNOWN. Likely application bug.
...
954.998:01c8:0240:trace:seh:call_vectored_handlers calling handler at 00006FFFEFA3C560 code=80000003 flags=0
954.998:01c8:06d8:trace:seh:sigsys_handler SIGSYS, rax 0x15, rip 0x7000005db8c8.
954.998:01c8:0240:trace:seh:call_vectored_handlers handler at 00006FFFEFA3C560 returned 0
954.998:01c8:0240:trace:seh:call_vectored_handlers calling handler at 00006FFFFC8D0680 code=80000003 flags=0
954.998:01c8:0240:trace:seh:call_vectored_handlers handler at 00006FFFFC8D0680 returned 0
954.998:01c8:0240:trace:seh:call_vectored_handlers calling handler at 00006FFFFDAEC060 code=80000003 flags=0
954.998:01c8:0240:trace:seh:call_vectored_handlers handler at 00006FFFFDAEC060 returned 0
954.998:01c8:0240:warn:seh:virtual_unwind backtrace: 0000700000574648: unknown module.

finals-proton-errors.log

Seems to be vkd3d related. @mikeymop I think you should report this in https://github.com/HansKristian-Work/vkd3d-proton and see if there's any comment over there from @HansKristian-Work.

Seems to be vkd3d related. @mikeymop I think you should report this in https://github.com/HansKristian-Work/vkd3d-proton and see if there's any comment over there from @HansKristian-Work.

Thanks I have opened !2293 and mirrored the same information there.

I also have this issue and couldn't solve it despite all troubleshooting attempts:
Proton versions: 9.0, hotfix, experimental, exp. bleeding edge. I cannot launch the game using Steam installed on Wine, EAC fails to load.
Kernel: 6.12.9-zen, 6.6.70-lts
AMD GPU core clock set to 2276 MHz and memory clock to 1124 MHz with corectrl
Launch parameters: LD_PRELOAD="" SteamDeck=1
Specs are AMD Ryzen 5 7600, 32 GB RAM, Radeon RX 7700 XT, Arch Linux

I am fairly certain this issue is not directly related to Proton or vkd3d. I'm pretty sure its related to the 5.5.0 patch of the game that was released yesterday.

I have reported the issue to the developers)and am waiting for a reply. (probably won't get any but eh worth a try)

Also the same bug occurs when running the game in dx11 mode so it isn't a vkd3d issue. Its something related to the game itself.

It seems like some sort of weird CPU bottleneck but doesn't make sense due to the fact that perf-top shows no difference between the times when the game runs normally and the game stutters.

The game is currently unplayable for me. The gpu doesnt use more than 10w power. The problem is not with me. Other games can use up to 80w power. The same problem occurred a few weeks ago. The problem was solved after updating the packages.
The game was updated recently. I also updated my all packages . I am currently experiencing the same problem again. I do not know if the problem is from Proton, game or the Nvidia drivers. I think the problems are caused by the nvidia drivers.

I didn't update the game or any packages at all and it only popped up yesterday. Was working the day before. Think it must be a patch to either the game or steam (although the game appears to have had no patches in that time).

Anecdotally, I have noticed that the game is not quite as aggressive with pre-compiling shaders as it used to be. The slow-downs seem to happen in areas that have not been loaded in a while, or even sometimes while the game is in a loading screen. I feel it is related to fossilize and/or VKD3D, mainly some issue with the shader cache.

I see messages about the vsyscall denied thing, but I have been seeing that in dmesg for a while now and had no problems from it. Recently though when I looked at the game's trace for problems, I have definitely seen that "module not found" error somewhere.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2599639474

I believe that your suggestion that it is the fault of the 5.5.0 patch is incorrect. I was playing hours after the patch with no issues at all. I was playing for around 3 hours straight with no crashes or fps issues. The issue has only appeared today, there have been no updates that I know of since then.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2599659371

I also noticed that it was not as aggressive. Normally I need to to a update on the shaders for every update of proton (I'm on the bleeding edge version) but that was not something I had to do this time.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2599601123

If you install your steam through wine, I don't know if anticheats would accept it or not. This method of steam install is rare used (and probably unsupported), maybe can you try install steam from repo or flatpak?

@sklynic I used Steam on Wine as a last resort when all proton versions failed (had the FPS issue). I normally use Steam from repos but I didn't try flatpak.

FWIW, I managed to play the game just fine on Thursday with the 5.5.0 update. Had zero issues. But Friday it started doing this stuttering.

Maybe the steam linux runtime updated?

FWIW, I managed to play the game just fine on Thursday with the 5.5.0 update. Had zero issues. But Friday it started doing this stuttering.

Maybe the steam linux runtime updated?

I'm not actually using the steam runtime. Running native libraries (which hadn't been updated when the bug started happening) here so it wont be the steam runtime I would think.

I noticed also that whenever the low fps happens, textures look a bit blurry. But when textures load in, it stops.

If I set textures to epic, the stuttering happens less frequently, but takes longer. With textures set to low, theres more frequent fps drops, but they take way less time.

No luck with the latest version of proton GE that came out yesterday.

I noticed also that whenever the low fps happens, textures look a bit blurry. But when textures load in, it stops.

If I set textures to epic, the stuttering happens less frequently, but takes longer. With textures set to low, theres more frequent fps drops, but they take way less time.

Great observation, and it aligns with my hypothesis that it has to do with textures being loaded and unloaded.

In the logs vk3d shows that the game spawns threads that throw exceptions. So maybe the threads that are crashing are the same threads that are loading the textures from disk to the GPU.

I feel like it's worth noting that, on my computer at least, I get the exact same problem on both Linux & Windows.

Before THE FINALS 5.5.0, Fortnite had the exact same bug introduced in it's v33.11 update (yes, 🚽 that one).

I have also noticed textures in The Finals not staying loaded when they should be, or taking longer than usual to load. Strangely, I was able to make the problem go away during one game session only by sheer luck, but every other time has been absolutely unplayable.

I believe this is an upstream bug in Unreal Engine.

I've noticed that Alt Tab sometimes gets temporarily better. I'm not sure what this has to do with it.

P.S. Arch Linux last, GE Proton 9.22 and 9.23 and Experimental

Also having this issue
I've noticed while trying to troubleshoot this that disabling Intel SMT in my case makes this issue way worse, so its probably something thread related.
With SMT I get 50~ fps during the stutter and 100~ fps normally.
Without SMT the stutter fps drops all the way down to 20-30 fps (and the textures look very blurry and are noticably slow to load).

On: NixOS Unstable, Proton 9.0-4/Experimental/GE 9.22, using steam flatpak

The gpu doesnt use more than 10w power.

Ive also observed the same behaviour, running nvidia-smi during the stutter showed me 11w power used.

In my case, very low GPU usage accompanied by consistently low FPS was caused by split lock mitigation. Disabling it with sudo sysctl -w kernel.split_lock_mitigate=0 when the game is on fixes the issue.

More info here: https://wiki.archlinux.org/title/Steam/Game-specific_troubleshooting#Split_lock_detection/mitigation

In my case, very low GPU usage accompanied by consistently low FPS was caused by split lock mitigation. Disabling it with sudo sysctl -w kernel.split_lock_mitigate=0 when the game is on fixes the issue.

I've had split lock off (because i wanted to play NFS: Heat and Heat with split lock on is a performance nightmare) for the entire time, I've had it off before the issue cropped up, and after, it doesn't do anything for me unfortunately.

In my case, very low GPU usage accompanied by consistently low FPS was caused by split lock mitigation. Disabling it with sudo sysctl -w kernel.split_lock_mitigate=0 when the game is on fixes the issue.

More info here: https://wiki.archlinux.org/title/Steam/Game-specific_troubleshooting#Split_lock_detection/mitigation

Its not consistent though. For a few minutes it performs great and then when it has to load textures it stutters until its loaded them all again.

In my case, very low GPU usage accompanied by consistently low FPS was caused by split lock mitigation. Disabling it with sudo sysctl -w kernel.split_lock_mitigate=0 when the game is on fixes the issue.
More info here: https://wiki.archlinux.org/title/Steam/Game-specific_troubleshooting#Split_lock_detection/mitigation

Its not consistent though. For a few minutes it performs great and then when it has to load textures it stutters until its loaded them all again.

My experience has been smooth. GPU utilization is slightly lower than usual (~90%) but the low FPS and stuttering issues that started around Friday are gone.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2600987430

Ill try it and come back with the result. Seems like a strange thing to be enabled by default although dmesg says stuff about CPU performance scaling so I guess its worth a try.

Setting kernel.split_lock_mitigate=0 seems to have no effect on fixing the bug for me.

Setting kernel.split_lock_mitigate=0 seems to have no effect on fixing the bug for me.

made it worse for me

NixOS Unstable | AMD 7700XT | AMD 5700X3D

Setting kernel.split_lock_mitigate=0 seems to have no effect on fixing the bug for me.

I've checked and I don't even have that option compiled into my kernel I guess because its not there.

Sadly, split_lock_mitigate doesn't fix it for me either (I do have kernel above 6.2, and the option is compiled in my kernel).

Replying to[#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2600970302)

split_lock_mitigate didn't change anything to the finals for me either, but regarding to nfs: heat did you tried this before? https://github.com/Octanium91/NFS_Heat_CPU_Load_FIX

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2599639474

Just wondering if you got a reply from the developers. I don't know much about wine but I would like to know why this bug which looks like it's in unreal engine is only an issue for linux users (or very few windows users)?

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2601633323

I received a pretty standard answer. I described the symptoms of the problem and provided several links to show the global nature of the problem (such as reddit, github, protondb, steamcommunity). Embark's response:

Thanks for reaching out to THE FINALS support team.

We appreciate knowing that you were playing the game through Linux and we're sorry to hear that you're having issues with the performance of the game recently. However, we regret to inform you that any errors or issues you've encountered may be due to the fact that Linux is not officially supported by us, thus we cannot guarantee the effectiveness of any possible troubleshooting as our official support for PC is based on Windows.

Rest assured that we have forwarded this information to the relevant department for consideration in future updates. Your feedback is invaluable to us as we strive to improve the gaming experience for all players.

We appreciate knowing that you were playing the game through Linux and we're sorry to hear that you're having issues with the performance of the game recently. However, we regret to inform you that any errors or issues you've encountered may be due to the fact that Linux is not officially supported by us, thus we cannot guarantee the effectiveness of any possible troubleshooting as our official support for PC is based on Windows.

I have also gotten the same response word for word.

I have gotten the same response for my ticket, while it's disheartening we should still make these tickets so Embark understands how many people this is affecting.

This is kinda getting off-topic now but @yesdotwmv I don't think more tickets is going to help. It's not helping us and Embark would just find it annoying. I think the better way to show how many people this is affecting would be going to the reddit or discord.

I'm getting this problem on Wayland. Anybody else with the same issue on X11?

I'm getting this problem on Wayland. Anybody else with the same issue on X11?

The majority of us :)

I tried disabling both Energy Saving, and changed the TAAU to FSR2. On the command screen and at startup it was 1fps, but in game after loading it seems to be better minimum fps and game response.

I also have this issue in the main menu, Practice Range and during the matches. When the frame drops happen I seem to get degraded desktop performance too - resizing windows feels sluggish, btop refreshes much slower, and looking at the processes not only The Finals go up but also others too - Steam and Konsole appear to use 100% of one core each, up from their normal use of ~10%. When it happens my GPU usage goes down to mere 20%.
I've tested -dx11 and -dx12 flags and issue appears in both scenarios. I've tried different Proton versions - Wine-Tkg 10, Proton 9.0, Proton Experimental, different kernels - 6.12.9-zen, 6.12.10-zen, 6.13-cachyos-rc and nothing seems to change.
CPU: Ryzen 7 5700X3D
GPU: RX 6700 XT

I also see a decrease in GPU usage. I played an 8 minute session in quickcash and got some graph during the game.

Black: CPU temperature
Purple: CPU usage
Red: GPU temperature (hotspot)

Places where there is a decrease in GPU temperature correspond to frame drops in the game. I had already launched psensors while playing the finals (when everything worked fine), my hotspot holds a stable graph with a small change (due to cooling as I understand)

The peaks of the red graph are 91 degrees Celsius, and during the drop ~60 degrees Celsius.

During this session, FPS dropped to 28-34, from a stable 140.

CPU: 7900X3D
GPU: 7900GRE
Proton Experimental
6.11.11-1-MANJARO

Anyone tried disabling FSYNC or disabling ESYNC as well?

At this point, I think the fact that I updated nothing on my system and the next day the problem appears even though it was working fine the day before (a couple others have had the same experience) means that either steam or the finals must have performed some remote update.

At this point, I think the fact that I updated nothing on my system and the next day the problem appears even though it was working fine the day before (a couple others have had the same experience) means that either steam or the finals must have performed some remote update.

Definitely it was a "hidden" update. Because I played after the patch on the finals for quite some time. After 6 hours I turned on the computer again, and the problems with FPS began. I definitely did not update the system, the game or download updates on proton

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2603143731

So then it is likely unreal engine, easy anticheat, or direct3d in that case? And I guess whatever it is has a unique bug with all linux setups. I don't think it was steam runtime because I don't have that enabled so I guess it isolates it to executable files and dlls that the finals uses in its prefix. I don't think its too unbelievable that one of them has updated itself.

Ok im getting fixme:ntdll:NtQuerySystemInformation (0x000000a3,0x164e0f957,0x00000001,(nil)) stub in the log when the stutters happen it seems.

There seems to be a few problems in the trace. Seems like the update is causing something to send bad syscalls?

I noticed the problem just now, and I thought it was something related to my NixOS/Nvidia configuration, so I tried a lot of changes. Different kernels (default 6.12, Zen, Xanmod, Cachyos) and runner versions (Proton-GE, Proton-9.0-4,Experimental and Hotfix).

Also tried with different launch parameters through Steam. Unfortunately, nothing improved the performance.

Hopefully this game will not follow Apex Legends and end "support" on Proton.

i5-13450HX
RTX 4050
NixOS (unstable)

The issue only occurs with -dx11 flag in my case. Please remove it and you should get rid of the stuttering.

Runs fine now, same goes for everyone else in #bug-reports on the Discord server.

Proton Experimental

Can confirm that it runs fine now, I'm using Bleeding Edge Proton on Arch Linux (I use arch by the way) with a NVIDIA GPU. I didn't have any updates so I'm guessing a hidden patch. Thanks Embark ❤

Yeah there was a 1gb patch yesterday. Check steamdb.

Hmmm, that's odd because I never updated. I made sure that I would stop updates. It doesn't matter, I'm happy I can play again.

Yep stuttering is fixed for me.

Haven't received any game update and I'm using the same proton-ge-23. It must have been a server-side bug affecting the client

It's fixed for me too. Only tested Proton Experimental

fixed with any proton wasnt a protof fix i think

Well it seems embark just pushed an update 5.6 and the games borked again . TLDR game does not start . Deleted Prefix and tried with proton exp, hotfix and stable. all have the same behavior.
CachyOS + KDE + Kernel 6.13 + Steam Runtime

After today's patch 5.6.0, the game simply won't turn on. The anti-cheat initializes and then nothing happens. Has anyone else encountered this?

Proton Experimental
Proton 9.0-4

The joy did not last long

Game worked fine for one day and then broke with 5.6.0.

Same issue happening on Cachyos, RX 6700 10GB, Kernel 6.13, Mesa 24.3.3

Here is a log
https://drive.google.com/file/d/1abTJCtzg_LGf8HOeBRjyjtn2FD3MFmFL/view?usp=sharing

Same thing here. Just crashing when initialising EAC. Tried without any environmental variables. Tried disabling fsync.

Could it be that vsyscall error finally causing a problem?

Yep its not EAC. If you look in dmesg you will see that Discovery.exe is having that vsyscall error which means it is getting to the game's executable itself. Checking the logs for EAC in the prefix and they also seem to be successful with no errors.

+1
our time is gone

Fixed the dmesg vsyscall error with the kernel parameter vsyscall=emulate. Still getting crashing.

https://steamcommunity.com/app/2073850/discussions/0/595138831417625880/

I think its another upstream issue because its affecting a lot of windows users as well. Should be patched soon.

They announced on Discord that there is a hotfix to fix an issue for PCs either an outdated driver. This might also fix this issue.

This unfortunately didnt fix the issue.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2607617349

Yeah I was on a reddit thread and somebody mentioned that that embark dev said the fix was vcruntime update or something on the discord server.

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2607617349)

Yeah I was on a reddit thread and somebody mentioned that that embark dev said the fix was vcruntime update or something on the discord server.

Just checked this, i updated both vcrun2022 and mfc140, both were already installed and repairing them didnt fix it here. (so the script steam uses already installs these for us

We just have to wait

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2607836139

is this about the hotfix that just got released or is there another one incoming?

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2607850447

I presume by "the latest update" they mean the major patch 5.6.0. As for the "hotfix", I think there is only one for now.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2607850447

I presume by "the latest update" they mean the major patch 5.6.0. As for the "hotfix", I think there is only one for now.

5.6.1 is the hotfix.

To save you the time, the game still crashes on launch. I believe proton will need the updated libraries mentioned in the hotfix changelog

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2608185295

5.6.1 is an hot fix for windows related issues, we have to wait 5.6.2.

The game might work again on the just updated Proton Experimental [bleeding-edge] branch (see https://github.com/ValveSoftware/Proton/wiki/Proton-Versions , Proton Bleeding Edge for details how to select it).

Completely untested, only made sure the game starts and gets to Practice Range for me.

can confirm bleeding-edge boots, no issues so far. latest GE does not.

Bleeding edge seems to fix these issues. Thanks Proton devs!

Same here, the game starts and I was able to play a couple of matches without issues

Whoever fixed the issue in bleeding edge is a legend, thank you

yeah bleeding edge working a dream - no launch options, runs like gravy. Thanks devgents

The game still doesn't work for me. I'm using proton experimental

In your steam library, under tools, go to properties of Proton Experimental then Beta, and opt in to bleeding-edge in the dropdown

In your steam library, under tools, go to properties of Proton Experimental then Beta, and opt in to bleeding-edge in the dropdown

That you for writing the steps and thanks to the proton devs for fixing this so fast. Man I love FOSS.

I can log in now. But I'm getting kicked off the servers.

I can log in now. But I'm getting kicked off the servers.

For me, restarting the game or rebooting my PC seems to fix this.

In your steam library, under tools, go to properties of Proton Experimental then Beta, and opt in to bleeding-edge in the dropdown

Thank you!

Lag issues with proton versions newer that 9.0-4. (Solved)

When the game launches everything works as expected, however, after 2-3 matches (usually in the middle of the game) my character movement becomes very choppy. It kind of looks like my framerate drops to somewhere between 10 and 20 fps, but if I stop moving I can see that everything else in the game is as smooth as was (particle effects, movement of other players or objects, etc.). This also looks like it is specifically the player controlled character that starts to lag and not the camera because it moves smoothly when inspecting other players and, I find thins really funny, my character movement is choppy in the menus (when I spin them with the mouse). This persists until the game is restarted.

The issue did not occur on 9.0-4 but unfortunately the game stopped launching with that version after latest game update.

I experienced this issue before but when season 5 dropped the game started crashing with proton-experimental and I switched to 9.0-4, where the game worked again and the issue was also gone.

Updated observations

I was wrong about the FPS, it actually does go down, but only during character interactions, including spinning them in the main menu. It has been pointed out that it was specifically the frame time that went up.

The issue does not happen with a (freshly plugged in) controller but continues to happen with keyboard and mouse, even if re-plugged.

Solution (new)

The game must be launched with LD_PRELOAD="" environment variable. It can be assigned in game properties in the launch arguments line like so LD_PRELOAD="" %command%. It is possible that the %command% part is not needed if it is not followed by anything else, but in my case I also used -dx11. If you are using both variables and arguments you definitely need the %command%.

Specs

Probably irrelevant.

Intel i7-6700k
Corsair DDR4 ram, 32Gb
Nvidia GTX 1070, driver 565.77
Linux 6.6, Wayland, flatpak Steam

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2613035961

Sounds a bit like the issue that was fixed with LD_PRELOAD=""

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2613035961

There is a separate nVidia specific issue that can cause stuttering. Its related to the nvidia GPU not going above 40w.

You can verify if this is the cause by looking at nvidia-smi while the game is running.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2613086387

This is an issue i have had for so long, any idea what the fix is? I tried hiding the gpu but that just made my game periodically crash. This is on a 4060 max q

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2613086387)

There is a separate nVidia specific issue that can cause stuttering. Its related to the nvidia GPU not going above 40w.

nvidia-smi shows well above 40W immediately after launching the game, so this must be a different issue.

Tbh, doesn't sound like it is a GPU issue because I can see that my character is animating smoothly when I spin them but the spinning itself is choppy. I'll update original post with more PC specs.

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2613086387)

There is a separate nVidia specific issue that can cause stuttering. Its related to the nvidia GPU not going above 40w.

nvidia-smi shows well above 40W immediately after launching the game, so this must be a different issue.

Tbh, doesn't sound like it is a GPU issue because I can see that my character is animating smoothly when I spin them but the spinning itself is choppy. I'll update original post with more PC specs.

One other suggestion, I don't have nvidia anymore, but when I did I had better luck with negativo17's driver.

Would you be open to trying this driver instead? I prefer the dkms version.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2613035961

This game has a habit of increasing ram useage after every match by 1-2GB like at the last round of ranked you might see ram useage at 12GB or even 15GB .

i have the same behaviour on my rx 570 4gb . i have tried all kinds of proton version . steam native or runtime same issue , tried linux mint(xorg) or cachyos kde(wayland) . could be due to the fact i am using older hardware (pcie3) amd 5 3600

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2614457195

Sounds like a memory leak have you tried using the flatpak varient of steam?

The game takes my system up to about 10-12Gb and sits there. The motion lag began at 12/32 last time I tested. After a match ended the memory went back to 11 but the motion lag in the main menu persisted. Tbh, this does sound like a memory leak but it is not as easy as ram running out.

I am already on flatpak version of Steam

Oh have you tried putting the LD preload flag ? In the launch options

I had some bouncing of my and sometimes other people's characters yesterday too. I thought it was general server problems and different ping. But it's still not clear from which side of the problem.

The problem I described here does not happen on PS5 even during server lag and did not on proton 9.0-4, I think it is unlikely that it was just the earlier part of season 4 that did not have this issue, which is when I was using that version of proton

I forgot about the LD_PRELOAD="" suggestion. A quick search suggested that it is not possible to add environment variables to steam games. Could someone please post a short instruction list for how to do this?

I forgot about the LD_PRELOAD="" suggestion. A quick search suggested that it is not possible to add environment variables to steam games. Could someone please post a short instruction list for how to do this?

It's can be added by going to the game in question opening the settings and you will see a blank area named lauch options adding it here is all you need to do

Thanks @izerotwo. I thought these launch options were just appended as a single string to the launch command, something like wine thefinals.exe -- --run-well --dont-lag-on-linux so I thought the variables would have to be set separately in a string that is prepended, I'll try it out and check if anything changes

The Finals Update of Today, 5.8.0 bricked the game again.

Starts and can play several minutes but crash in the first round playing. Proton experimental and bleeding edge doesn't fix that. LD_Prelaod don't work as well.

I have the same problem here is the proton log.
Crash happens during a match with unknown reason when and why.

steam-2073850.zip

Confirmed, proton 9.0-4 and hotfix were not starting the game at all an hour ago, testing proton-experimental just now started the game but crashed mid match, I informed the teammates I might crash thanks to other replies here

proton experimential (no bleeding edge), crashes after apporiximately 10 minutes. this crash can be reproduced constantly.

nothing in proton log except these thing (they are basically the same message to game's own crash report :( )

47801.721:01c4:02a4:warn:seh:OutputDebugStringW L"LowLevelFatalError [File:.\\Runtime/Launch/Private/Windows/LaunchWindows.cpp] [Line: 76] \nSECURE CRT: Invalid parameter detected.\nExpression: Unknown Function: Unknown. File: Unknown Line: 0\n\n"
47801.721:01c4:02a4:warn:seh:dispatch_exception L"LowLevelFatalError [File:.\\Runtime/Launch/Private/Windows/LaunchWindows.cpp] [Line: 76] \nSECURE CRT: Invalid parameter detected.\nExpression: Unknown Function: Unknown. File: Unknown Line: 0\n\n"
47801.721:01c4:02a4:warn:seh:OutputDebugStringA "LowLevelFatalError [File:.\\Runtime/Launch/Private/Windows/LaunchWindows.cpp] [Line: 76] \nSECURE CRT: Invalid parameter detected.\nExpression: Unknown Function: Unknown. File: Unknown Line: 0\n\n"
47801.721:01c4:02a4:warn:seh:dispatch_exception "LowLevelFatalError [File:.\\Runtime/Launch/Private/Windows/LaunchWindows.cpp] [Line: 76] \nSECURE CRT: Invalid parameter detected.\nExpression: Unknown Function: Unknown. File: Unknown Line: 0\n\n"
47801.722:01c4:02a4:warn:seh:dispatch_exception backtrace: --- Exception 0x4000.
47801.722:01c4:02a4:warn:seh:dispatch_exception unknown exception (code=4000) raised
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 00006FFFFFC1CF57: L"kernelbase.dll" + 000000000000CF57.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 0000000140234116: L"Discovery.exe" + 0000000000234116.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 00000001401D4296: L"Discovery.exe" + 00000000001D4296.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 0000000140175BC8: L"Discovery.exe" + 0000000000175BC8.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 0000000143CAC904: L"Discovery.exe" + 0000000003CAC904.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 00006FFFFFA64B4B: L"ucrtbase.dll" + 0000000000084B4B.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 0000000140002A4A: L"Discovery.exe" + 0000000000002A4A.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 000000014000BD6E: L"Discovery.exe" + 000000000000BD6E.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 00000001480DA5FE: L"Discovery.exe" + 00000000080DA5FE.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 00000001480D0581: L"Discovery.exe" + 00000000080D0581.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 0000000140089BDE: L"Discovery.exe" + 0000000000089BDE.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 00000001400AC03D: L"Discovery.exe" + 00000000000AC03D.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 000000014024DAD5: L"Discovery.exe" + 000000000024DAD5.
47801.722:01c4:02a4:warn:seh:virtual_unwind backtrace: 000000014024DA16: L"Discovery.exe" + 000000000024DA16.

proton log here (compressed):

steam-2073850 TF5.8.0 Proton-Experimential.tar.gz

I can't get any further than the anti-cheat

The crash mid-match might be fixed in the just updated Proton Experimental [bleeding-edge] branch (see https://github.com/ValveSoftware/Proton/wiki/Proton-Versions , Proton Bleeding Edge for details how to select it). The first version with the fix is experimental-bleeding-edge-9.0-159290-20250205-p66871e-wf62aeb-dcf946e-v1fb838 .

The crash mid-match might be fixed in the just updated Proton Experimental [bleeding-edge] branch (see https://github.com/ValveSoftware/Proton/wiki/Proton-Versions , Proton Bleeding Edge for details how to select it). The first version with the fix is experimental-bleeding-edge-9.0-159290-20250205-p66871e-wf62aeb-dcf946e-v1fb838 .

Tested it, resulting in In-Game Error: TFGE0027 "Disconnected from Server" after going in Queue.

The crash mid-match might be fixed in the just updated Proton Experimental [bleeding-edge] branch (see https://github.com/ValveSoftware/Proton/wiki/Proton-Versions , Proton Bleeding Edge for details how to select it). The first version with the fix is experimental-bleeding-edge-9.0-159290-20250205-p66871e-wf62aeb-dcf946e-v1fb838 .

Tested it, resulting in In-Game Error: TFGE0027 "Disconnected from Server"

This can sometimes happen randomly, just restarting the game will fix this.

So far, I still don't even have the launch working. Tried changing Proton branches, checked file integrity, restarted Steam many times. No response.

So far, I still don't even have the launch working. Tried changing Proton branches, checked file integrity, restarted Steam many times. No response.

That's weird, do other games lauch?

So far, I still don't even have the launch working. Tried changing Proton branches, checked file integrity, restarted Steam many times. No response.

That's weird, do other games lauch?

Single games work. But online seems to be having problems. Except Deadlock. Apparently Proton c network does not work.

Coincidentally, it was me. Disabling DNS Crypt but leaving DNS in systemd-resolv. Surprisingly it only affected Proton Steam.

New observation regarding motion lag issue. I noticed that it is not just the camera motion, the FPS actually drops but this still happens only during interaction (including holding the mouse button down to spin the character in main menu). This seems much less weird now. Could it be that at some point some IO loop fails and starts spamming messages internally that cause the slowdown? Did anything related to that change between proton 9.0-4 and current hotfix?

Also, LD_PRELOAD="" did not solve this (or change anything that I observed). Screenshot of how I did it because it still looks wrong to me and maybe it just didn't apply.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2646306521

You need to use %command% to use that environment variable LD_PRELOAD="" %command% -dx11

I have mangohud shows that there is no drop in fps. but a very crazy frametime.
and happens during the match under unclear conditions. maybe after the destruction.

Found out something else. This does not happen with the controller (freshly plugged in after issue starts), only mouse and keyboard. In main menu only the mouse, i guess because the keyboard does not do anything there.

I'll try the variable again.

Now the bug with freezes appeared right at the start of the match. It seems to be some random scans of the anti-cheat

@guglovich @jungleweiner
Are you also seeing these crashes or freezes when using the Bleeding Edge beta branch?
https://github.com/ValveSoftware/Proton/wiki/Proton-Versions

Yes

On Tue, Feb 11, 2025, 8:39 AM Blisto91 @.***> wrote:

@guglovich https://github.com/guglovich @jungleweiner
https://github.com/jungleweiner
Are you also seeing these crashes when using the Bleeding Edge beta branch?
https://github.com/ValveSoftware/Proton/wiki/Proton-Versions

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2651015421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BPL5OZD5CIAUNNBAAGXILPL2PIDSTAVCNFSM6AAAAABAM23QNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJRGAYTKNBSGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@guglovich @jungleweiner Are you also seeing these crashes or freezes when using the Bleeding Edge beta branch? https://github.com/ValveSoftware/Proton/wiki/Proton-Versions

Yes, I'm sitting on that Proton update thread.

Are you able to upload a Proton log from a time it happens?
Just insert PROTON_LOG=1 %command% in game's launch options and a file called steam-2073850.log should appear in your users home folder. If it is too big to attach directly then they usually compress well

steam-2073850.log.zip

steam-2073850.log.zip

The ld preload variable solved my issue, thanks to everyone who helped! I updated the original comment with a solution.

This isn't my issue

On Thu, Feb 13, 2025, 6:07 AM Star Lederer @.***> wrote:

The ld preload variable solved my issue, thanks to everyone who helped! I
updated the original comment
https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2613035961
with a solution.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2656401649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BPL5OZFXB4ITK37CHGYX7OL2PSDJTAVCNFSM6AAAAABAM23QNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJWGQYDCNRUHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

also every single unreal engine game i runs does this so it may not be a game issue not sure what to do

I tried the startup option LD_PRELOAD=‘’ %command%, and the whole session had no problems. Yesterday I removed it and the lags happened again. I will test further.

Broken again since today's update.
Crash on startup.

Starting with Proton experimental

Broken again since today's update. Crash on startup

Playing it right now without problems on cachyos, what proton version are you using and can you provide logs by doing a steam launch command on the finals

PROTON_LOG=1 %command%

It will output a file in your home directory where you can then upload it here, if you can't you can upload the file to google drive or something then link it to here

If you could also list your specs and distro your using that would be great

The memory usage seems to be extremely good now also so thats awesome, id hover around 4gb of ram for the game when before it used to leak like crazy and i would have to restart the game to keep playing after a couple of hours

Game can't go a single match without crashing since the update.

Game can't go a single match without crashing since the update.

Please provide logs by reading my above message and the proton runner your using, the distro your using and your specs, thanks

Game can't go a single match without crashing since the update.

Please provide logs by reading my above message and the proton runner your using, the distro your using and your specs, thanks

steam-2073850.log.zip

Linux mint
Rx7900xt
Ryzen 7 5700x3D
Asrock x570

Game boots to menu, but the rendering freezes while loading into a match or the practice range. Everything else works, I have sound, I can move and shoot, but the display output is stuck on the loading screen. Tried both proton experimental and bleeding-edge.

• NixOS unstable
• RX 6700XT
• Ryzen 7 5800X3D
• Gigabyte B350

Log for bleeding-edge:
steam-2073850.zip

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2686068271

what mesa version are you using? do this in your terminal vulkaninfo --summary

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2690679624

Vulkan Instance Version: 1.3.275


Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1

Instance Layers: count = 11
---------------------------
VK_LAYER_INTEL_nullhw             INTEL NULL HW                1.1.73   version 1
VK_LAYER_MANGOAPP_overlay         Mangoapp Layer               1.3.0    version 1
VK_LAYER_MANGOHUD_overlay_x86     Vulkan Hud Overlay           1.3.0    version 1
VK_LAYER_MANGOHUD_overlay_x86_64  Vulkan Hud Overlay           1.3.0    version 1
VK_LAYER_MESA_device_select       Linux device selection layer 1.4.303  version 1
VK_LAYER_MESA_overlay             Mesa Overlay layer           1.4.303  version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207  version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_32   Steam Overlay Layer          1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_64   Steam Overlay Layer          1.3.207  version 1
VK_LAYER_VKBASALT_post_processing a post processing layer      1.3.223  version 1

Devices:
========
GPU0:
	apiVersion         = 1.4.305
	driverVersion      = 25.0.0
	vendorID           = 0x1002
	deviceID           = 0x744c
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = AMD Radeon RX 7900 XT (RADV NAVI31)
	driverID           = DRIVER_ID_MESA_RADV
	driverName         = radv
	driverInfo         = Mesa 25.0.0 - kisak-mesa PPA
	conformanceVersion = 1.4.0.0
	deviceUUID         = 00000000-0f00-0000-0000-000000000000
	driverUUID         = 414d442d-4d45-5341-2d44-525600000000
GPU1:
	apiVersion         = 1.4.305
	driverVersion      = 0.0.1
	vendorID           = 0x10005
	deviceID           = 0x0000
	deviceType         = PHYSICAL_DEVICE_TYPE_CPU
	deviceName         = llvmpipe (LLVM 19.1.7, 256 bits)
	driverID           = DRIVER_ID_MESA_LLVMPIPE
	driverName         = llvmpipe
	driverInfo         = Mesa 25.0.0 - kisak-mesa PPA (LLVM 19.1.7)
	conformanceVersion = 1.3.1.1
	deviceUUID         = 6d657361-3235-2e30-2e30-202d206b6900
	driverUUID         = 6c6c766d-7069-7065-5555-494400000000

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2690690059

can you check your other logs on mint? Cinnamon has Menu > Administration > Logs, with a Search facility.

Do you see any crash logs related to amd maybe like a timeout?

Replying https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2690791363

Because everyone who is subscribed to this issue will get pinged and there are developers in here that don't want to be pinged

You can contact me through email if you still have issues

[email protected]

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2690690059)

can you check your other logs on mint? Cinnamon has Menu > Administration > Logs, with a Search facility.

Do you see any crash logs related to amd maybe like a timeout?

this is what i get from the log

-The package providing /home/louis/.steam/debian-installation/steamapps/common/Proton could not be found.
If you want to generate a stack trace for this crash report, please reinstall it.

Here we go again, update which includes

Security and Anti-cheat

• Improved detections

Broke the game. See the proton logs, I have tested bleeding edge, hotfix and 9.0-4 with no help. Sometimes I get the error The program encountered C0000022 at 015D7E24 during intialization. No message.

steam-2073850.zip

Patch 5.12.0 borked this game again. error window below belongs to /The Finals/Discovery/Binaries/Win64/Discovery.exe.

0x29f39f20:1: Token id=0.1018 primary=1 impersonation level=-1
0x29f34d60:1: Handle table last=1 count=32 process=0x29f34aa0
    0004: 0x29e957e0 000f037f [\\Sessions\\1\\Windows\\WindowStations\\WinSta0] Winstation flags=1 clipboard=0x29efd9e0 atoms=(nil)
    0008: 0x29ecd560 000f01ff Desktop flags=0 winstation=0x29e957e0 top_win=0x29ec3290 hooks=0x29ec2ac0
0x29f34aa0:1: Process id=01ec handles=0x29f34d60
0x29f34a30:1: Startup info in=0000 out=0000 err=0000
0x29ec2ac0:1: Hook table
0x29f14610:1: Thread id=011c unix pid=136607 unix tid=136611 state=1
0x29f0c500:1: Token id=0.1011 primary=1 impersonation level=-1
0x29f174b0:1: Process id=0108 handles=(nil)
0x29efd9e0:1: Clipboard open_thread=(nil) open_win=00000000 owner=00000000 viewer=00000000 seq=43
0x29efb090:1: window 0x29efb090 handle 10028
0x29ec3290:1: window 0x29ec3290 handle 10020
0x29edf140:1: Fd unix_fd=36 user=0x29ed9eb0 options=00000020
0x29ed9eb0:1: Mapping size=0000000000001000 flags=08000000 fd=0x29edf140 shared=(nil)
0x29ecd560:1: Desktop flags=0 winstation=0x29e957e0 top_win=0x29ec3290 hooks=0x29ec2ac0
0x29e957e0:2: [\\Sessions\\1\\Windows\\WindowStations\\WinSta0] Winstation flags=1 clipboard=0x29efd9e0 atoms=(nil)
0x29225160:1: [\\Sessions\\1\\Windows\\WindowStations] Directory
0x29225030:1: [\\Sessions\\1\\Windows] Directory
0x29224ad0:1: [\\Sessions\\1] Directory
0x29223f70:1: [\\Sessions] Directory
0x29223350:1: Directory
pid 136545 != 136544, skipping destruction (fork without exec?)

full proton log: steam-2073850.log

tested with proton experimental, no bleeding edge.

edit: patch 5.12.1 makes no difference.

Also getting that message, I tried proton experimental and proton ge with no change.

Same here.
New update, new issues... it's THE FINALS.

Same here.
New update, new issues... it's THE FINALS.

Hello Yolks!

We’re seeing a few cases of crashing on boot for some of our PC players. We have a fix in the works and will likely push out another, very small update today for PC only, to solve the issue. Sorry to those of you running into this problem! We’ll get you back in business soon!

Seems this could be embark being embark breaking something on PC in general, I bet when this update comes up the problem will resolve itself

Edit: well that didn't fix it lol

Thanks for the info!

Edit: oh well :/

The crash seems to be caused by preloader.dll throwing EXCEPTION_ACCESS_VIOLATION exception (code=c0000005)

Having the game break on every update is annoying but having Proton devs fixing it in only a few hours sometimes make it even more frustrating in a way. If Proton devs can fix those issues so fast after the fact, imagine if they could be involved in the release process... maybe we'd get bug-free updates

The crash seems to be caused by preloader.dll throwing EXCEPTION_ACCESS_VIOLATION exception (code=c0000005)

I believe the dialog box saying the program encountered C0000022 is a general Windows exception code for STATUS_ACCESS_DENIED.

So it's probably unable to access certain resources.

Can confirm I am getting this error too on the the latest version of proton experimental bleeding edge as well as the game itself

Getting the error The program encountered c0000022 at 014C6D71 during initialization. No message.. Tried with experimental, bleeding edge, and GE. Also tried verfying files and using PROTON_USE_EAC_LINUX=1 %command% as a launch option. Fedora 41 KDE

Similar fault was reported by a few windows players: https://discord.com/channels/1008696016318513243/1347335407322398780

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2705145098

That crash has already been fixed by Embark, the one we're getting is different. (Doesn't pop up the UE bug reporter)

Sometimes the UE bug reporter does show for me and some other users. If I launch the game around 5 or so times I get it. The other times it will just crash. This was before patch 5.12.1 though so I am yet to test if I still get it.

For Proton Experimental, Proton Experimental Bleeding Edge, and GE-Proton-25, I am left with this error
The program encountered C0000022 at 014C6D71 during initialization.

No message.

For Proton Hotfix (both frog and normal), it just crashes after showing EAC, showing no error message.

I got confirmation by an Embark employee on Discord that it's a known bug internally and they seek to work on a solution

Should hopefully work again with the just updated Proton Experimental [bleeding-edge] (see https://github.com/ValveSoftware/Proton/wiki/Proton-Versions, 'Proton Bleeding Edge' for the info about how to select this Proton version).

Yep, can confirm this works. Thanks a lot to the team :)

Replying to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2705145098)

That crash has already been fixed by Embark, the one we're getting is different. (Doesn't pop up the UE bug reporter)

why do i still get it then?

Fixed for me now on GE-Proton9-25

Fixed for me now on GE-Proton9-25

Idk if im stupid but hoe do i install this? I mean there is no new update for me atm

I believe that proton hotfix is working so you could try that. I am using the bleeding edge which works, if you want that take a look at the bottom of https://github.com/ValveSoftware/Proton/wiki/Proton-Versions

not sure if directly related to the finals but i am experiencing it whilst playing this game.

I am using pipewire, and I can hear audio crackling when triggering some sound effects. has anyone else noticed this recently?

not sure if directly related to the finals but i am experiencing it whilst playing this game.

I am using pipewire, and I can hear audio crackling when triggering some sound effects. has anyone else noticed this recently?

I've always had this when using pipewire. Veeery occasionally it doesn't happen, but I have no idea how to replicate. Probably has something to do with default sample rate and depth mismatch with my audio setup.

idk if it's related to today's update, but I'm experiencing game hangs for minutes every few seconds, severe graphical glitches, the game might as well have crashed (although audio is still playing). If I revert to a previous version of my OS the game straight up doesn't launch.

@taotien the game is working normally here, could be something else in your setup, on mesa 25, with a rx6600, proton experimental and linux 6.13.6, the game is working normally. If anyone else is having issues they should comment it.

Something like running out of memory could cause the game to hang as it moves memory around to swap but I don't know if that's what's happening in your case, if you use mangohud with the game you can check real time usage of your computer, maybe you'll be able to see if anything looks suspicious as the game hangs.

game crashes after 20 or 30 minutes mid game. unreal engine crash
I am using hotfix but have tried experimental and bleeding edge as well as GE. same result each time.

launch command is as fallows
PROTON_LOG=1 mangohud LD_PRELOAD='''' %command%

gist:b0ced45552894887c9c71887d08a000c

steam-2073850.log.zip

proton hotfix

Also I tried running on windows and it does the same thing. Is this a driver issue with the rx7900xt?

@taotien the game is working normally here, could be something else in your setup, on mesa 25, with a rx6600, proton experimental and linux 6.13.6, the game is working normally. If anyone else is having issues they should comment it.

Something like running out of memory could cause the game to hang as it moves memory around to swap but I don't know if that's what's happening in your case, if you use mangohud with the game you can check real time usage of your computer, maybe you'll be able to see if anything looks suspicious as the game hangs.

EDIT: been busy w/ school and haven't played on my laptop; just launched the game and this issue doesn't seem to be a problem anymore.

Sorry, I forgot to clarify with details. The exact behavior is: game launches fine, menu functions as usual, but as soon as I join a game it slows to maybe half a frame a minute (almost nothing renders) while audio is still mostly playing.

I've captured some of the output of dmesg and enabled proton log. It looks like a block of the errors appear in dmesg every "frame" that actually manages to happen. My specs are:

NixOS unstable
AMD Ryzen 7 7840HS
AMD Radeon RX 7700S
32GB RAM
Proton Hotfix / Bleeding Edge

dmesg snippet
https://gist.github.com/taotien/42a80c4ec01989e971fc81b8cd561aac

steam-log
steam-2073850.log.zip

@taotien I definitely don't have this issue, with page faults going around it's not surprising the game is not playable. I'm guessing the game was playable in the past, in that case do you know if it was a kernel update or a mesa update that introduced this issue?

No issues in Fedora, been using experimental on unstable branch.

They've updated dlls that broke the game but experimental has picked up the fixes before end of workday in each case.

Definitely want to use up to date mesa versions for this game.

Solved my issue. My ram was running slow. I had to change the voltage and timing and now that it is running at 3600 I have not had crash since.

Solved my issue. My ram was running slow. I had to change the voltage and timing and now that it is running at 3600 I have not had crash since.

It likely wasn't the fact it was running slow that was causing your issue, more likely it for some reason wasn't stable at the old speed. (usually it's the other way round though)

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2726330233

Hey im running a very similar system to yours, but havent been able to play the game for about a week

are you able to run? or is it just me?

I always get this error when i try to open the game:

It happens just after a small back window opens and closes soon after.
since it started happening i upgraded GE-proton9-{26->27} and it still occurs.

my system is:

• NixOS 25.05 (Warbler) x86_64 (ustable)
• AMD Ryzen 7 8845HS (16) @ 5.14 GHz
• AMD Phoenix3 [Integrated]
• GE-proton9-27

I got something similar on my system but a re launch of the game fixed it.

No matter how many times i relaunch i get the same error

Update 6.6 crashes after a few minutes, seems similar to #8636.

When I started the game yesterday it started in windowed mode. I change it back to bordered-windowed but in matches during my mouse would break out of the window to my other monitor causing me to lose fights constantly. I tired full screen as well and it continued to happen.

If I took a second to test if the mouse would leave the window after spawning it never would, only during fights. I'm running NixOS so I tried updating my system just to see if anything would change but nothing.

Has anyone else experienced this?

Also getting the same thing @shaqaruden, it is a bit different for me though. The setting has not changed but it launches windowed. Here are the logs from my crash:

steam-2073850.zip

Update 6.6 crashes after a few minutes, seems similar to [#8636](https://github.com/ValveSoftware/Proton/issues/8636).

I tried Proton Experimental, Hotfix, and CachyOS. All freeze after a few minutes. Neither journalctl nor the steam logs report anything at the time of the freeze.

@proJM-Coding for the time being I'm just disconnecting my monitor while I play. Very annoying but oh well

Tried Proton experimental, hotfix, and latest stable. Latest stable does not lauch, both others crashed, as already confirmed by @Callisto95. LD_PRELOAD="" and -dx11 do not seem to affect this. Interestingly, game remains responsive to kill signals

@proJM-Coding for the time being I'm just disconnecting my monitor while I play. Very annoying but oh well

That must suck, you didn't say that you got crashes though. Also did anyone else notice that there are 2 black windows (cmd.exe I think) that open now, was it like that before?

Only 1 cmd window in my case, and it always used to be 1. I also noticed that people in the windowed mode discussion don't seem to be experiencing crashes but the update came out today so maybe they just didn't see it yet. I guess also worth mentioning that I am on Nvidia GTX 1070, driver 565.77, Gnome, wayland, Linux 6.6.88

Just tested your suggestion about windowed mode but I still have the crash. I find it odd though that only weird resolutions were showing up (I didn't have a 1080p option) and I still get 2 cmd windows. I have only seen this happen after the update which is odd

Can confirm game is entirely broken as of right now (update 6.6, proton experimental bleeding edge + eac runtime test branch), freezes after a bit, similar to 8636, which I also have the exact same problems with.

Same issue here. Game freezes after 1-10 mins. Proton 10.0.1.

Logged in to comment the same thing. The game freezes after a minute or two.
Running on EndeavourOS (Arch-Like)

Tested it out with GE-Proton 9-26 and 9-27.

Can confirm here it crashes a couple minutes into a match, Kubuntu 25.04, Proton Experimental.

Log file: steam-2073850.tar.gz

@proJM-Coding for the time being I'm just disconnecting my monitor while I play. Very annoying but oh well

That must suck, you didn't say that you got crashes though. Also did anyone else notice that there are 2 black windows (cmd.exe I think) that open now, was it like that before?

I think the crashing started happening after I finished playing last night. My game did not update last night.

Game ran without an issue this morning and became unstable following the update. Game crashes after a couple of minutes into the game.

Game now freezes a couple minutes after playing after the update.

Operating System: CachyOS Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080

yep after last update "Season 6: Massive Mid-Season!" game freezes completly when u start any mode in game
Ubuntu Mate 24.04 (Display: x11 server: XOrg)
DE: Mate 1.26.2
Kernel: Linux 6.11.0-24-generic
CPU: Intel® Core™ i5-9300H CPU @ 2.40GHz × 8
RAM: SO-DIMM DDR4-2666 24Gb
SSD: 256Gb KINGSTON OM8PDP3256B-AI1
GPU: Intel UHD Graphics 630 @ 1.05 GHz [Integrated] (driver: Mesa 24.0.5)
GPU: NVIDIA GeForce GTX 1650 Ti Mobile [Discrete] (driver: 570.133.07)

the game was working smoothly before update. After update it is freezing after some minutes.

OS: ubuntu 24.04 based os (with xanmod kernel and some customizations)
DE: KDE 5.27
Kernel: 6.12.16-x64v3-xanmod1
CPU: Model name: AMD Ryzen 7 5800X 8-Core Processor
GPU: Nvidia RTX 3060 12 GB
RAM: 40 GB DDR4
NVIDIA-SMI 550.144.03 Driver Version: 550.144.03 CUDA Version: 12.4

Same thing here, the game freezes after a few minutes in-game.

OS: EndeavourOS x86_64
Kernel: Linux 6.14.4-zen1-1-zen
DE: KDE Plasma 6.3.4 (Wayland)
CPU: AMD Ryzen 9 5900X
GPU AMD Radeon RX 6950XT (Mesa 25.0.4-arch1.1)
RAM: DDR4-3200 32 GB

I too am having game freezes after season 6 latest update:

OS: Fedora 42
Kernel: 6.14.4-300.fc42.x86_64
DE: KDE Plasma 6.3.4
Graphics Platform: X11
CPU: AMD Ryzen 7 7700
GPU: NVIDIA RTX 4060 TI (8 Gb)
RAM: 32 Gb

Thanks for the prompt reporting and logs, the problem is universally reproducible and the basic reason is understood by now, no more logs / reports are necessary. I am hoping to issue some fix in Proton Experimental [bleeding-edge] / Proton Hotfix today.

what is the reason?

what is the reason?

Is the problem solved?

not yet, wait for proton experimental bleeding edge update

Played for several hours last night. No issues on Proton Hotfix, mesa 25
and Kernel 6.14

• Michael

On Thu, May 1, 2025, 11:48 AM mrvictory1 @.***> wrote:

mrvictory1 left a comment (ValveSoftware/Proton#7317)
https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2845228969

not yet, wait for proton experimental bleeding edge update

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2845228969,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6RJGPIONWWKWXGSOXXYRT24JF4DAVCNFSM6AAAAABAM23QNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBVGIZDQOJWHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2845240232

no, Still crashes

os Ubuntu 24.04

last night

@mikeymop It broke in todays update

@gofman tz?

I have problems too. Can play practice a few minutes and then it crashes. I've tried latest GE-Proton 27 and 26 and Proton Experimental and Hotfix

Operating System: EndeavourOS
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-zen1-2-zen
Graphics Platform: Wayland
Processors: AMD Ryzen 7 5600X 6-Core Processor
Motherboard: Gigabyte B550 Aorus Pro V2
Memory: 32 GiB of RAM
Graphics Processor: AMD 9070XT

Can confirm that it works again on newest bleeding-edge.

boys it work now lets goo

Can confirm that it works again on newest bleeding-edge.

Yeah, this is hopefully fixed with the just updated Proton Experimental bleeding-edge branch, see https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge for details how to opt-in for it.

Latest bleeding edge has fixed the crashing issue but the mouse losing focus issue is still present, making the game pretty much unplayable (consistently losing fights) because the mouse floats off onto a different window.

Mouse issue is also present in ARC Raiders.

Does anybody experiencing and issue with FPS drooping every 2 seconds after the latest proton bleeding edge update?

Thanks for today's Proton patch to the game 😁.

I think there may be an issue with the controller on Proton Experimental bleeding edge. About 10 minutes after launching the game, the game stops listening to the controller -- controller input no longer works. After restarting the game, it will listen to the controller again for another 10 minutes, but again, it stops working after that. Just disconnecting and reconnecting the controller via the cable once this happens doesn't work either.

When this happens, the controller input can still be interpreted with evtest -- everything appears normally there... It just seems to be THE FINALS specifically that stops receiving the gamepad signals.

Things I've tried:

• Rebooting the computer -- doesn't make any difference.
• Using Steam Input -- doesn't work at all with Steam Input enabled.
• Using/not using gamescope -- doesn't make any difference.
• Flipping between Proton Experimental (bleeding-edge) and Proton Hotfix -- the issue is present in both of them.
• Flipping between Wayland/Xorg GNOME sessions -- doesn't make any difference.

My setup:

• Arch Linux, up to date.
• Standard Xbox Series X/S controller via USB cable, using the default kernel driver for Xbox gamepads (I think xpad?). Bluetooth is disabled, so I don't think the issue is to do with different types of connections interfering with one-another.
• Using the native Arch Linux package of Steam, with Steam itself downloading/managing Proton versions and whatnot.

A slightly annoying bug, as I have no idea whether the issue's fixed or not until I suddenly stop moving mid-match and throw the rest of the game since I'm not good at KB+M 🥴.

Anyway, please let me know if you want more details.

Latest bleeding edge has fixed the crashing issue but the mouse losing focus issue is still present, making the game pretty much unplayable (consistently losing fights) because the mouse floats off onto a different window.

I've had this in other games before I resolved by using gamescope. I'll give it a try later.

With the added hack for steam overlay on EAC EOS games on proton 10 which this one is, when im in the match while picking the character, if i activate the steam overlay and close it my cursor is invisible and i cant get it back till im in the match, i can still click on things its just the cursor is invisible, on KDE Plasma, Cachyos, Proton Hotfix

toggle on and off steam overlay, or use alt+tab to switch focus between window could make cursor visible again; had this once (cannot remember when) and method above works for me

@Wartybix couldn't repro on my side, at least with plasma wayland. I tried with a dualsense and xbox series x controller separately in two different sessions for around 50 minutes each, they were wired as well (one at a time). Do you have any other different controllers to try and see if it happens to them as well?

@Wartybix couldn't repro on my side, at least with plasma wayland. I tried with a dualsense and xbox series x controller separately in two different sessions for around 50 minutes each, they were wired as well (one at a time). Do you have any other different controllers to try and see if it happens to them as well?

Ah okay, thank you for testing. You mentioned you're using Plasma, so maybe using KDE instead of GNOME could fix it? I'll give it a try later today. If that fails, I do have an older Xbox One controller in the cupboard I can try out. This bug only happened to me after the latest update to THE FINALS, and it was working fine before that. I'll update with how it goes.

@simifor my update: I tried playing on Plasma (without gamescope), though the issue remains... it doesn't seem to matter which controller I use either -- after a certain amount of time, the game just refuses to listen to any controller connected. Annoying if this bug only affects me -- maybe I need to reinstall Linux or something. In the meantime, I may have to just play this game on my Windows partition.

Does anybody experiencing and issue with FPS drooping every 2 seconds after the latest proton bleeding edge update?

Yes!

From my experiments this is what I found for THE FINALS:

• Proton 10 beta, Proton latest stable, Proton experimental bleeding-edge, Proton hotfix:

  • no game crash
  • but EAC launching twice, leading to stuttering

• Proton experimental bleeding-edge-9.0:

  • game crashes after game launch, or even in the lobby
  • no double instance of EAC, so no stuttering, the game runs butter smooth as it should

• Proton 9.04:

  • game doesn't launch at all

• Weird textures/blurring issue:

  • isn't Proton-dependent
  • distance level has no effect
  • trees LOD has no effect
  • CNN vs Transformers has no effetc
  • can be a bit mitigated by setting global illumination detail to epic, but remains still

I just installed Proton Hotfix and played 4 games before I had to get off.
I experienced no stuttering, crashes, or texture issues.

I do have a second EAC window though.
"Idle Energy Saving", "Inactive Window Energy Saving", and "Mute Game When Minimized" doesn't work as well.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2848094266

I can't try myself with Wayland as display server, but maybe we have a clue here? As I suspect the majority of us run under X11

Does anybody experiencing and issue with FPS drooping every 2 seconds after the latest proton bleeding edge update?

yup.. proton ge had no lag before. now after the patch with experimental bleeding edge, it doesnt crash, but its laggy..

is there any news of smoothing out this performance issue created?

@Wartybix I've seen a similar report from someone suffering gamepad disconnection but on fallout 76 and oblivion (I tried the latter, but no luck there either). So it doesn't seem like you're alone, but it's not clear what's causing the issue.

I played a game with the bleeding edge experimental and captured logs to see if it might provide some insight into the massive stuttering. the fps says its high, but the frametime is jumping all over the place (it was not doing this with proton-ge prior to this patch).

steam-2073850.log.zip

Looking forward to a potential fix. This stutter is unbearable.

And imagine you are a flicker guy 😂 Dude I just can't aim

Fedora 42
Plasma 6.3 wayland
Mesa 25
Kernel 6.14.4

No issues on experimental or hotfix. Proton 10 I do see the double eac prompt.
Proton 10 the game froze in practice range, but it was steam webhelper that crashed.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2848361375

i seem to get double eac even on proton experimental bleeding edge or on hotfix.

@Wartybix I've seen a similar report from someone suffering gamepad disconnection but on fallout 76 and oblivion (I tried the latter, but no luck there either). So it doesn't seem like you're alone, but it's not clear what's causing the issue.

I've also heard about the same thing happening to a Diablo IV player on Steam Deck. Some people mention a bug in Proton 10 is the cause of this, but that's all I know.

• Double EAC + stutters every ~2sec still occurring on today's bleeding-edge-latest.
• Crash still occurring on today's bleeding-edge-9.0.

Fedora 42 Plasma 6.3 wayland Mesa 25 Kernel 6.14.4

No issues on experimental or hotfix. Proton 10 I do see the double eac prompt. Proton 10 the game froze in practice range, but it was steam webhelper that crashed.

Same here, I have the double EAC thingy but it doesn't seem to be affecting the performance for me atleast but I do think the performance has dropped a bit (whether that is just finals being finals or something related to the EAC is unknown to me)

@ivyl I couldn't see anything suspect from your last commits, but I think https://github.com/ValveSoftware/Proton/commit/ea317ca6032c115eacba12f15ee899b9775af283 could actually match temporally. Do you think it's fair to consider it's coming from wine side?

• Double EAC + stutters every ~2sec still occurring on today's bleeding-edge-latest.
• Crash still occurring on today's bleeding-edge-9.0.

Well, I tried to build locally and trialed several 9.0 commits down to https://github.com/ValveSoftware/Proton/commit/8888e21f031b17e5cca4744184e12658ef164478
And also tried latest 10.0.1 build https://github.com/ValveSoftware/Proton/commit/449e9774ba93c5751ea080629aa6091758d6507f

To summarize what I found:

• all proton 9.0 builds lead to the game crash introduced last week after a THE FINAL update
• all proton 10.0.1 builds, which fixed the game crash lead to the double EAC issue and therefore, stuttering

If anyone who doesn't notice the stuttering issue despite having 2 EAC instances launching, would be great to share your FPS limit value, just to make sure the perception isn't what's responsible for divergent reports here.
Just to clarify for myself: I'm capping it at 140 FPS, and reaching those 140 FPS in training range, so I might be reaching that in the welcome screen too. Anyway, I can notice those stutters in both.
They happen periodically, as I said like every ~2 sec, and are really slight, so I think they could actually not even be noticed or felt on lower FPS if they happen in between the frames, or at least be really less easily noticeable.

Maybe to start: @s-ka-te-s @qvvonk what's your framerate guys? Cause it seems we are the only 3 ones reporting this here.

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2852287224

I have a very similar experience myself. after this update, all proton builds that don't crash to desktop include experiemental (bleeding edge) and hot fix (i think). im getting stutters more frequently than every two seconds. i would say constant stuttering. my fps values are pretty high though, so im guessing it has to do with frametimes?

when i run proton-ge (latest) that crashes to desktop after 10-60 seconds. however, there is ZERO stuttering before that happens (in-game of course).

i am also having 2 EAC black screens pop-up on every launch (including proton-ge which crashes). idk if that happened before this finals update,

ive experimented to capping my fps at 120, 180, etc. it hold high at those fps values, but i can still feel the stutters constantly. this, again, did not happen prior to this update.

ive even gone so far as to reinstall my operating system to see if something was bugged. this is reproducible.

i would like to help log this issue in any way possible. would it help if i recorded gameplay of the stuttering? with mangohud enabled?

thanks for the ping. i appreciate it.

P.S. im also on a single monitor. so @RobotRoss 's message above regarding the mouse losing focus has not affected me in any way whatsoever. this is not related to the issue ive been facing.

I can confirm that the finals update is what caused the two EAC black screens. I didn't see it before the update and I play many times during the week.

I can confirm that the finals update is what caused the two EAC black screens. I didn't see it before the update and I play many times during the week.

Nah I think I we got the THE FINALS update that made the game crash, and right after proton bumped from 9.0 to 10.0.1 on experimental bleeding edge. That's what fixed the crash issue, but then we now have this EAC thing on any 10.0.1 build.
The date seem to correspond, even if I don't really remember which day the THE FINAL update in question has been rolled out, look: https://github.com/ValveSoftware/Proton/tags?after=experimental-bleeding-edge-10.0-192033-20250430-p7d7999-wc03e2c-d27b71a-v4ec9ec
that's my guess

When you have issues it's always helpful to have system information like your gpu, cpu, kernel version and driver version.

I've been trying to repro the cyclical stutters but I haven't had luck on my side, I've tried cycling through low/medium/high settings with uncapped and later capped framerate, both from mangohud and the game's builtin limiter. The only stutters I encountered seemed to come from the game itself, explosions and the like but nothing happening in regular intervals.

This is on a system with a rx 6600, ryzen 5700 x3d, mesa 25.0.5, linux 6.14.4 and proton experimental bleeding edge with no special launch parameters, just proton logging and mangohud to keep an eye on frametimes.

I found this in steamapps/compatdata/2073850/pfx/drive_c/users/steamuser/Application Data/EasyAntiCheat/service.log:

proton 10.0.1 (any)

[EAC Setup] [388] [20:31:06:576] [Info] Process started, running as admin: false.
[EAC Setup] [388] [20:31:06:576] [Info] Started with 'install b5adc328432e4883a396eba3d9c05133'.
[EAC Setup] [388] [20:31:16:580] [Info] Argument handling done, requested action: 1.
[EAC Setup] [388] [20:31:16:580] [Info] Operation requires admin elevation, attempting relaunch with admin privileges.
[EAC Setup] [436] [20:31:16:758] [Info] Process started, running as admin: true.
[EAC Setup] [436] [20:31:16:758] [Info] Started with 'install b5adc328432e4883a396eba3d9c05133'.
[EAC Setup] [436] [20:31:26:763] [Info] Argument handling done, requested action: 1.
[EAC Setup] [436] [20:31:26:769] [Info] ProductId already marked as installed, no action needed.
[EAC Setup] [436] [20:31:26:774] [Info] Operation 1 completed successfully.

proton 9.0 latest bleeding edge

[EAC Setup] [360] [20:25:39:353] [Info] Process started, running as admin: true.
[EAC Setup] [360] [20:25:39:353] [Info] Started with 'install b5adc328432e4883a396eba3d9c05133'.
[EAC Setup] [360] [20:25:49:356] [Info] Argument handling done, requested action: 1.
[EAC Setup] [360] [20:25:49:364] [Info] ProductId already marked as installed, no action needed.
[EAC Setup] [360] [20:25:49:371] [Info] Operation 1 completed successfully.

I mean, "relaunching" would mean to kill the process and launch a new instance, not letting the first one running.
It really feels something is wrong there.

I don't really think it can help, but here is my setup:

linux kernel 6.11.0-25-generic
AMD Ryzen 9 series
Nvidia RTX 3000 series
Nvidia drivers 570.133.20 open kernel
No launch option in Steam

Replying to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2855585649

my specs:
linux mint 22.1
xanmod kernel latest
ryzen 7 5700x3d
32gb ddr4
rx 6750 xt with Mesa 25.0.5

it seems like we have similar specs. even the same cpu

@s-ka-te-s indeed Indeed, we have similar systems. Could you share the output of dmesg? It could give some hints about the issue.

@s-ka-te-s indeed Indeed, we have similar systems. Could you share the output of dmesg? It could give some hints about the issue.

[ 5172.621261] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c1c3cd
[ 5172.629105] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c1de47
[ 5172.649741] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c6a74b
[ 5172.654811] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c583e5
[ 5172.668442] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c5ccc8
[ 5172.681042] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c60bd7
[ 5172.687980] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c5be56
[ 5172.697833] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c5e722
[ 5172.719664] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c68d0b
[ 5172.739152] Discovery.exe[12414] vsyscall read attempt denied -- look up the vsyscall kernel parameter if you need a workaround ip:7000007732cc cs:33 sp:b9bd38 ax:b9bda0 si:ffffffffff600000 di:c678f4
[ 5174.763955] umip: wine_threadpool[12441] ip:700001543cec sp:2a8ed3e0: SMSW instruction cannot be used by applications.
[ 5174.763961] umip: wine_threadpool[12441] ip:700001543cec sp:2a8ed3e0: For now, expensive software emulation returns the result.
[ 5176.763042] umip: wine_threadpool[12432] ip:700001543cec sp:23a0d3e0: SMSW instruction cannot be used by applications.
[ 5176.763049] umip: wine_threadpool[12432] ip:700001543cec sp:23a0d3e0: For now, expensive software emulation returns the result.
[ 5178.809214] umip: wine_threadpool[12713] ip:700001543cec sp:c682d350: SMSW instruction cannot be used by applications.
[ 5296.762384] umip_printk: 115 callbacks suppressed
[ 5296.762388] umip: wine_threadpool[12555] ip:700001543cec sp:641dd350: SMSW instruction cannot be used by applications.
[ 5296.762392] umip: wine_threadpool[12555] ip:700001543cec sp:641dd350: For now, expensive software emulation returns the result.
[ 5298.859777] umip: wine_threadpool[12554] ip:700001543cec sp:6365d350: SMSW instruction cannot be used by applications.
[ 5298.859784] umip: wine_threadpool[12554] ip:700001543cec sp:6365d350: For now, expensive software emulation returns the result.
[ 5300.861411] umip: wine_threadpool[12818] ip:700001543cec sp:12e22d350: SMSW instruction cannot be used by applications.
[ 5418.581338] umip_printk: 115 callbacks suppressed
[ 5418.581342] umip: wine_threadpool[12713] ip:700001543cec sp:c682d350: SMSW instruction cannot be used by applications.
[ 5418.581347] umip: wine_threadpool[12713] ip:700001543cec sp:c682d350: For now, expensive software emulation returns the result.
[ 5420.580855] umip: wine_threadpool[12431] ip:700001543cec sp:22a8d3e0: SMSW instruction cannot be used by applications.
[ 5420.580863] umip: wine_threadpool[12431] ip:700001543cec sp:22a8d3e0: For now, expensive software emulation returns the result.
[ 5422.581291] umip: wine_threadpool[12552] ip:700001543cec sp:61f5d350: SMSW instruction cannot be used by applications.

Let me know if theres anything here that may point to the issue.

@s-ka-te-s no different from what I get. It's likely not going to be useful in this case, but, in general, it's a good idea to share the whole output of dmesg, you can get it saved to a file by doing dmesg > dmesg.log so you don't have to manually copy stuff.

Just to rule things out, have you tried cleaning the prefix of the game? in your steam library there's a folder called compatdata, inside that you'll find you prefixes, the one for this game is called 2073850. If you delete it and run the game, proton will make a new prefix for the game. Does the issue still happen with a clean prefix?

@s-ka-te-s no different from what I get. It's likely not going to be useful in this case, but, in general, it's a good idea to share the whole output of dmesg, you can get it saved to a file by doing dmesg > dmesg.log so you don't have to manually copy stuff.

Just to rule things out, have you tried cleaning the prefix of the game? in your steam library there's a folder called compatdata, inside that you'll find you prefixes, the one for this game is called 2073850. If you delete it and run the game, proton will make a new prefix for the game. Does the issue still happen with a clean prefix?

yes, i still get stuttering when i did that. i also re-installed my entire os and the same issue was present. so because of that, i do not believe there is an issue with my software or game install.

is there anything else i could do to be more helpful?

@simifor in addition, for further insight, my GPU usage is almost glued at 99% during matches. the stuttering is solved somewhat if i crank all my settings to low and render the game at FSR Performance. I never had to do this with Proton-GE, but Proton-GE crashes to desktop when i enter a public match. if i stick with proton-ge in the practice tool, i dont get the same stutters in the same version of the game. something weird is going on with the official Proton Experimental bleeding edge. I get the same stutters with Proton 10 beta in the practice range, however that crashes to the desktop when entering a public match.

I hope this information is useful.

@s-ka-te-s then we start looking at other factors. Have you tried to use a stock kernel after this problem started to see if the issue still happens? Is the game installed on an HDD or a SSD? What's the filesystem format of the partition where it is installed? What desktop environment are you using? xorg or wayland?

@simifor

i just uninstalled the xanmod kernal and rebooted my pc. verified the generic kernel was active and it still stutters.

it is installed on my ssd (ext4). same drive and partition as my boot drive.

im using Linux Mint (cinnamon)

according to the echo $XDG_SESSION_TYPE command, im using x11

using mangohud, the fps is stay consistent i think. however, the frametime is jumping between 6.5 and 25.0 ms. even up to 30ms. aiming is almost impossible. thought that information might be relevant.

should i upload some gameplay footage? idk

Nobody else than me shared the framerate they are playing at, because the stutters (at least for me) are really slight actually, so maybe they are barely noticeable at lower FPS. I'm running at 140 (capped).
Also, I tried dual booting: no double EAC under windows. I think this really is the most probable and simpler explanation...

@Wartybix Regarding the controller disconnection issue - I hopefully have an answer for you :D We believe the issue is related to users who have changed their config to allow hidraw access to their mouse/keyboard.
https://github.com/ValveSoftware/Proton/issues/8644#issuecomment-2857710891. There is a fix for this in the experimental-10 build that just went live. Could you please test this and let me know if you still get the random controller disconnection with Proton - Experimental (or bleeding-edge)?

Edit - in reply to https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2845967967

@s-ka-te-s what you and @blakkd describe appear to be different levels of severity, so I'd appreciate a video showing what you see.

Just to rule things out, have you launched the game without mangohud? While unlikely to be the culprit, it does have framecapping capabilities, so might as well. Also try to launch the game with directx11, it can be forced here by using %command% -dx11, note that this will cause stutters as it compiles shaders so you'll need to play for a few minutes for things to smooth out, after you've played for a while, how do the frametimes fare? Better? Worse?

@Wartybix Regarding the controller disconnection issue - I hopefully have an answer for you :D We believe the issue is related to users who have changed their config to allow hidraw access to their mouse/keyboard. [#8644 (comment)](https://github.com/ValveSoftware/Proton/issues/8644#issuecomment-2857710891). There is a fix for this in the experimental-10 build that just went live. Could you please test this and let me know if you still get the random controller disconnection with Proton - Experimental (or bleeding-edge)?

Edit - in reply to [#7317 (comment)](https://github.com/ValveSoftware/Proton/issues/7317#issuecomment-2845967967)

@alasky17 Yes, I've been in game for about 2 hours with the latest Proton Experimental (non bleeding-edge), and haven't had the controller disconnect 😊. Thank you for your work on this. In the meanwhile, I'll look into revoking the hidraw access to the mouse and keyboard if this is a security vulnerability. I don't think this is something I enabled intentionally.

the double eac prompt should be fixed in the last bleeding edge update, the first launch will still show it twice on an existing prefix, but it will be normal in subsequent launches

Can confirm that the double eac prompt is no longer present. Just to make it clear I am on bleeding edge.

Latest bleeding edge 10:

• No more double EAC instances
• but I still have the cyclic stutters!
• dx11/dx12 / prefixes deleted from compatdata

I'm surprised it isn't caused by EAC at the end!

For myself, still dual booting, those stutters are really subtitles but can't aim like that.

@simifor about the video, I tried capping at 60 to see: they couldn't be spotted even when closely watching. So, could you play a 140 fps video smoothly? That would be the only way

Edit: I didn't see all your responses! So "I confirm too!"

the double eac prompt should be fixed in the last bleeding edge update, the first launch will still show it twice on an existing prefix, but it will be normal in subsequent launches

@simifor why did you announce this at the futur tense? Are you a dev of one of the projects? No arsh tone, just to be clear! It's just I thought you were only a user like us, it's just to know who I'm talking to, no less merit in one case or the other.
and thanks for helping in any case!

@blakkd I've been mostly playing the game with the framerate uncapped, though with my hardware I mostly get around 90-100 FPS. Gave cinnamon, plasma xorg, and xfce a try, and neither of those had the cyclical issues (though xfce would have some odd spikes here and there that I wasn't really seeing with the rest).

I know the other reporter is on cinnamon, but I don't know what you're using, or if you've tried running the game with directx 11 and if that had any effect in your case, that could help narrow things down.

That message wasn't meant to be future tense, the update was already out, but I do help test things related to proton.

I just want to hook in and report my current issues.
Playing on Nobara 42, the game still feels laggy, even though I have 90–120 FPS on Nvidia. I get frame drops every few minutes, leading to the point that the whole game stops for like 2 seconds and then continues to run.
I run it with bleeding edge, the new 10.0 Beta also hangs after a few minutes.
So there are still a few issues.

@BLACK4585 how frequent are those? I tried it today on nvidia and it went fine, but that was only a single powershift match (so that'd be 10 minutes of action). nvidia 570.144, linux 6.14.5, plasma wayland

Actually every minute, often more when there is a lot of stuff happening.

@simifor

I mostly get around 90-100 FPS

Do you think you would be able to play a 140 fps video? Because I think I might be able to record at this.

xfce would have some odd spikes here and there that

I remember having troubles with xfce with the finals in the past (I don't remember what it was), but I can give it a new try, thanks for the suggestion.

I don't know what you're using, or if you've tried running the game with directx 11

Cinnamon too (Linux Mint)
Sorry my previous msg wasn't really clear, yeah I tried dx12 and dx11, no effect.

the update was already out, but I do help test things related to proton

OK, thx for clarifying.

@BLACK4585 that's curious when dual booting to Windows, I do have some total ~2 sec freezes as you describe, but only on the first games and only 1 per game I would say. That said, the frames latency isn't bad (not as good as linux, but it's really OK) like yours apparently.
Don't really think this will help, but I just wanted to say it in case it could be related.

Since not everyone seems to have this problem, I wonder if I can somehow fix this by reinstalling the game or recreating the prefix? Maybe through the versions + proton switches over the months there is so much "bloat" installed which somehow interferes with the game(s anticheat). Can this even happen that prefixes get bloated in the way I described here?

Since not everyone seems to have this problem, I wonder if I can somehow fix this by reinstalling the game or recreating the prefix? Maybe through the versions + proton switches over the months there is so much "bloat" installed which somehow interferes with the game(s anticheat). Can this even happen that prefixes get bloated in the way I described here?

I'm also facing the same issues, recreated the prefix and it still persists. Been having almost constant stutters for more than a week, sometimes the game starts fine but then once the stutters start it just remains unplayable.

Update: It was a hardware issue on my side, game runs well now.

@blakkd reduced internal resolution as much as I reasonably could, getting the game in the 130-170FPS range (based on the map, what's happening and what's visible), and I'm not facing constant stutters or anything similar, just some spikes here and there when grenades go off and that kind of thing, not something that actively throws my aim or anything.

@simifor OK, so you might definitely not suffer from it on your side. I still do as of today! In the lobby, in training range, don't even need to launch a match.
Even if you didn't answer me on this, I'll still share a recording at 140fps soon as I was proposing, to at least see if @s-ka-te-s or others are suffering from the same, or if I'm alone in my case!

And thanks for reporting back!

OS: DEBIAN SID SNAPSHOT VERSION OF October 2024
Kernel: 6.11.2-amd64
GPU: NVIDIA GeForce RTX 3060 Lite Hash Rate
CPU: AMD Ryzen 7 5800X (16) @ 4.851GHz
Memory: 40GB
game just freeze after some time.

running with proton expremental bleeding edge

here is full log

steam-2073850.tar.gz

:Last lines:

4896.971:00f8:0278:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
4897.451:0030:0454:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
4897.451:0030:0290:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
4897.451:0030:0464:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
4897.452:0030:0264:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 12350 != 12349, skipping destruction (fork without exec?)