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

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

• Use Steam Native Runtime
• Try Steam Flatpak
  It sounds like you've tried everything else otherwise.

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

Here on Manjaro, Testing branch, with kernel 5.15, default Steam, and Proton 7.0, everything seems to work. Try to reset everything to default, delete the prefix, and try again.

Hi, @daugustin.
I can confirm that.

Apex EAC works on my system also, but that is likely because they're using a different implementation of EAC.
Apex Legends uses easyanticheat_x64.so, which Insurgency: Sandstorm doesn't.
Insurgency: Sandstorm uses the EOS version of EAC, which provides the splash screen among other things.

If you were to launch Apex without EAC, you'd get into the main menu no problem, but the game would create a notification and boot you back out later, while EOS wouldn't let you launch the game at all.

@Zorrototo The only thing that I've not yet "reset", is to launch Steam with --reset.
I might try that on my laptop later, as it also has the same issue as my desktop computer and runs the same Linux distribution.

So far we have three reports of Gentoo systems that are unable to launch Insurgency: Sandstorm.

I'm on Ubuntu and have just gotten it to work. The only major change I made to make it run was switching to Proton Experimental and it runs well. The only issue I'm getting is only sometimes it will have difficulty starting and getting passed the main loading screen. However I reckon this is due to having FSR enabled, and it doesn't bother me much since this is a rare occurrence and the game typically starts as usual. I'm starting to wonder if this only works on certain distributions. Like I've said before, most users that have gotten it to work on protondb.com are on Arch or Ubuntu-based distros.

@sketch54 Yes, it also takes around 2 - 4 tries to launch fully. It shows a splash screen and then yields zombie processes. Stop from steam and try again repeatedly until it fully launches. I saw the same behavior when we had a brief EAC "alpha" (possibly accidental) last November, so my feeling is that this may not be EAC. I'm attaching a proton log, although I haven't tried to delve into it. It feels a lot like a failure to go fullscreen.

steam-581320_crash.log

I don't have Insurgency: Sandstorm (yet) but I do have Elden Ring, and what you've just mentioned with the game needing a few tries at loading before it works is a very similar problem between the two games.

@Irets make that four. Have been unable to launch the game on Gentoo as well, with the same "failed to load anti-cheat module" error. Apex Legends works fine. Can't say anything about other EAC EOS games as Insurgency Sandstorm is the only game with that implementation that I own.

Is there still no solution other than using the flatpak version of steam on Gentoo?

I tried a lot of things, even stracing it, couldn't find anything why it doesn't launch EAC. If you want to checkout the game, you can launch "Insurgency.exe" instead of "InsurgencyEAC.exe" (e.g. with steamtinkerlaunch). I was hoping this would still launch EAC in the background or something, but this is indeed the "offline" version. You can try the game and play against bots - the game itself works fine.

@daugustin, I just picked this up yesterday and have had a few games with EAC enabled, I did find that using the default Proton compatibility mode didn't launch the game (The EAC popup started and then nothing), but I switched to GE-Proton7-5, which is what I'm also using for Elden Ring and it launches just fine, no other command arguments used.

Insurgency was working great for me up until a week or so ago. Not sure what changed but now I just get a black screen after the initial EAC and sandstorm logo here's my logs:

==> .steam/steam/logs/connection_log_7777.txt <==


[2022-04-28 17:31:38] CCMInterface::OnConnectivityTestResult -- Start connecting to Steam

==> .steam/steam/logs/connection_log.txt <==


[2022-04-28 17:31:38] Connectivity test: Starting test, fetching 'http://test.steampowered.com/204'
[2022-04-28 17:31:38] [3,3] StartVoiceRecording() (was recording: 0)
[2022-04-28 17:31:38] [3,3] StopVoiceRecording() (was recording: 1)
[2022-04-28 17:31:38] Connectivity test: OK!
[2022-04-28 17:31:38] Connectivity test: result=Connected, in progress=0

==> .steam/steam/logs/content_log.txt <==
[2022-04-28 17:31:38] Game 581320 no longer tracking PID 137392
[2022-04-28 17:31:38] Game 581320 adding PID 137489 as a tracked process

