Open ThisNekoGuy opened 2 years ago
steam-1029690.log Almost everything is identical, except I don't even make it to the game. The launcher shows up, (incorrectly formatted), the screen goes black, and then it just crashes out.
I am also experiencing some errors regarding EAC, neither Proton experimental (both stable and bleeding edge) or Proton-GE work, and give the same error. steam-1029690.log
@unclamped Just to be sure: you do have the EAC runtime installed from the "Tools" category in your Library, right?
@unclamped Just to be sure: you do have the EAC runtime installed from the "Tools" category in your Library, right?
Yes, tried initializing the game both with it installed and without it. Apparently Sniper Elite uses EOS EAC from what someone told me in the ProtonDB Discord server, although I'm not really sure
Last update breaks the launching the game.
Hello @NTMan, wine: Unimplemented function iphlpapi.dll.NotifyNetworkConnectivityHintChange called at address 0000000170032138 (thread 0344), starting debugger...
looks like the line of interest from your log.
Since the latest giant 40GB patch this has started crashing. Log attached.
Hello @NTMan,
wine: Unimplemented function iphlpapi.dll.NotifyNetworkConnectivityHintChange called at address 0000000170032138 (thread 0344), starting debugger...
looks like the line of interest from your log.
Same error in my log. Any workaround?
I thought it was just me, but not, the game borked after the latest update. First it was the EAC, now the entirely game, even with native Vulkan. No workaround found by now. Tried with Proton Experimental and Proton-GE 7-42.
Really annoying cos I was 50% through the game when that update landed.
It's working again with Vulkan with the Hotfix Update from 2022-12-05.
Can confirm, after latest update, now working with proton 7.0.5 and experimental
Yes, after the latest update the game is working again with Vulkan. However, the EAC issue («hash catalogue not found») is still present.
However, the EAC issue («hash catalogue not found») is still present.
I confirm that anti-cheat didn't work. steam-1029690.log
Although Proton EasyAntiCheat Runtime is installed.
Replying to https://github.com/ValveSoftware/Proton/issues/6140#issuecomment-1330945899
I just installed it and it's not working. Just the launcher works, not the game and Vulkan is greyed out. :( It grew almost 20Gigabytes in size since the last time I installed it. WOW!
I don't know if it's due to recent versions of Proton or some update, but multiplayer is now working. I just played a deathmatch without issues. Using Valve Proton 8.0.
My game refused to even pop up the launcher, so I set PROTON_LOG=1
to get a log file. Turns out Steam had created a 32-bit wine prefix instead of a 64-bit one. After deleting the game's compatdata
folder and launching the game again it worked.
Today's update seems to have broken the game on proton, it crashes after pressing play and showing the splash screen for a bit.
Seems to be related to EAC, disabling it in the launcher makes the game run with Proton 8.0-2, but even better is that it seems to work just fine even with experimental, though I'll have to wait for later to actually try co-op.
Replying to https://github.com/ValveSoftware/Proton/issues/6140#issuecomment-1624013733
It looks that you ran it using DX12, which is kinda broken when using Proton. Try Vulkan version instead.
Is seems that with the latest update (The Kraken update) they updated EAC and its now crashing on the splash screen. Uninstalling it and disabling EAC in the launcher options makes the game works again, so its an incompatibility with newer versions of EAC.
@jorgicio I was always launching it with vulkan, idk why the logs would show otherwise.
@KDERazorback Launch the game with Proton Experimental, I was able to launch and play the game in co-op for a few hours last night.
@jorgicio I was always launching it with vulkan, idk why the logs would show otherwise.
@KDERazorback Launch the game with Proton Experimental, I was able to launch and play the game in co-op for a few hours last night.
Ok, I confirm that tried launching with Proton Experimental, it works but multiplayer got broken again after can't find the binary .exe. A similar issue happened in Epic version of Dead by Daylight.
@jorgicio I was always launching it with vulkan, idk why the logs would show otherwise.
@KDERazorback Launch the game with Proton Experimental, I was able to launch and play the game in co-op for a few hours last night.
Doesnt work for me. Tried with a clean compatdata in every scenario possible, tried Proton Experimental and Proton 8.0-2. Also tried GE-Proton8-6 without success. In all cases the game works perfectly on single-player if EAC is disabled on the game launcher.
When EAC is enabled for coop or online multiplayer, the game crashes on the splash screen while "Initializing" after a couple of seconds.
Log doesnt show anything relevant. Renderer was always set to Vulkan on launcher.
Tried to disable mangohud and steam overlay. Still not working.
Was working perfectly before the Kraken update last week with Proton Experimental and EAC enabled for Coop campaign.
I think they updated the EAC runtime and that broke compatibility with Proton.
Just want to add my 2 cents, for this new EAC issue post Kraken update. Was playing coop & multiplayer before the Kraken update just fine using Vulkan mode with high & stable fps, with proton exp & 535 Nvidia drivers.
After the update & when EAC is enabled, I get below 30 fps all the time, with large variations in frame time. If I go offline during a level (which presumably disables EAC), I instantly go back up to my old performance (200+ fps), even during the same level.
Just want to add my 2 cents, for this new EAC issue post Kraken update. Was playing coop & multiplayer before the Kraken update just fine using Vulkan mode with high & stable fps, with proton exp & 535 Nvidia drivers.
After the update & when EAC is enabled, I get below 30 fps all the time, with large variations in frame time. If I go offline during a level (which presumably disables EAC), I instantly go back up to my old performance (200+ fps), even during the same level.
So could you play in MP and co-op after the Kraken update?
Yes, I am able to play MP & co-op - however, my framerate drops from ~200 offline, to ~30, and the frame times are even worse.
Yes, I am able to play MP & co-op - however, my framerate drops from ~200 offline, to ~30, and the frame times are even worse.
How did you manage it to play MP? Because every time I want to try, it says that anticheat blocks me due to binary not found in the catalogue. I'm using the Vulkan version with Proton Experimental.
Thanks.
Yes, I am able to play MP & co-op - however, my framerate drops from ~200 offline, to ~30, and the frame times are even worse.
Based on my findings and the (outdated) results in protondb, I'm a little skeptic on this. Maybe you got something installed that us don't? Which OS are you using? GPU and driver version, etc?
I Just tested in a completely fresh install of ZorinOS 16.2 (based on ubuntu LTS) with latest updates, nvidia GPU with latest driver from the 535 version, latest steam, Proton Experimental, no tweaks, no modified drivers, no other programs (neither discord, OBS or anything) and it doesnt work at all. Crashes while initializing EAC if enabled.
If I disable EAC it works perfectly.
Maybe something to do with nvidia itself?
On my installation I have driver 525 and still nothing. My specs: OS: Zorin OS 16.2 KERNEL: 5.15.0-73-generic CPU: AMD Ryzen 5 2600X Six-Core GPU: NVIDIA GeForce RTX 2070 GPU DRIVER: NVIDIA 525.105.17 RAM: 80 GB
Been working great with Proton Experimental with EAC enabled, and now with Proton 8.0-3 released it works with that too.
OS: Arch Linux Kernel: 6.1.39-1-lts CPU: AMD Ryzen 7 3700X GPU: AMD Radeon RX 6600 XT (mesa 23.1.4) RAM: 48GB
Finally found a partial solution to the issue.
When launching the game, wine64 was throwing a segmentation fault error on dmesg that immediately crashed the game on the splash screen if EAC is enabled.
Upon investigating, it seems newer versions of EAC also require newer versions of some libs not available on many older distros (like ZorinOS 16.2).
Switched to the latest version of PopOS! with a lot of updated libraries and newer kernel but still the old fashioned 525 nvidia driver and finally the linux portion of EAC loaded properly and was able to actually launch the game with it enabled.
But now the game fails to enter any coop or multiplayer mode from the main menu due to "the game executable" not being found on the [EAC] catalogue. Tried deleting the compatdata again, verifying game files, installing it to the root drive, installing EasyAntiCheat runtime from within Steam but still not working.
It seems it wasnt a compatibility issue with Proton, but EAC requiring very up-to-date libs instead. This explains why @kattjevfel can play in Multiplayer/Coop.
The result is the same tho, not being able to play online since the Kraken update due to an updated EAC.
Replying to https://github.com/ValveSoftware/Proton/issues/6140#issuecomment-1646090792 Replying to https://github.com/ValveSoftware/Proton/issues/6140#issuecomment-1646279707
Sorry for delay in reply, nothing special really. I have a 2080 Super & 4090, both running ubntu 23.04 & both with 535.86.05 from the graphics driver repo. Proton 8.03 also slightly helped the framerate when EAC is enabled. Other than that I really made no other changes, having EAC proton helper downloaded or not made 0 difference.
Replying to https://github.com/ValveSoftware/Proton/issues/6140#issuecomment-1646713086
what kind of libs? I'm EndeavourOS, with recent libraries updated, and tried with Proton Experimental and still can't play MP due to binary cannot be found (the .exe with the Vulkan one).
Replying to https://github.com/ValveSoftware/Proton/issues/6140#issuecomment-1646713086
Same issue on steam deck :(
Still not working under Endeavour OS, having installed on an external drive. Any fix/workaround? Using Proton 8.0. (I don't want to try several Proton versions in a time, since the game has Denuvo)
Compatibility Report
System Information
I confirm:
steam-1029690.log
Symptoms
Reproduction
Proton 7.0-4
as the used Proton version, if not already