Closed Revenator closed 8 months ago
Same thing happens on my desktop with an R5 5600x and a GTX 1080 running the latest official NVIDIA driver, so it's not GPU vendor specific. The game is fully stable until it starts to attempt to connect to a game session.
My first thought was maybe that's when the game initializes / starts using EAC
E: I should mention that this occurs on DX11 and DX12
Same here. Just tried to join the practice range, then it hung. Specs:
I have the same issue.
As of patch 0.2, when I queue for the practice range and it finishes looking for players, a quick loading screen appears. After that, you get put back to the main menu, and a new error shows. This error may not show the first time you queue. For me two showed after I queued a second time.
Even though the error pops up, the game doesn't crash, and you can still navigate the menu. However, when you click 'OK,' the game closes, just as the error message says.
OS: Arch Linux KERNEL: 6.2.2-arch1-1 WM: sway version 1.8.1 CPU: AMD Ryzen 9 5950X 16-Core GPU: AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.0, DRM 3.49, 6.2.2-arch1-1) GPU DRIVER: 4.6 Mesa 23.1.0-devel (git-a4fa489002) Proton version: Experimental
gamemoderun mangohud %command%
Added PROTON_LOG=1
to get the log. During the 3rd time waiting for practice range the errors showed.
steam-2076040.log (fixed the gamemodeauto
issue)
Steamlog for game launching with gamemoderun
removed.
steam-2076040.log
With patch 0.2, the first time I try to enter the practice range, I get thrown back to the main menu during the loading screen without any apparent error. The second time around, it hangs as before.
I can also confirm the issues while trying to get into quick play/ practice range.
However, the video playback issues seem to be fixed in Proton GE 7-50
OS: Fedora Linux KERNEL: 6.1.13-200.fc37.x86_64 CPU: AMD Ryzen™ 9 5900X × 24 GPU: AMD Radeon™ RX 580 Series (polaris10, LLVM 15.0.7, DRM 3.49, 6.1.13-200.fc37.x86_64) GPU DRIVER: 4.6 Mesa 22.3.6 Proton version: Experimental / Proton GE 7-50
Same here. When finding matches, back to the menu.
Update with the second beta the finals is still using easyanticheat eos Which means enabling proton would be super easy for them to do
Easyanticheat launches a installer window Then shows the easyanticheat then closes instantly. Steam thinks the game is still running when it isn't.
I highly recommend anyone that wants the finals the work on Linux through proton joins the discord and goes to the beta feedback and bug text channels and asks for Linux support as it would tell the embark devs to enable it.
Replying to https://github.com/ValveSoftware/Proton/issues/6602#issuecomment-1591838407
They were using EAC in the first beta as well.
Also this is the response I got from a community manager on discord:
goofygoobbue#0 Hey fren, Beau here! We do not have proton enabled for this CB2. We've been hearing all the yolks wanting for Linux support, and this feedback has been forwarded to our devs in large. If there are any developments on that end, we will make sure to announce it on the appropriate channels. Community Manager•12/06/2023 14:56
Replying to https://github.com/ValveSoftware/Proton/issues/6602#issuecomment-1591844135
Oh I see I see 😅 That's good to hear. hopefully they enable it when it fully releases or in the beta
Open Beta began on 26 Oct, still hangs on launch presumably waiting for EAC to initialize (which it never does). Same symptom as CB2. I assume the devs still haven't got around to adding support.
Open Beta began on 26 Oct, still hangs on launch presumably waiting for EAC to initialize (which it never does). Same symptom as CB2. I assume the devs still haven't got around to adding support.
They have not, rob clarified to me in dms that they haven't done it yet but they are gonna do it at some point, hopefully release
Log says that we have a syscall fault somewhere, there are also some clues that suggest the game actually has Linux EAC enabled. This might be actually some Wine compatibility issue. Let me look into this at some time.
Log courtesy of Rezzafri.
It looks like Embark made their in-house anti-cheat as preloader.dll
and it does wacky things that most importantly prevents DXVK from loading Vulkan. EAC is probably fine (they have .so too). We'll need to wait for compat fix from Embark.
It looks like Embark made their in-house anti-cheat as
preloader.dll
and it does wacky things that most importantly prevents DXVK from loading Vulkan. EAC is probably fine (they have .so too). We'll need to wait for compat fix from Embark.
Hmm very interesting 🤔 embark dont like to share their own anticheat so yeah we will have to wait
Wouldn't it be vkd3d as the game is under directx12 not 11?
After the last update I get this:
OS: Arch Linux KERNEL: 6.5.8-arch1-1 WM: i3 version 4.23 CPU: AMD Ryzen 9 5900X GPU: NVIDIA GTX 1070ti GPU DRIVER: NVIDIA 535.113.01 Proton version: Proton GE 8-22
The reason the game starts is probably because they removed the DLL signature enforcement, maybe because it also caused some compat issue on Windows. I would assume they still haven't resumed work on Linux support yet, and the game being able to launch is just a side effect.
The only interesting thing I see in logs unknown information classes with NtQueryInformationProcess, including 64 and 88. 64 is documented (ProcessTelemetryIdInformation).
(Also, please make sure to attach logs with each new report.)
game now boots up with the latest proton experimental bleeding edge with the newest update but this comes up now
Someone already posted the same above. Also, including logs would be helpful next time.
Replying to https://github.com/ValveSoftware/Proton/issues/6602#issuecomment-1789313532 https://github.com/ValveSoftware/Proton/issues/6602#issuecomment-1789325981
i have uploaded one to my comment
The Finals has been released today and it has the same system integrity violation error.
The Finals has been released today and it has the same system integrity violation error.
Yep, a lot of people are asking for support in the discord so hopefully they enable it soon
they said that we wouldn't be able to do beta but at release we would be able to play via proton if i remember correctly.
1000's of ppl repeating them selves. you'd think it be smarter to just PSA (hey sorry atm with linux users, heres the info
they said that we wouldn't be able to do beta but at release we would be able to play via proton if i remember correctly. 1000's of ppl repeating them selves. you'd think it be smarter to just PSA (hey sorry atm with linux users, heres the info
) ... but no... the hype is hot air at this point.
They never said that
The only thing that came close to bringing support was from my dms with embark rob who said they would do it in the future they never said at release
I wouldnt be suprised if they bring support within a couple of weeks from now because many people are asking for it
so discord replies aren't legit? I am sure that was the "hush" talk when we bombarded them during beta about why we couldn't play. the things i remember said to reply, something about their own proprietary anti cheat and eac, so wont be able to participate in the beta, but it will be at launch (re steamdeck/proton eac) ill try find it. may have just been a mod calming the farm as it was out of hand as it is atm in their.. jeez
I have contacted technical support 3 times to resolve the Linux support problem and we must work more
I have contacted technical support 3 times to resolve the Linux support problem and we must work more
True we must keep reminding them 😂👌
I am pretty much in the same situation. Tried and failed to run it on fedora and pop_os.
Same here guys.. But i got the error code.. tfav0010
Is there a proper channel to voice support for linux?
Is there a proper channel to voice support for linux?
Only there discord in feedback
works now
Game didn't get past a black screen until running it with GE Proton 8-27, but game detects is as cheating software. After that tkg bleeding edge started working for menu's, but crashes when trying to get into game. Proton experimental crashes almost exactly 10s after getting into the main menu, though it works until then.
You have to disable "compatibility tool" in Steam and then it works just fine.
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 Sorry for no log attached, didn't really know which to add on deck
I'm getting the same error as you, HinataKato, but about 10s after game loads into main menu.
I'm getting the same error as you, HinataKato, but about 10s after game loads into main menu.
That's werid, looks like we had the same issue? Mines are EAC→Login→Main menu→Some second later-hung→Also sometimes later hung-popup→Clicked the ok button→Back to Steam's menu
It looks like this game's playtest beta has ended a while ago and the current feedback being added here is intended for the game's full release (2073850).
Please continue discussing your experience with the full game release on #7317.
Closing because the Playtest does not appear to be publicly accessible anymore.
Compatibility Report
System Information
I confirm:
Symptoms
The Video doesn't play at the beginning and when you launch a game after about 20 seconds you get a message "applications has hung and now will close.
Reproduction
happens every game
steam-2076040.log