search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.86k stars 1.04k forks source link

THE FINALS (2073850) #7317

Open HurleybirdJr opened 9 months ago

HurleybirdJr commented 9 months ago

Compatibility Report

System Information

I confirm:

Proton Log

steam-2073850.log

Symptoms

image

Reproduction

HurleybirdJr commented 9 months ago

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

NTMan commented 9 months ago

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

steam-2073850.log

Screenshot from 2023-12-08 22-35-10

JGodin-C2C commented 9 months ago

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

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

r0b3rtf1sh3r commented 9 months ago

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

polluxau commented 9 months ago

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

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

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

Kagukara commented 7 months ago

Looks like it might be working now.

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

polluxau commented 7 months ago

Screenshot_20240113_043324

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

alasky17 commented 7 months ago

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

beh-10257 commented 7 months ago

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

image

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

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

NoHidSe commented 7 months ago

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

polluxau commented 7 months ago

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

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

Pokepunch commented 7 months ago

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

sevmonster commented 7 months ago

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

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

happysmack commented 7 months ago

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

SopaDeMacaco-UmaDelicia commented 7 months ago

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

sevmonster commented 7 months ago

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

Make sure you have the Proton EasyAntiCheat runtime installed.

SopaDeMacaco-UmaDelicia commented 7 months ago

Make sure you have the Proton EasyAntiCheat runtime installed.

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

xpander69 commented 7 months ago

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

DaveKram commented 7 months ago

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_LINUXto add clearcpupid=304 at the end.

Ran

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

Rebooted and launched the game. Using Proton Experimental.

Screenshot from 2024-01-12 18-24-32

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

SopaDeMacaco-UmaDelicia commented 7 months ago

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

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

SopaDeMacaco-UmaDelicia commented 7 months ago

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

Yeah, if you turn on voice chat game hangs.

Vinjul1704 commented 7 months ago

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:

SraamaR commented 7 months ago

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

structnull commented 7 months ago

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

kisak-valve commented 7 months ago

The Finals

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7405. @UbuntuGaming posted on 2024-01-13T21:45:05:

Compatibility Report

System Information

I confirm:

Symptoms

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

steam-2073850.log.zip

Reproduction

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

More Info:

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

djdeath commented 7 months ago

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

learning-thing commented 7 months ago

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: ↓

2024-01-14_15-29

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

ZyanKLee commented 7 months ago

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.

SopaDeMacaco-UmaDelicia commented 7 months ago

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.

hckgg commented 7 months ago

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

Same issue similar setup but gtx 1070

ZyanKLee commented 7 months ago

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.

polluxau commented 7 months ago

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 Screenshot_20240115_194940

Screenshot_20240115_194958

sevmonster commented 7 months ago

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.

polluxau commented 7 months ago

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

polluxau commented 7 months ago

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

SopaDeMacaco-UmaDelicia commented 7 months ago

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.

BobrImperator commented 7 months ago

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

IvanKulagin commented 7 months ago

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

SopaDeMacaco-UmaDelicia commented 7 months ago

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

crash 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

WapaMario63 commented 7 months ago

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: Screenshot_20240115_165855 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)

kisak-valve commented 7 months ago

THE FINALS (2073850)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7413. @dizeeee posted on 2024-01-16T00:53:05:

Compatibility Report

System Information

I confirm:

steam-2073850.log

Symptoms

When trying to queue to join games, I get error TFGE0001. I have tried virtually every bit of troubleshooting advice I can to resolve this error. I have had success running the game on my Steam Deck though, which seems to indicate that this is something related to proton or my system configuration. On the Steam Deck, I verified that it worked both wired and wireless, since this issue seems to be network related. It runs without any config changes, and keeping crossplay enabled worked.

Reproduction

dizeeee commented 7 months ago

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.

sevmonster commented 7 months ago

@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?

dizeeee commented 7 months ago

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

bursterburster commented 7 months ago

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

Yes it is.

dizeeee commented 7 months ago

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

alasky17 commented 7 months ago

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

polluxau commented 7 months ago

@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 commented 7 months ago

@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

Zenzi0 commented 7 months ago

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