==> .steam/steam/logs/stats_log.txt <==
[2022-04-28 17:31:38] [AppID 581320] CAPIJobRequestUserStats - no stats data in server response, we must be up to date

==> .steam/steam/logs/systemmanager.txt <==


[2022-04-28 17:31:38] Initializing System Manager
[2022-04-28 17:31:38] Node mode active on resume 0
[2022-04-28 17:31:38] wifi power management: 1
[2022-04-28 17:31:38] Error: BYieldingRunJob: failed to query system battery state

==> .steam/steam/logs/connection_log_7777.txt <==
[2022-04-28 17:31:40] IPv6 HTTP connectivity test (ipv6check-http.steamcontent.com / [2a01:bc80:8:103::9b85:fc12]:80 ([2a01:bc80:8:103::9b85:fc12]:80)) - TIMEOUT
[2022-04-28 17:31:40] IPv6 UDP connectivity test (ipv6check-udp.steamcontent.com / [2a01:bc80:c:103::9b85:e232]:27019) - SUCCESS

==> .steam/steam/logs/systemmanager.txt <==
[2022-04-28 17:31:40] Error: BYieldingRunJob: failed to query system battery state

==> .steam/steam/logs/configstore_log.txt <==
[2022-04-28 17:31:40] Flushed store 'install' to '/home/fayaaz/.local/share/Steam/config/config.vdf'

==> .steam/steam/logs/systemmanager.txt <==
[2022-04-28 17:31:42] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:44] Error: BYieldingRunJob: failed to query system battery state

==> .steam/steam/logs/custom_log.txt <==
[2022-04-28 17:31:44] IssueClientServiceCall: 25128992 ac9916fb 4 3

==> .steam/steam/logs/systemmanager.txt <==
[2022-04-28 17:31:46] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:48] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:50] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:52] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:54] Error: BYieldingRunJob: failed to query system battery state
[2022-04-28 17:31:56] Error: BYieldingRunJob: failed to query system battery state

Not sure if these are important:

Error: BYieldingRunJob: failed to query system battery state

IssueClientServiceCall: 25128992 ac9916fb 4 3

Did you try to delete the prefix folder, and use the normal Proton7 or Proton Experimental? It is working properly on my side I just checked.

Did you try to delete the prefix folder, and use the normal Proton7 or Proton Experimental? It is working properly on my side I just checked.

Thanks that solved it! Using Proton Experimental and launch options:

mangohud %command%  -nominidumps -dx12

Edit: I had to use GE-Proton-7-15 to get the first time DirectX install to work properly.

Getting black screen as well. Clearing compatdata didn't help, commandline options above didn't help either.

tried the launch options suggested above, tried disabling shader pre-caching, tried proton-GE and Proton Experimental, stuck on the launch banner, the EAC logo shows but moves very slowly in the bottom left of the banner, game doesn't launch, right side of banner stuck on "initialising", no .so easy anticheat file that I can see in the steamapps folder but there is a windows exe, just to note: Apex legends runs perfectly for me and I'm using Nvidia 515.48.07 driver

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.90
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor
Memory: 23.4 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

Yes no longer working for me either, I have been playing regularly until August, and after recent updates I get an error on the Splash Screen as EAC is initialising.

Launch Error
Failed to load the anit-cheat module.

I have tried the suggestions above with file validation and prefixes, and I have tried GE Proton 7.5, GE Proton 7.29 and Proton Experimental

It stopped working for me with the lateste Proton experimental update.
Now the game crashes before joining a server.

journalctl -p 3 -b outputs this for me:

[🡕] Process 5289 (InsurgencyClien) of user 1000 dumped core.

Stack trace of thread 5290:
#0  0x0000000000000000 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

I am on Arch with Linux 5.19.3-arch1-1 and amdgpu driver.
My launch options are DXVK_ASYNC=1 mangohud %command% -nominidumps

It works with Proton 7.0-4, but there are quiet some lags which I assume are due to texture and shader loading which were not that bad in Proton experimental.

