Easyanticheat error failed to create igameclient

There are a few steam games that have non-functional or otherwise useless Linux ports, the ability to install the Windows version of a game that has a native Linux version would be incredibly useful.

@exezin

I agree completely with this.

Battleblock theater’s Linux port only works on Ubuntu 14.04.x, however the Linux version works 100% on wine.

Would be great if on the game properties there was a way to override the Linux version and use the windows one.

It’s free weekend but launching it with 4.2-9 fails with the fact it cannot find /squad_launcher.exe error since it didn’t download it. Checking files won’t help.

It fails using Native2Proton (also it still runs on 3.16 beta instead of 4.2-9)

[1] Use winetricks on prefix
[2] Install Non-Steam App [Experimental]
[3] Recreate config
[4] Quit
What would you like to do? 0
Please enter the Steam app ID: 393380
Got: Squad
Please enter your Steam username: xxx
Redirecting stderr to '/home/xxx/.steam/steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.
"@sSteamCmdForcePlatformType" = "windows"
Logging in user 'xxx' to Steam Public ...
Logged in OK
Waiting for user info...OK
 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Error! App '393380' state is 0x212 after update job.
Please select the game executable by number:```

Squad (sudden fps drops)

Issue transferred from #3071.
@aly199 posted on 2019-09-19T23:29:24:

Latest Proton (4.11-5) has Squad dropping fps, from 60-90fps, down to 15fps. It happens sort of every 20-30s, drops for about 5-10s, then gets back to normal, cycling like this through the entire game.
Reverting back to Proton 4.2-9, the issue disappears.

Proton 4.11-5
Linux Mint 19.1 (Tessa)
NVIDIA Driver 430.4
Kernel 4.15.0-55-generic

Hello @aly199, please add PROTON_LOG=1 %command% to the game’s launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

Counter point to the above, I put in a few hours in the game today on the latest Proton (4.11-5) and it runs flawlessly, multiplayer works perfectly as well and I had no issues with the anticheat (this used to play up with Proton)

I do use these launch commands, not sure if they’ll make a difference for @aly199

__GL_THREADED_OPTIMIZATIONS=1 PROTON_NO_ESYNC=1 gamemoderun %command%

@kisak-valve, I’ve played for some 5 minutes or so, and the generated log file is 1.8GB in size!
I mean, I’m willing to upload it through whatever means, but github accepts 10MB maximum.

Ouch, Proton logs compress well, but even in an archive there’s a good chance it’ll be larger than github is happy with.

Yep. 113MB was the best gzip could do.
I’ve uploaded the compressed file to pcloud.
Here’s the link.

Not that it helps with diagnosing the perf issue, but debugstr is very active with lines like
4460.245:0033:0034:warn:debugstr:OutputDebugStringA "[2019.09.20-22.02.28:146][ 0]LogPackageLocalizationCache: Warning: Skipping the cache update for the package asset groups due to a cache request from a non-game thread. Some localized packages may be missed for this query.rn"
4460.246:0033:0034:warn:debugstr:OutputDebugStringA "[2019.09.20-22.02.28:147][ 0]LogPackageLocalizationCache: Warning: Skipping the cache update for 3 pending package path(s) due to a cache request from a non-game thread. Some localized packages may be missed for this query.rn"

grep "Warning: Skipping the cache update" steam-393380.log | wc -l
90520

This along with the seh lines that fire off with it makes up the majority of the log.

Oh, I had to do some other stuff here, and forgot to mention: I’m running Steam on a firejail, with an overlay-fs. Don’t know if it has something to do with anything, but thought I should mention it.
It probably doesn’t matter, since the game ran on Proton 4.2-9 without any hiccups, under the same circunstances.

I’m unable to run Squad suddenly due to EAC. No one else is having this issue that I can see. Running on the latest Proton 4.11-7 on Ubuntu 19.10. When I launch the game, it tells me that EAC could not initialize a game client and subsequently, I could not join any online servers.

I’m unable to run Squad suddenly due to EAC. No one else is having this issue that I can see. Running on the latest Proton 4.11-7 on Ubuntu 19.10. When I launch the game, it tells me that EAC could not initialize a game client and subsequently, I could not join any online servers.

Working for me on 1570630972 proton-4.11-7, using Ubuntu 18.04.
There was a Steam outage yesterday, maybe it was related? https://twitter.com/SteamStatus/status/1188893289409400832

I’m unable to run Squad suddenly due to EAC. No one else is having this issue that I can see. Running on the latest Proton 4.11-7 on Ubuntu 19.10. When I launch the game, it tells me that EAC could not initialize a game client and subsequently, I could not join any online servers.

Working for me on 1570630972 proton-4.11-7, using Ubuntu 18.04.
There was a Steam outage yesterday, maybe it was related? https://twitter.com/SteamStatus/status/1188893289409400832

Still not working. It worked before I reinstalled Ubuntu on this new disk (but with no other hardware changes) and I know others still have it working. I’m tempted to spin up the debugging and see what’s wrong.

Wanted to play again since the last time two weeks ago. Same problem. Game runs fine but shows a little popup with: EasyAntiCheat Error: Failed to create IGameClient instance!

The game has not updated in these two weeks and as far as I can see only proton updated in that time (I saw it shortly in my download list downloading 4.11 (or an update for it?)). Anyway, its practically borked now, cause without EAC you can not play on any of the public servers.

Update: I nearly forgot to mention, that I ran WINEPREFIX=~/SteamLibrary/steamapps/compatdata/393380/pfx/ ./EasyAntiCheat_Setup.exe which surprisingly worked and I could select «repair». Though sadly without any success.

Fresh install by Steam (without Proton) still with the empty repo.

With Proton 4.11-9 it works perfectly fine after deleting the Movies folder (Proton does not have the needed codec), except for the Easy Anti Cheat/EAC which intermitently stopped working since Alpha 16 was launched.

EasyAntiCheat Error: Failed to create IGameClient instance!

Current version is 17.

Hello guys.
I’m playing >20 hours online with zero configuration. I’m kinda lucky.

Current version: Beta v18.0.5
Proton: 4.11-11
Distro: Linux Mint 19.2 Tina
Kernel: 5.3.0-24-generic
RAM: 16 GB
GPU Driver: NVIDIA 440.44
GPU: NVIDIA GeForce GTX 1070
CPU: Intel Core i7-6700K @ 4.00GHz

This game is still laggy however.

Beta v18.0.5 has EAC working back, finally. But you have to run it multiple times until it does not show the EAC error.

I can sadly not confirm @BRMateus2’s results. I verified my game data, deleted the prefix to have a fresh start and I still get the EAC GameClient error even after starting it 10 times in a row. I’m open to suggestions for what else I could try…

Current version: Beta v18.0.5
Proton: 4.11-11
Distro: Manjaro Linux x86_64
Kernel: 5.4.6-2-MANJARO
RAM: 16 GB
GPU Driver: X.Org Radeon RX Vega (VEGA10, DRM 3.35.0, 5.4.6-2-MANJARO, LLVM 9.0.0)
Driver Version: 4.5 (Compatibility Profile) Mesa 19.3.1
GPU: AMD ATI Radeon RX Vega 64
CPU: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz

@Byter09 What DE are you using? lxde on arch gave me a startup error but switching to lightdm got rid of the startup error.

@greymood09 I’m using KDE. Does something like this really have that much impact? Wow.

This comment has been minimized.

This comment has been minimized.

And I just re added the easyanticheat file from repo and all good.

I reinstalled, then followed the steps and it worked for me. Had to WIPE it off fully however.

3060ti here, terrible performance at very conservative settings. ~30 FPS on latest 510 drivers

Tried reinstalling the thing from scratch as suggested, but as usual with a 1660ti I get the first round with decent fps and the second grinds to 3 fps. I’ve noticed a huge FPS degradation even when just loading maps with USMC forces in it

I think the only thing we can do is wait for the developers. They don’t seem to care however.

Aaand EAC is broken again…

Aaand EAC is broken again…

Sure is. I noticed that Squad now has a new EAC installer, the filename reveals they’ve updated to the EOS version of EAC.

Getting EAC errors in game

[EOS] Reason: Null Client | Details: Antcheat client protection not active (NullClient)

And:

[EOS] Reason: Authentication Faiiled | Details: Authentication timed out (1/2)

• Current Valve EAC fix doesn’t work
• Validating game files doesn’t work
• Reinstalling and putting Valve EAC fix in the new EAC folder (EasyAntiCheat/55c7dc1d520f4cba8ff261b85059f963/5dee4062a90b42cd98fcad618b6636c2/)
• Proton version nor GE doesn’t seem to make a difference

Loader log looks like:

[2022.11.10-17.12.35] Loader initializing with bootstrapper version 1.3.1.
[2022.11.10-17.12.35] Loader initialized.
[2022.11.10-17.12.35] [Connection] Connecting to URL: https://modules-cdn.eac-prod.on.epicgames.com/modules/55c7dc1d520f4cba8ff261b85059f963/5dee4062a90b42cd98fcad618b6636c2/linux32_64
[2022.11.10-17.12.35] Download Progress: 0    <repeats loads>
[2022.11.10-17.12.36] Download Progress: 0
[2022.11.10-17.12.36] [Connection] Connect result: No error (0) Response Code: 403 Destination IP: 13.227.219.27
[2022.11.10-17.12.36] HTTP Response Code: 403 Curl Code: 403
[2022.11.10-17.12.36] [EAC Callback] Code: 506. Message: 'HTTP Response Code: 403 Curl Code: 403'.

Please help.

I am having the same issue as well.

It seems to be fixed now. I deleted the EasyAntiCheat directory located in SteamLibrary/steamapps/compatdata/393380/pfx/drive_c/users/steamuser/Application Data and started the game again. It downloaded the correct EAC version and I was able to play. Probably a permission issue on the EAC server side that got corrected.

Confirm @FaulTTY solution.

I am guessing that the previous workaround of limiting read-write permissions to the EAC directory needs to be undone to get it to work. It seems to work now.

Confirm @FaulTTY solution.

I am guessing that the previous workaround of limiting read-write permissions to the EAC directory needs to be undone to get it to work. It seems to work now.

AFAIK only GE-Proton7 has the Squad protonfix that downloads an EAC blob and modifies directory permissions. Which version did you test with?

Confirm @FaulTTY solution.
I am guessing that the previous workaround of limiting read-write permissions to the EAC directory needs to be undone to get it to work. It seems to work now.

AFAIK only GE-Proton7 has the Squad protonfix that downloads an EAC blob and modifies directory permissions. Which version did you test with?

So now it works if you use proton experimental when launching it after you reinstall it. No idea how but I was able to play for 3 hours last night without getting kicked.

You’re right, I thought I was using Experimental, but I have been using GE-Proton7-41, which sets the directory permissions as follows:

dr-xr-xr-x    - user 12 Nov 09:36  55
drwxr-xr-x    - user 12 Nov 09:36  55c7dc1d520f4cba8ff261b85059f963
.rw-r--r-- 260k user 12 Nov 09:36  anticheatlauncher.log
drwxr-xr-x    - user 12 Nov 09:36  GameLauncher

I bought a new GPU recently so I thought I’d give Squad another try.

Anyway I got an RX 6600 (8GB). Now my game freezes after the initial loading screen. I can’t close it and it keeps producing the audio of what sounds like a beach???

Alt tab, go to terminal, type in top, wait for the squad process, ctrl + c
out of top and type kill (insert pid number) to kill the squad game and
then reattempt launching.

…

Reinstalled, now getting nulldevice anticheat warnings when joining. Tried a vew versions of ProtonGE and Proton to no avail. Have both dirs (55 and Temp) as readonly only after first trying to join, seeing the error, then adding the new EAC files and then setting dirs to read only.

Is it borked now? Can anyone else confirm. Seems like an update just pushed recently.

Reinstalled, now getting nulldevice anticheat warnings when joining. Tried a vew versions of ProtonGE and Proton to no avail. Have both dirs (55 and Temp) as readonly only after first trying to join, seeing the error, then adding the new EAC files and then setting dirs to read only.

Is it borked now? Can anyone else confirm. Seems like an update just pushed recently.

As far as I know (not sure tough) you have to undo all the aec file permission stuff. Like a fresh install. I’ve read it’s not necessary anymore.

So with the Chinese update it’s now platinum. Meaning that if you use
proton experimental there is no need to transfer files over. It works
straight out of the box. My best recommendation is to uninstall and
reinstall the game and boot it up using proton ge experimental.

…

Thank you both, saw the notification hit my phone and have it reinstalling now. God I need to get 10gbe in here! Will report back. Thank you again, been a few months since i’ve been able to play so had some dust collecting should have checked gh first.

Running experimental im seeing

Fossilize INFO: Overriding serialization path: "/mnt/9e402c0d-92c9-44c1-b17e-c3099ed10f03/SteamLibrary/steamapps/shadercache/393380/fozpipelinesv6/steamapprun_pipeline_cache".
warn:  DXVK: No state cache file found
info:  DXVK: Graphics pipeline libraries not supported
info:  D3D9DeviceEx::ResetSwapChain:
info:    Requested Presentation Parameters
info:      - Width:              1
info:      - Height:             1
info:      - Format:             D3D9Format::Unknown
info:      - Auto Depth Stencil: false
info:                  ^ Format: D3D9Format::Unknown
info:      - Windowed:           true
info:  Presenter: Actual swap chain properties:
info:    Format:       VK_FORMAT_B8G8R8A8_UNORM
info:    Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR
info:    Buffer size:  1x1
info:    Image count:  3
info:    Exclusive FS: 0
XIO:  fatal IO error 25 (Inappropriate ioctl for device) on X server ":1"
      after 229 requests (229 known processed) with 1 events remaining.
pid 635247 != 635246, skipping destruction (fork without exec?)

I’ve not seen this error before, I assume related to DXVK, but have not made changes there (this was after fresh install and using experimental. Im on Manjaro. Using a 3090. Im on the 470x drivers.

Ah. I personally run mint with an AMD 6600XT. Could be a driver issue?

…

Went down a rabbit hole. My issues were IBT related (im on an 11th gen intel), so I ripped out Manjaro and went Arch. Setup the new drivers with new kernel, just finished installing squad, removed some amdvlk packages and it is working agian (with just installing).

My issue has not been resolved.

Yesterday I played Squad public testing (774941), and everything was fine, no EAC issues, and it was using VKD3D, so DX12. FSR also worked(Tho, I did not observe any performance benefit)

I just did a fresh install and as others have reported, everything just worked like on Windows.

But is there a way to get an performance overlay? Mangohud does not work for me, but it works fine with other games.

Squad won’t launch, it seems to get stuck in a loop at the logo screen.

Pop!_OS 22.04 LTS x86_64
Kernel: 6.0.12-76060006-generic
CPU: AMD Ryzen 5 5600X (12) @ 3.700GH
GPU: NVIDIA GeForce RTX 3060

Tried a bit of everything, reinstalling steam and game, deleting compat data, different GPU drivers, different versions of proton. All have the same issue. This same set of hardware worked a week ago when I was just using ubuntu.

I’m interested in troubleshooting myself, but am not sure where to go from here. Any advice or things to investigate would be greatly appreciated. If someone tells me which logs (and where they are) to post, I’ll do so.

Yeah it’s a bug. I just type top in the terminal. Look for the squad
game.exe and the pid number and then kill it. Relaunch squad and it works.
Sometimes 2 times other times it’s 4.

…

Somehow the FPS drop to single digit after a map change seems to have disappeared as I have tried in a single session to change maps and servers and had no degradation. Despite everything though, with my GTX1660Ti, I had to turn all settings to minimum in order to play without stuttering compared to several updates ago where I could play with medium/highish settings at decent fps rate, but my guess is that I would have the same issue under Windows. It works on most maps except the ones that came out with USMC which seem to always lag as soon as I enter the server

Replying to #938 (comment)

In reference to my earlier post, I seem to have much better luck getting Squad to launch right after a reboot. Hopefully this means something to someone else

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку