Unable to load Anti-Cheat

[Chronic]

I just recently tried to play after a month break and when I load the game it pops up saying that it can't find/load the anti-cheat then forces me to quit. Playing on a steam deck. Has something changed recently? Anyone else having this problem? I've made sure all updates have been applied and restarted multiple times. Thanks,

[MayaFaraday_Sharkmob]

Hello Chronic,

Steam Deck has never been supported by us. Valve marked the game as playable on Steam Deck, not Sharkmob. We haven't updated or changed anything, Bloodhunt has always been intended to be played only on Windows 10 and PS5, as those are the platforms and OS it is programmed for. It might work on other platforms or OS but we cannot guarantee that it behaves as intended nor can we help if it stops working.

[Noïram]

The discussions "launch error" and "help" both go into the same issue. As far as I know, it affects all Steam Deck users. The discussions include my suggestion on how to inform Valve of the issue (the company that allows the game to work properly on Steam Deck), my note of a temporary workaround (using Geforce Now), and another user's claimed solution. Although I personally could not get the game to work using their method (and it is annoying, so I did not spend much time trying to get it to work that way), and would suggest using Geforce Now instead, it could work for you.

When I informed Valve, the response I received is the issue was being sent to the team responsible for compatibility with the Steam Deck (to either be fixed, or to have the Playable tag removed from the game), but multiple submissions of the problem could not hurt.

[fok]

...i guess the glibc problem arrived at the deck. try this bellow. it worked for everyone i've told. you can also check protondb.com.
ACTUAL SOLUTION to play on LINUX:
install the flatpak version of steam, give flatseal permissions, install the game, play.
the problem is with the version of glibc that steam uses. flatpak uses a working version of glibc so there are no problems with the anti cheat.

[fok]

Originally posted by Noïram:

The discussions "launch error" and "help" both go into the same issue. As far as I know, it affects all Steam Deck users. The discussions include my suggestion on how to inform Valve of the issue (the company that allows the game to work properly on Steam Deck), my note of a temporary workaround (using Geforce Now), and another user's claimed solution. Although I personally could not get the game to work using their method (and it is annoying, so I did not spend much time trying to get it to work that way), and would suggest using Geforce Now instead, it could work for you.

When I informed Valve, the response I received is the issue was being sent to the team responsible for compatibility with the Steam Deck (to either be fixed, or to have the Playable tag removed from the game), but multiple submissions of the problem could not hurt.

until the glibc library is updated(it's been a long time) the issue won't be solved. the other possibility, which probably won't happen, would be steam downgrading the glibc library they use to a working version which is what flatpak does.

[Noïram]

Originally posted by fok:

until the glibc library is updated(it's been a long time) the issue won't be solved. the other possibility, which probably won't happen, would be steam downgrading the glibc library they use to a working version which is what flatpak does.

Alright, I quickly tested it, and looked into it slightly, and you seem to be correct. It works once I give the Steam flatpak access to my home directory (I did not do this during my first test; I was unclear on what permissions you were suggesting to provide to the flatpak).

I knew there was some issue with Steam and glibc, but this being the only EAC game I have in my library and have played (that I can recall at this time, anyway), I never ran into the issue, either with the Steam Deck or Tumbleweed (my main distro).

Very much appreciated.

[PavelDobCZ23]

This issue has been resolved in EAC itself, all the devs need to do is update the game with the latest EAC version, which I understand won't happen, but still, it's such a low effort fix and it's sad to see this problem.