@abienz

So, I've never had EAC load reliably, but I'll give you two hacky workarounds that generally have worked (and continue to work, since nobody seems to be patching this).

Trick 1:
Use the script linked here: https://github.com/ValveSoftware/Proton/issues/1328#issuecomment-511651465

Which I run as follows to load regedit: ./protoncfg.sh 7.0 581320 regedit

Yes, I'm using Proton 7.0 as well. In regedit, delete the following keys:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Valve\Steam\Apps\sandstorm_EOS_anticheat
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Valve\Steam\Apps\581320
HKEY_LOCAL_MACHINE\Software\Wow6432Node\EasyAntiCheat_EOS

Close regedit. Then retry launching from Steam. Steam will reinstall EAC in the winedir. I have to do this more often following patches, although that might be psychosomatic. (I should probably be crediting someone somewhere on the internet for this trick, but I can't recall who or where it was.)

Trick 2:
...And this is going to sound a little bit ridiculous, but here goes. The vast majority of attempts to launch the game show only the first splash screen but not the second, and the game is stuck in some state that doesn't generate error messages but also does not kill itself or load any further. You have to kill the processes manually or from steam. However, if I load a youtube video or do something else that adds a little bit of graphics lag as it attempts to load past the first splash screen, the game loads the second splash much more reliably and continues to launch normally. Last time I tried to spend a few minutes on it, it seemed like there might be a race condition in finding the game window...

Good luck all.

EDIT: I realized that the version of the bash script I'm using seems to be available only off site, so I'm going to paste it into a gist here. Credits to the link above: https://gist.github.com/privat3dancer/965f976ca7990e2a04e1856a22073fe2

LOL that's the script I made from pieces and bits from the internet :D here is the source http://gromano.fr/bludit/using-winecfg-or-regedit-on-a-proton-game-prefix

:+1: Funny to find people using the stuff I post on my "hidden"/personal blog :P (I write it in english so people can actually find something useful for them one day, and it is not really hidden since I posted a link to it once or twice on Github).

For the EAC issue on my side (I got to retest) I never had issue with this game (but I have with Vermintide 2 for example).

//EDIT: yeah, I started the game, I was still on Proton Experimental, it updated the prefix I guess as it took 5 seconds to launch, but I'm playing COOP on official matchmaking rght now for 10 minutes so EAC works here.

//EDIT2: do you have the Proton EasyAntiCheat Runtime installed? Not sure if required but I have it.

It stopped working for me with the lateste Proton experimental update. Now the game crashes before joining a server.

@puresick If this is still happening to you, could you provide more details (which type of server, random auto-match, etc)? I was unable to reproduce the issue on my AMD Arch machine.

I just today (26th Aug) updated my Arch system to the latest packages, and ran Insurgency Sandstorm with Proton Experimental, and I successfully got past the Splash panel, loaded up the game and completed a full round of Firefight, all seems to be working for me now.

I noticed there was also a hotfix for the game too, but the changelog didn't mention anything with Linux.

They didn't even announce the "Linux support" as far as I know so you'll never see changelog or changes related to Linux in my opinion.

@alasky17 Sure!

I tried joining an official PVP Push server with my region settings only having Europe selected. I have no mods installed.

My system specs are:

• Linux 5.19.4 (just updated, the comment above was with 5.19.3, but the current version made no difference)
• CPU: AMD Ryzen 7 3700X
• GPU: AMD Radeon RX 5500 XT (kernel driver: amdgpu)
• RAM: 32GB
• Gnome 42.4 (Wayland)

I just tried joining a server today after a new Proton Experimental updates has been installed via Steam, but that did not improve anything visibly.

I did some testing changing some of the "variables":

• Removed all launch options: No improvement
• Tried to join a community server (see server I chose in screenshot below - I do not know how to get the servers ip adress without connecting to it): No improvement
  
• Trying to joing official Coop Checkpoint server: No improvement
• Deleting [STEAMLIBRARY]/Steam/steamapps/common/sandstorm/EasyAntiCheat folder and verifying game files to reaquire them: Resulted in Insurgency: Sandstorm not starting up. I killed the process for it manually which took down Steam aswell. Restarting Steam started into another file verification process. Starting the game afterwards resulted in no improvement

EDIT:

Adding -dx12 as a launch option seems to work. I can successfully joing an official Versus Push server/match. The problem I am having with that launch option i.e. forcing DX12 usage is having bad micro-stuttering if I turn texture pool streaming on, which I have to because disabling it with -dx12 results in me having no proper textures ingame at all or only really low-res textures at best.

@alasky17 Seems like you are on a good path here: After copying the described files over from Proton Experimental to Proton 7.0 the game crashes exactly like with regular Proton Experimental.

As mentioned in the DXVK report, I don't know how to reproduce this. If anybody has got more info on this and can give me step-by-step instruction on how to actually make the game crash, as well as tell me which Vulkan driver is being used, please post there.

Just a heads up: It seems to be an AMDVLK issue. I was using AMDVLK but did not know that it was unsupported by DXVK. Using RADV solved the crashes.

I will open an issue on the AMDVLK repository soon.

Do you ALT-TAB and open the Steam overlay regularly?

I meant before it happens.

I had once a real FPS drop like going to 75 FPS to 20 then 10 then less.. it wouldn't go up, anytime, so I had to restart the game then it worked well.

Maybe there are settings that create bugs, I don't know. Try to change some settings and see if the issue is reproducible. Also maybe try to see if you can reproduce the issue solo, offline, with the minimum action going on (if possible, solo on a map offline).

Myself and a bunch of other users are suddenly being kicked from every server we join with "Kicked from server: Anti-Cheat: Client integrity violation". Game was working fine Friday night, there where no updates and then this suddenly started happening Saturday night.

I've tried reinstalling, clearing the prefix, a few different proton versions (experimental, hotfix, normal versions, GE ones including 43 which was the one the game was working with Friday night). Tried different launch arguments including with and without -dx12, no luck.

I did update my Nvidia drivers (RTX 3070) sometime Saturday, I can't recall if it was before or after I first tested sandstorm, haven't had a chance to roll back and see if that's causing any issues but I am getting a lot of crashing in a lot of games with the latest Nvidia drivers.

Thread with other reports, for some the game still works, for others it doesn't: https://old.reddit.com/r/linux_gaming/comments/10ihf1x/eac_doesnt_work_with_insurgency_sandstorm/

Edit; I'm starting to see a few threads on this on steam discussions as well, may not be a Linux/Proton related issue, could just be EAC playing up.

I haven't had that specific issue, but have been having a tonne of issues getting the game to even open for the past couple of days. Constantly getting stuck on the splash (the one that opens after the EAC splash)

More details:

• Pop_OS! 22.04 Linux 6.0.12-76060006-generic
• No VR
• RTX 3060, driver version 515.65.01-1pop0~1666367711~22.04~b8c0232
• Not using Flatpak Steam. Proton EasyAntiCheat Runtime installed. Using Beta branch Steam. Tried Proton Bleeding, Proton Next, and current Proton.
• Using gamemoderun launch option only

I haven't had that specific issue, but have been having a tonne of issues getting the game to even open for the past couple of days. Constantly getting stuck on the splash (the one that opens after the EAC splash)

Do you have a VR headset? I've had the same issue, rename the OpenXR folder in steamapps/common/sandstorm/Engine/Binaries/ThirdParty/ to "_OpenXR" (or something else). That resolved it for me. This appears to happen to Windows users as well.

I haven't had that specific issue, but have been having a tonne of issues getting the game to even open for the past couple of days. Constantly getting stuck on the splash (the one that opens after the EAC splash)

Do you have a VR headset? I've had the same issue, rename the OpenXR folder in steamapps/common/sandstorm/Engine/Binaries/ThirdParty/ to "_OpenXR" (or something else). That resolved it for me. This appears to happen to Windows users as well.

I have the same problem as @JellyWX. I don't hade a VR but will try your fix later anyway.

I've played quite a bit the last few weeks but haven't had a single EAC error. I did delete the steamapps/compatdata/581320 folder when trying to fix the steam overlay issue though. I'm using Proton 7.0-5. Not using any launch options.

Is anybody else getting this horrible stuttering both in the main menu and in match? I've tried clearing shader cache, compatdata, and reinstalling the game. The stuttering sometimes subsides but starts up again within a minute or so, and it does not go away like shader compilation does.

Is anybody else getting this horrible stuttering both in the main menu and in match? I've tried clearing shader cache, compatdata, and reinstalling the game. The stuttering sometimes subsides but starts up again within a minute or so, and it does not go away like shader compilation does.

Are you launching with the -dx12 flag? If so, per a previous comment here having the texture pool streaming option on in-game could cause stuttering when running with -dx12.

Personally, when the game was actually working for me, I wasn't using the -dx12 flag and the game was running very well for me at max settings on my RTX 3070 & 5900x.

Replying to https://github.com/ValveSoftware/Proton/issues/1651#issuecomment-1400303234

No, unfortunately I'm not running dx12. There is no difference in the amount of stuttering when using max and lowest settings. I'm using a RX 6700 XT & 13600k

Verifying game files on every reboot allows me to launch. This forces the EOS installer to re-run is my guess as to why this resolves it for me.

...seems resolved now, I guess either by the Steam client update or by the various patches to the client runtime and Proton bleeding edge that just shipped.

Spoke too soon. Stopped working again now.

This has suddenly started working again for me, I've not changed anything or done anything.

Did some more testing, the stuck on loading screen issue appears to happen randomly and you can get to the main menu by relaunching the game at most a few times. Now to the stuttering, weirdly this only happens when the game is connected to the New World Interactive servers. If the game is launched in offline mode there is no stuttering, but of course you can't play anything other than bot matches.

Looks like I'm not the only one having EAC issues since v1.13 or the subsequent hotfix. However, my issue is a little different, I have no issues launching/playing sandstorm using the EAC exe launcher. I don't receive any sort of EAC invalidation error or have issues getting kicked, BUT I do have issues with trying to exit the game, the process doesn't seem to terminate properly and Steam will still show the game running. When bringing up task manager, there is no insurgency sandstorm process to terminate, instead I noticed one of my logical cores maxed out at 100% usage. The process maxing this usage is "system", so I can't terminate it. The only way I can fully terminate the process is by restarting the whole PC. As a test, I launched the game using the non-EAC exe located in the same parent folder (insurgency.exe) and had no issues exiting the game. SO, this leads me to believe there is some on-going bug between EAC and the game.

If anyone would like a workaround just to be able to play the game and omit EAC-associated issues until things are patched, I am running 2 community servers without EAC (one modded, one vanilla). You just need to first launch the game with the non-EAC exe (typically located at \SteamLibrary\steamapps\common\sandstorm). Then in community servers, make sure modded is checked on the left and checkpoint is selected from the mode dropdown. Then search "Nancy's Insiders" and you should see the 2 servers.

Update. I have now also started to get EAC errors. Not often but sometimes. Usually only a restart of the game is required to fix it.

The game still doesn't launch sometimes. Renaming OpenXR didn't fix it.

It seems I spoke too soon before. Can't get the game to get past the splash again: verifying files, restarting, using different Protons, etc. makes next to no difference. I got it to open once using Proton GE 7-48, but even then couldn't get into any matches due to EAC integrity.

Has anyone successfully found a workaround for the steam overlay?

These are the only log entries I have when grepping for overlay:

3590458.849:016c:0170:trace:loaddll:build_module Loaded L"C:\\Program Files (x86)\\Steam\\gameoverlayrenderer64.dll" at 0000000012680000: native 3590468.147:016c:0170:warn:seh:OutputDebugStringA "[2023.04.02-06.52.46:826][ 0]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden\r\n" 3590468.147:016c:0170:warn:seh:dispatch_exception "[2023.04.02-06.52.46:826][ 0]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden\r\n" 3590493.272:016c:0170:warn:seh:OutputDebugStringA "[2023.04.02-06.53.11:956][872]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden\r\n" 3590493.272:016c:0170:warn:seh:dispatch_exception "[2023.04.02-06.53.11:956][872]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden\r\n"

Nothing to do as far as I know. The overlay opens in the initial EAC popup, not in the game, so you have no overlay. Maybe if you find a way not having the EAC popup on game launch it could fix the issue.

The overlay opens in the initial EAC popup, not in the game, so you have no overlay.

This is correct. I managed to lag the splash screen long enough to trigger the overlay key combo, which works fine while the splash is up. So the splash window opens and closes, and the overlay process appears exit with that window. The game window itself doesn't get the overlay. After the game fully launches, I can see a process called gameoverlayui trying to load repeatedly and exit.

[gameoverlayui] <defunct>
[gameoverlayui] <defunct>
[gameoverlayui] <defunct>
 /home/xxxx/.local/share/Steam/ubuntu12_32/gameoverlayui -pid xxxx -steampid xxxx -manuallyclearframes 0 -gameid 58132

But I'm a little confused why the log claims it loads gameoverlayrenderer64.dll, i.e. as a dll. Is the working overlay supposed to be a wine process or native process? If native, why is it trying to load the 32-bit version? And how safe is it to try to breakpoint these processes with this EAC crap running?

Continue to get kicked when trying to join online due to EAC NullClient error. According to protondb, the game seems to work for some but not others...

@Swivelgames I don't know why this happens, but when it does, I can still fix it by forcing a reinstall of EAC from the setup script. See my comment above: https://github.com/ValveSoftware/Proton/issues/1651#issuecomment-1224906309

Are you sing latest Proton 8 version? Do you have the EAC Runtime installed in Steam? Did you try to remove the prefix to generate a clean one from Proton 8?

If it helps anyone, I've had EAC Unexpected Error #1 in ArchLinux recently that prevents the game from running when using Steam Native and Steam Runtime.

After looking around for a bit, it turns out that this is because EAC needs a certain patch for glibc in order for it to work (that ArchLinux probably removed recently).

The workaround for me is to use the Steam version from Flatpak that includes its own compatible glibc which is kinda nice as it also gives some degree of isolation/sandboxing.

Thanks @kisak-valve i'm new for github and my limited english skill

If it helps anyone, I've had EAC Unexpected Error #1 in ArchLinux recently that prevents the game from running when using Steam Native and Steam Runtime.

After looking around for a bit, it turns out that this is because EAC needs a certain patch for glibc in order for it to work (that ArchLinux probably removed recently).

The workaround for me is to use the Steam version from Flatpak that includes its own compatible glibc which is kinda nice as it also gives some degree of isolation/sandboxing.

@jkcdarunday if you on Arch base distro just install glic-eac in AUR .No config needing

easy fix without techticual knowlage by switch both locale gui game menu with US insteadd of TH

@Tune45 glibc-eac is upstreamed to Arch's main glibc, so installing glibc-eac usually isn't necessary. However, even after installing glibc-eac (and lib32-glibc-eac), I'm still not able to get it to work.

I've tried:

• Proton Experimental
• Proton Hotfix
• Proton 9.0-1
• Proton 8.0-5
• Proton GE 9-5

With and without glibc-eac.

I'm using zen kernel.

Thank you @privat3dancer for your regedit trick; it definitely saved me a lot of time going through all the different Proton versions I tried, before and after installing glibc-eac.

glibc-eac is upstreamed to Arch's main glibc

It is not.

The patch was removed and haven't been added back since.

However, even after installing glibc-eac, I'm still not able to get it to work.

You also need lib32-glibc-eac btw.

@Revival8697 Yeah, I realized it had been rolled back after the fact, but forgot to update my comment. 😅

And, indeed, I also installed lib32-glibc-eac.

However, I posted in #7721 that I found (with the help of someone in the GZW Discord) an old workaround that Star Citizen lug-helper left over in my /etc/hosts. Commenting out or removing this line out in my /etc/hosts fixed the NullClient issue:

127.0.0.1	modules-cdn.eac-prod.on.epicgames.com #Star Citizen EAC workaround

Now EAC can communicate with the EAC servers again, instead of been looped back.

However, I'm now getting the error #1 when the initial EAC prompt pops up. I'll poke more at it tomorrow 👍

@BRS5672023 Arch's AUR has [lib32-]glibc-eac-bin as well if you don't want to build it 🙌

Clean Proton 9 prefix, EAC popup downloads the EAC update, then EAC error appears on screen. Here are the EAC logs:
anticheatlauncher.log
loader.log

Solved. Back to playing again! by reinstalling lib32-glibc-eac + glibc-eac after removing the following from my /etc/hosts from an old workaround that was added for Star Citizen by lug-helper:

127.0.0.1	modules-cdn.eac-prod.on.epicgames.com #Star Citizen EAC workaround

I'll post an update to my ProtonDB entry :+1:

still broken, not great considering how behind glibc-eac is by now. Is there a way to use some runtime sanboxing shenanigans to get glibc-eac running only for this game? I'd prefer not to run a seperate steam flatpak instance for this one game

how behind glibc-eac is by now

Like 10 days? You could just modify the PKGBUILD to match the repo one.

how behind glibc-eac is by now

Like 10 days? You could just modify the PKGBUILD to match the repo one.

Last update was in july as far as I can tell, either way my main concern is it messes up debug symbols for programming so a system install ain't great since I'd have to containerize everything while debugging.

Last update was in july as far as I can tell

I meant the last update only include 10 days worth of commits.

Anyway, if you want keep it up-to-date, just modify the PKGBUILD to the equivalent commit and checksum.

There's a lot of mixed comments here. I can't get past the launcher just like @Zorrototo, is there any workaround or is the game borked? I see people recommending a variety of libs to install but no clear answer to which specific ones.

Yes I just deleted the old prefix, verified the game files, and started the game, it is exactly the same as last time I checked on Proton 9, and did the same again with Proton Experimental bleeding edge. It is broken.

There's at least a few reports on protondb from the last few weeks of it apparently working with GE/experimental. I've had no such luck no matter what I try, just fails on the launcher as usual. Anyone else made progress?

There's at least a few reports on protondb from the last few weeks of it apparently working with GE/experimental. I've had no such luck no matter what I try, just fails on the launcher as usual. Anyone else made progress?

You need glibc-eac and lib32-glibc-eac on Arch distros.

I'm seeing quite a few reports that this game has apparently stopped working on Steam Deck after the 3.6.19 update (same error code), and I suspect it's related to the above issues with glibc on Arch Linux.

After the latest update, I've been getting kicked for anti-cheat authentication timeouts. Not found a fix yet

After the Dec 12 update, the game is running fine. It also no longer requires the DT_HASH patch for glibc. Users using glibc-eac on Arch can now return to the official package.

On the latest Proton versions I've been having some odd issues

• On experimental, the game (despite stating it is at 180 FPS in mangohud) feels really choppy- like its syncing down to 60hz on my 144hz monitor
• This issue goes away on Proton 9, but on Proton 9 steam overlay and game recording don't work

I think I've had the choppiness on Hunt as well, but not as noticable. I couldn't find anyone else talking about these issues though- anyone else having similar problems?

E: Found a thread, this isn't specific to Sandstorm. Swapped to GE-9-27 and its fine

• On experimental, the game (despite stating it is at 180 FPS in mangohud) feels really choppy- like its syncing down to 60hz on my 144hz monitor

This should be fixed in Steam Beta.

On the latest Experimental version. Been experiencing "Failed to get the process' path" error from EAC, but only when game is installed in non-OS partition. When game is on /home, game launches normally.

@NAS-KAR hmm the game is working fine (at least co-op) on my end with experimental and bleeding edge, and this is with an external partition. Does it still happen on your end? is the path to that partition somewhat long? if so setting this as the game launch parameter might help PROTON_SET_GAME_DRIVE=1 %command%