Open ricardoalcantara opened 6 years ago
"It's likely that some games using complex DRM or anti-cheat systems will be difficult, or even impossible to support."
We will probably need to wait for a native version.
"It's likely that some games using complex DRM or anti-cheat systems will be difficult, or even impossible to support."
We will probably need to wait for a native version.
I was somewhat hopeful since proton is an official product of valve they would try to talk to developers of popular DRM services like easy anti cheat and denuvo to work together to find a solution and make them work on proton.
@Rabcor maybe they are. Lets have faith, valve already made something really historical.
Implementation of some kind of whitelist/integration of anti-cheat systems into Proton is tracked here: #1468
I can play online on community server with EAC disabled, but there is still an issue, when I quit the game, the process InsurgencyEAC.exe doesn't exit and needs to be manually terminated for Steam and Proton to properly finish game execution.
Will we ever see a fix to this Easy Anti-Cheat issue? Valve was supposedly working with them a year ago, but we have heard nothing. Was this dropped?
As far as I know there is absolutely nothing new and that's probably a sign that there was absolutely no progress at all. We can also imagine that having your market competitor buying EAC probably didn't help but I can confirm anything about that, just guess game.
@Zorrototo Epic Games acquired Easy Anti-Cheat before they announced working with Valve to fix this. Epic Games buying them has nothing to do with this.
Any updates on this topic? I don't understand why this problem was solved with Squad, but is not with Insurgency.
I doubt EAC is working for any game under Proton.
Squad has a working EAC for wine64. Seems like this should be doable.
https://github.com/ValveSoftware/Proton/issues/938#issuecomment-655405271
We finally have official Linux support for EAC from Epic games and linux users are pushing the devs to add support for it soon.
Here's the main thread for it but some people are saying that they might hear this out better on their Discord server. https://steamcommunity.com/app/581320/discussions/0/2954914688104040461/
I created a ticket asking if they've changed their minds at all with the recent EAC developments and was able to get a response on their current status:
The team has heard about EAC enabling Wine/Proton compatibility, but for now, it hasn't been discussed. We're working on resolving some issues that came along with the release of Insurgency: Sandstorm on console for the time being.
Unfortunately not a yes for support, but looks like it's not out of the question anymore?
EAC seems working- Proton 6.3-7, latest game ver (1.11). Still some issues starting the game up though
EAC seems working- Proton 6.3-7, latest game ver (1.11). Still some issues starting the game up though
Confirm. It works!
There hasn't been anything official from the team mentioning enabling EAC for Proton, so this may just be a similar scenario to that seen in e.g Paladins, where it'll work for a little while and revert to not working again. Have any of you checked whether EAC is actually running in the background or if the logs say it successfully started?
There are also mentions of EAC not functioning properly in the discord as well, so the hype will be short-lived, it seems...
There hasn't been anything official from the team mentioning enabling EAC for Proton, so this may just be a similar scenario to that seen in e.g Paladins, where it'll work for a little while and revert to not working again. Have any of you checked whether EAC is actually running in the background or if the logs say it successfully started?
There are times where I have been kicked for EAC, or been told by the game that EAC isn't running (in which case restarting Steam has fixed this). This has mostly happened when either restarting the game without restarting Steam, or some issue with lobbies.
There are also mentions of EAC not functioning properly in the discord as well, so the hype will be short-lived, it seems...
I'm guessing that it's somewhat system dependent at the moment, possibly due to bugs in Proton. The game (with EAC) is still working for me as of this moment, and has been most of tonight, with the exception of having some AC issues when playing in a lobby rather than as a solo queue. Interestingly, the other member of the lobby (who was on Windows) also got kicked for EAC timeout when I did
Edit, here's the contents of the EAC log file, which may be telling of if EAC is loaded or not. This is from loading the game in the play session I'm currently in, which seems working fine to me.
[21:11:41:573] [Windows] [EAC Launcher] [Info] [] Localization file loaded, using en_us.
[21:11:41:885] [Windows] [EAC Launcher] [Info] [] Embedded resources successfully loaded.
[21:11:42:003] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:004] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:005] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:007] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:010] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:011] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:014] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:015] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:018] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:019] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:024] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:024] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:024] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:030] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:031] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:043] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:044] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:068] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:070] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:071] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:083] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:084] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:113] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:113] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:113] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:113] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:113] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:134] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:134] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:134] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:134] [Windows] [EAC Launcher] [Info] [] Current progress: 0 (0/0).
[21:11:42:229] [Windows] [EAC Launcher] [Info] [] Launcher finished with: 301, 'Easy Anti-Cheat successfully loaded in-game'.
[21:11:42:229] [Windows] [EAC Launcher] [Info] [] Downloaded 0 bytes in 304 ms (0.00 KB/s)
[21:11:42:229] [Windows] [EAC Launcher] [Info] [] Successfully initialized the Easy Anti-Cheat service, waiting for game window to become visible.
[21:11:42:229] [Windows] [EAC Launcher] [Info] [] Unlocking the launch lock, allowing next game to launch to take place.
Without even looking into log or whatever, the devs said they might look at it in the future but was not their priority. Was there a significant game update prior to EAC working? Any announcement? if answer is no, then it is like other occurrence, where EAC wasn't working properly on other games, you'll soon see nothing has changed and you can't play on Proton on this EAC protected games, it is only temporary EAC issue.
There was a major update released yesterday, after which I tried launching the game via Proton again and have had mostly success. I do still suspect EAC is functioning, since as I said I have been kicked by it with failed authentication and a null client error on a couple of occasions, which would indicate surely that EAC is validating requests?
Even if there was an update to the game I'm still pretty confident this is a temporary issue and EAC is just not working properly, hence why people can connect to server under Proton.
At least some people would know if it was officially enabled, so far to me it just looks like the usual EAC not working issue that happened on multiple occasion on multiple games previously. Enjoy it while it lasts, but don't get too exited for that.
I see a similar log to JellyWX. The log says it's downloading 0 bytes, and I confirm with curl that it pulls down an empty file. Nevertheless ps shows a large number of EAC processes running.
[nobody] 1244436 0.0 0.0 31076 25004 ? S 00:14 0:00 /bin/sh -c PROTON_LOG=1 /home/[nobody]/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=581320 -- '/home/[nobody]/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier'/_v2-entry-point --verb=waitforexitandrun -- '/home/[nobody]/.local/share/Steam/steamapps/common/Proton 6.3'/proton waitforexitandrun '/home/[nobody]/.local/share/Steam/steamapps/common/sandstorm/InsurgencyEAC.exe'
[nobody] 1244437 0.0 0.0 30288 24380 ? S 00:14 0:00 /home/[nobody]/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=581320 -- /home/[nobody]/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/_v2-entry-point --verb=waitforexitandrun -- /home/[nobody]/.local/share/Steam/steamapps/common/Proton 6.3/proton waitforexitandrun /home/[nobody]/.local/share/Steam/steamapps/common/sandstorm/InsurgencyEAC.exe
[nobody] 1244438 1.1 0.0 4624 676 ? S 00:14 0:00 /home/[nobody]/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/pressure-vessel/bin/pv-bwrap --args 26 /usr/lib/pressure-vessel/from-host/bin/pressure-vessel-adverb --generate-locales --fd 21 --regenerate-ld.so-cache /run/pressure-vessel/ldso --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu --set-ld-library-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/aliases:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/aliases --exit-with-parent --subreaper --shell=none --terminal=none --ld-preload=/home/[nobody]/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so --ld-preload=/home/[nobody]/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so -- /home/[nobody]/.local/share/Steam/steamapps/common/Proton 6.3/proton waitforexitandrun /home/[nobody]/.local/share/Steam/steamapps/common/sandstorm/InsurgencyEAC.exe
[nobody] 1244744 0.0 0.0 27260 4600 ? Ss 00:14 0:00 /usr/lib/pressure-vessel/from-host/bin/pressure-vessel-adverb --generate-locales --fd 21 --regenerate-ld.so-cache /run/pressure-vessel/ldso --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu --set-ld-library-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/aliases:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/aliases --exit-with-parent --subreaper --shell=none --terminal=none --ld-preload=/home/[nobody]/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so --ld-preload=/home/[nobody]/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so -- /home/[nobody]/.local/share/Steam/steamapps/common/Proton 6.3/proton waitforexitandrun /home/[nobody]/.local/share/Steam/steamapps/common/sandstorm/InsurgencyEAC.exe
[nobody] 1244768 0.3 0.0 46132 19460 ? S 00:14 0:00 python3 /home/[nobody]/.local/share/Steam/steamapps/common/Proton 6.3/proton waitforexitandrun /home/[nobody]/.local/share/Steam/steamapps/common/sandstorm/InsurgencyEAC.exe
[nobody] 1244771 0.2 0.0 1826196 27644 ? Sl 00:14 0:00 steam /home/[nobody]/.local/share/Steam/steamapps/common/sandstorm/InsurgencyEAC.exe
I did get an EAC kick immediately on connect to one specific server with the error NullClient. This is a different behavior from pre-1.11, where it would generally allow a 2 minute run before an EAC timeout.
LogGameState: Warning: AINSPlayerState::OnTeamChanged Invalid TeamInfo, TeamId is 1^M
15318.360:014c:0150:warn:seh:OutputDebugStringA "[2021.11.21-05.28.01:275][725]LogINSPlayerController: Display: Kicked by server: Anti-Cheat: Anti-cheat client protection not active (NullClient).\r\n"
The InsurgencyEAC.exe processes are all running. But this is the only server on which I've seen an EAC problem so far.
The log says it's downloading 0 bytes, and I confirm with curl that it pulls down an empty file.
This is more than likely an indicator that EAC is not working correctly. As with other games that have had similar anomalies with EAC blobs being 0 bytes causing some to start working out of the blue, this usually get patched a few days to a few weeks later and players will start being kicked again.
As much as I want the game to keep working too, we probably shouldn't expect it to stay this way unless the devs explicitly announce that they will be supporting Linux.
I have had to turn shader pre-caching off to get it to reliably start up but can confirm this has been working for a good few days now on official PvP servers.
we probably shouldn't expect it to stay this way unless the devs explicitly announce that they will be supporting Linux.
You jinxed it. The small patch yesterday seems to have broken it again. Oh well, the party's over.
Told you guys.
Well damn I just bought the game and now it broke again.
Game is broken? How so?
Anticheat works again. I tried using Proton-6.21-GE-2 and Proton Experimental and got the same result, being kicked out after a few minutes of online play.
Edit: If someone else still has it working I would like to hear about that.
Latest hotfix post (link) addresses their current status with EAC support:
Hello penguin pals, this message is being written for you by someone who has in their lifetime been a self-described Linux-head. Yes, we are very much aware that EAC announced Proton and Wine compatibility. Please understand however that we would still need to do quite a bit of development work to properly support Linux, and at this point in time we do not have that capacity. Thank you for your understanding!
Is this promising or still a problem with using an older version of EAC: https://store.steampowered.com/news/group/4145017/view/3137321254689909033
It's great that they're making it easier and easier, but I fear it isn't promising until there are genuine motivations that even business executives can understand: i.e. revenue.
After the first public report of Proton+EAC compatibility, it took NWI over two months to issue a statement on it buried at the bottom of a changelog. (Great comms guys!) Proton is clearly not a business priority for them, and I guess there's no internal interest in it. They haven't really explained why it is they claim significant development work would be needed for Proton support, especially given that we've been able to unofficially "alpha" the game on the platform ourselves. The small number of platform-specific bugs we've encountered can't possibly entail more than a few hours of development effort if they even felt motivated to fix them.
Since it's closed source, there's nothing the community can do about it that doesn't carry significant risk of user bans. (Anything attempted on the client side wouldn't look any different to them from a hack.) I fear that unless Valve really creates consequences for developer revenue streams on steam, we will not see them lift a finger on this.
Steam Deck support can be motivating for many devs. But maybe this game is not the best to focus on this portable console/PC. On the other hand, enabling EAC Linux support would redeem themselves from the lies they sold us the game on, they cancelled the Linux version after release, refused me my refund because I played too much and asked too late (was booting to my Win 7 old system to play this game with friends).
so, I found in this folder
~/.local/share/Steam/steamapps/compatdata/581320/pfx/drive_c/users/steamuser/AppData/Roaming/EasyAntiCheat/eb330869cd5f4881b0a8a0220a8c284d/2324da9a1c0341eea4cf43c070760c75/
an executable called easyanticheat_linux_x86_x64.eac
The game apparently has the Epic Online Service thing, so it may not be the same as the new simpler method of enabling anticheat, so there might no be a easyanticheat_x64.so file alongside the EasyAntiCheat_x64.dll file as explained here https://partner.steamgames.com/doc/steamdeck/proton (but I can't find the documentation for the EOS implementation).
So maybe there is hope. But for sure without official announcement don't get your hopes too high.
//EDIT2: a friend just confirmed on his Windows installation he has a different file:
C:\Users\UserName\AppData\Roaming\EasyAntiCheat\3bc138d96fb24d9597d4bbff23b9ecee\c5b7c99d0d6f40faa323823e4dff37ca\easyanticheat_wow64_x64.eac
so this time this may smell good, hope for official info sooner than later
I have been playing just now with Proton Experimental Bleeding Edge and all seems good. Can anyone else confirm multiplayer is working consistently?
Yes it is, the question is not is it working consistently, because it is, the question is will it last, is it now properly configured/enabled by the devs. It seems like from my poor investigation that it is now enabled by the devs and working but no official info and the fact EAC is often broken after an update still leave doubts.
On another note I have issue with the Steam overlay, it seems to activate in the EAC popup before the game starts (I see the FPS counter in the popup), and then there is no overlay in the game (no FPS counter, and no possibility of opening the overlay). Maybe this can be fixed in Proton somehow, but I didn't figure that out, if anyone has any idea that would be great. Maybe this should be reported to @kisak-valve as it is most likely an issue with Proton and/or Steam for Linux.
[581320] Insurgency: Sandstorm EAC module failure
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5662. @Irets posted on 2022-03-11T00:14:36:
Upon launching Insurgency: Sandstorm, an EasyAntiCheat splash screen will pop up saying "Launch Error, Failed to load the anti-cheat module" and at this point the only way forward is to click the "Exit" button below the message.
I've tackled with this issue for about a week now and have found a probable source of the problem: easyanticheat_linux_x86_x64.eac.metadata and easyanticheat_linux_x86_x64.eac are missing from _~/.steam/steam/steamapps/compatdata/581320/pfx/drivec/users/steamuser/AppData/Roaming/EasyAntiCheat/eb330869cd5f4881b0a8a0220a8c284d/2324da9a1c0341eea4cf43c070760c75/.
From my understanding these files should be present after the EAC installer has done it's job when Steam is running the installscript on a fresh prefix, but they never appear, thus causing EAC to bail on game start.
To try to solve this issue, I've tried the following:
I will include service.log, anticheatlauncher.log and loader.log from _~/.steam/steam/steamapps/compatdata/581320/pfx/drivec/users/steamuser/AppData/Roaming/EasyAntiCheat service.log anticheatlauncher.log loader.log
Is this the right place to ask for support or report the issue? I'm not very familar with Github.
Cheers.
@Irets You mentioned that you tried copying the eac files across but they get deleted when you start the game.
Have you tried setting that folder to read-only? This is the approach that Squad has used for a long time now, see this for reference: https://squadfm.org/#installation-setup
Hi, @abienz. I asked my friend to send me the two missing files again, placed them in to the folder and set it as read-only. Unfortunately, I'm still faced with the "Launch Error, Failed to load the anti-cheat module" message but this time the two files don't get deleted from the directory.
The guide also mentioned about setting _pfx/drivec/users/steamuser/Temp to read-only also, so I tried that too. No success yet.
There are quite a few reports of this working over the last couple of weeks.
Did this use to work for you too? Or are you trying to get it working for the first time with no luck?
First time with no luck.
The previous time I played Insurgency: Sandstorm was on November 19, 2021. For a week the game let linux players in because the anticheat was broken.
Yeah, I was concerned this recent access has been the same issue, I would like to hear from other posters of the game still works for them.
@abienz At least for me, I haven't had any problems with Insurgency: Sandstorm, it has worked out-of-the-box, with Proton Experimental, at least for a week now.
@Irets it sounds like it may be an environmental issue then, or perhaps caused by an update.
Some things to try.
I haven't been following this topic very closely for some time but it seems that many people on protondb.com have found luck with just switching to Proton Experimental. As of now (~13 hours ago) the latest report states that it "Works out of box with proton experimental" and the site has given reviews for the last 2 weeks. It seems as though most people having been using Proton Experimental or Bleeding Edge. This could just be another lapse in EAC's integrity like it was back in November but it's been going pretty strong for about 2 weeks now.
I didn't have luck with Steam Native Runtime
Installing Flatpak & Steam got me past the EAC splash screen, but something else caused the game to not load all the way. I checked EAC logs and it's folder to see everything to be in order. Even the two missing files were present. It seems that the Flatpak version of Steam was able to properly install & initialize EAC.
I'm not planning on keeping Flatpak on my system, but maybe this experiment helps someone to come up with ideas to try on the non-Flatpak version of Steam & Insurgency: Sandstorm.
I feel like I'm out of options at this point but thank you to everyone who has taken their time to assist.
I'd be interested in hearing from other Gentoo Linux users about how the game runs on their system with Steam from the steam-overlay repository.
First, I'll say that EAC is indeed now working. Steam overlay is not. Frame rates are nicely much higher than in Windows, although there's some graphics stutter and some input lag I'm still trying to pin down.
Second, @Irets, as far as the EAC module problems, I'm not familiar with your distro, but I wonder if you're tripping some security modules/profiles that you have installed. For example, something with SELinux/Apparmor could be going on. The way EAC behaves is very much like a dropper. Do you see anything relevant in your audit.log ?
Could the EAC problem be specific to certain distros? Most of those reviews on protondb.com were from Arch or Ubuntu users. Another recent report (from a Mint user) states that Steam Overlay does not work at all for him too.
@privat3dancer My kernel is quite lenient on security features and I don't use Apparmor or SELinux.
Nothing out of the ordinary gets logged in 'dmesg' or syslog when Insurgency: Sandstorm is run. Having Steam output to a terminal when starting the game doesn't print any permission errors either.
I also tried the distribution kernel to rule out the possibility of my own kernel build interfering with something. But because the Flatpak version of Steam was able to load the EAC module on game start, the issue very likely lies in user space.
I'd be interested in hearing from other Gentoo Linux users about how the game runs on their system with Steam from the steam-overlay repository.
Yes I'm seeing the same thing on Gentoo with native install, although Apex with EAC works fine.
€dith: In steamapps/compatdata/581320/pfx/drive_c/users/steamuser/AppData/Roaming/EasyAntiCheat/somerandomids/...
there is a loader.log that says:
[2022.03.16-16.47.17] Download Progress: 100
[2022.03.16-16.47.17] [Connection] Connect result: No error (0) Response Code: 200 Destination IP: 18.66.2.89
[2022.03.16-16.47.17] Download Progress: 100
[2022.03.16-16.47.17] [EAC Callback] Code: 507. Message: 'Failed to load the anti-cheat module.'.
Compatibility Report
System Information
I confirm:
Symptoms
Insurgency: Sandstorm local game works with a minor framedrop, but runs smooth even on Very High, but does't work for online game because Easy Anti-Cheat will kick you.
Reproduction
Just try online game.