Enable new Proton (Steam Deck/Linux) support for EAC

[Pierogo]

Hello!
Now that Epic Games officially supports SteamOS/Linux/Wine/Proton in Easy Anti-Cheat, on behalf of all Linux players I'd like to ask the devs for enabling it so we can play :)

According to the post on Epic's dev blog, "developers can activate anti-cheat support for Linux via Wine or Proton with just a few clicks in the Epic Online Services Developer Portal"

I'd love to play Vermintide on my PC and the lack of EAC support was the only thing holding me back.

Huge thanks!

[®omano]

Would be great to have support sooner than Deck release. Hope to play it soon again (currently have to boot to my old Windows 7 installation, and when/if I do, I usually have big updates for the game so I end up half of the time no playing it... and rebooting to Linux). Having my last EAC games compatible with Linux would make me play them more.

[topi]

Still looking forward to playing this with some linux friends :).

[Day #2357 of being a Pod-Frog]

Waiting for this, as well.

[Zoot™ Gaming]

patiently waiting for eac to be changed

[Planewalker]

Just want to give my +1 here.

Happy xmas to those who celebrate it and happy holidays to those who have it.
Happy workjoy to those who have to work these days!

cheers

[Liemaeu]

+1 for Linux

[Scheming Weasel]

+1 I need dis

[®omano]

It is very sad the devs have no consideration to help going forward in Linux gaming. There are little roadblocks only devs can lift, and then everything else will flow naturally and no more work would be needed from devs, no one is asking for devs to support Linux OS, what is only needed is the activation of the EAC support for Linux/Proton. After it is enabled that's all, the Linux support burden would be on Valve and the Linux community.

Seriously very sad and disappointed of the disdain we can perceive from devs regarding this simple request. This is a really minimal request, compared to the huge gain it would offer to Linux gaming community.

[Tyfuzzle]

Originally posted by ®omano:

It is very sad the devs have no consideration to help going forward in Linux gaming. There are little roadblocks only devs can lift, and then everything else will flow naturally and no more work would be needed from devs, no one is asking for devs to support Linux OS, what is only needed is the activation of the EAC support for Linux/Proton. After it is enabled that's all, the Linux support burden would be on Valve and the Linux community.

Seriously very sad and disappointed of the disdain we can perceive from devs regarding this simple request. This is a really minimal request, compared to the huge gain it would offer to Linux gaming community.

It's fatshark. They're nothing but disappointing. I'm expecting the same when Darktide comes around.

[[Fatshark] Hedge]

So we have looked in to this. It's far more complex than first suspected -- EAC has two versions. Non-EOS and EOS (Epic Online Services). Most games historically use Non-EOS EAC. It's the one Vermintide 2 uses as well. Epic only added Proton support for the EOS version of EAC. Therefor in order to implement proton support for Vermintide 2, a huge amount of reworking of the EAC implementation would be required, which may also require all players to authenticate with Epic Online Services as well -- perhaps even logging in to the Epic environment (to be confirmed, however).

So the "just a few clicks" statement made in the original announcement wasn't entirely accurate, and would only apply to titles using the EOS version of EAC, which simply hasn't been many games aside from either pretty new ones, and likely predominantly Epic exclusive titles.

We are still looking at what is or isn't going to be possible, but it's not as easy as it was made out to be -- far from it in fact.

There may be other solutions or workarounds, but ripping out the old EAC and rewriting everything to implement "NuEAC" and potentially asking our entire playerbase to connect through and sign through EOS for an honestly tiny market share that was (and would remain) unsupported from the get go might be a deal breaker.

Time will tell.

[Lamdarer]

Good to hear that you are on it, also a login to Epic Games is also probably something very few Linux users would want.
Hopefully it is possible to use it without that or any workaround, looking forward to it :)

[Grankotte]

Oh god. As much as i want to run this on Linux, no way in hell would i want to run using EPIC Online Services. I really hope we wont in Darktide.

[[Fatshark] Hedge]

Originally posted by Grankotte:

Oh god. As much as i want to run this on Linux, no way in hell would i want to run using EPIC Online Services.

It's the only way for this to work out. The only question we have yet to answer fully is what that would entail from an End User perspective (as in, would it require an additional log-in layer, or terms agreement).

The only certainty we have is that it would require all our players to make use of EOS.

[Tyfuzzle]

Originally posted by Fatshark Hedge:

So we have looked in to this. It's far more complex than first suspected -- EAC has two versions. Non-EOS and EOS (Epic Online Services). Most games historically use Non-EOS EAC. It's the one Vermintide 2 uses as well. Epic only added Proton support for the EOS version of EAC. Therefor in order to implement proton support for Vermintide 2, a huge amount of reworking of the EAC implementation would be required, which may also require all players to authenticate with Epic Online Services as well -- perhaps even logging in to the Epic environment (to be confirmed, however).

So the "just a few clicks" statement made in the original announcement wasn't entirely accurate, and would only apply to titles using the EOS version of EAC, which simply hasn't been many games aside from either pretty new ones, and likely predominantly Epic exclusive titles.

We are still looking at what is or isn't going to be possible, but it's not as easy as it was made out to be -- far from it in fact.

There may be other solutions or workarounds, but ripping out the old EAC and rewriting everything to implement "NuEAC" and potentially asking our entire playerbase to connect through and sign through EOS for an honestly tiny market share that was (and would remain) unsupported from the get go might be a deal breaker.

Time will tell.

Thanks for this update.

It seems the "just a few clicks" thing is only causing more damage than good then. There are lots of people buying steam decks banking on compatibility being pretty good and these anti-cheats are pretty much the largest blockers left. Lots of linux gamers were echoing this line wondering why it hasn't happened much. If this is a similar case to lots of other games out there using EAC, then it seems unlikely that (at least for older games,) EAC compatibility will be delivered on a wider scale.

[Moskeeto]

Originally posted by Fatshark Hedge:

So we have looked in to this. It's far more complex than first suspected -- EAC has two versions. Non-EOS and EOS (Epic Online Services). Most games historically use Non-EOS EAC. It's the one Vermintide 2 uses as well. Epic only added Proton support for the EOS version of EAC. Therefor in order to implement proton support for Vermintide 2, a huge amount of reworking of the EAC implementation would be required, which may also require all players to authenticate with Epic Online Services as well -- perhaps even logging in to the Epic environment (to be confirmed, however).

So the "just a few clicks" statement made in the original announcement wasn't entirely accurate, and would only apply to titles using the EOS version of EAC, which simply hasn't been many games aside from either pretty new ones, and likely predominantly Epic exclusive titles.

We are still looking at what is or isn't going to be possible, but it's not as easy as it was made out to be -- far from it in fact.

There may be other solutions or workarounds, but ripping out the old EAC and rewriting everything to implement "NuEAC" and potentially asking our entire playerbase to connect through and sign through EOS for an honestly tiny market share that was (and would remain) unsupported from the get go might be a deal breaker.

Time will tell.

Wow, that's really unfortunate. Is the non-EOS version still being updated otherwise or is it a legacy version?