[SOLVED] Client integrity violation (impossible to join a server)

[WarMask]

Hello,

I have a little issue starting the game.

I did check files integrity on Steam.

I went in the folder of the game and installed the EasyAntiCheat thingy.

In EAC setup, I get three options, the "current game" option is named "Game 55"

I've installed it. And I also used the repair service. Installtion succesful.

Back to the game. I launch a server, and I load, then see a few images of the server, then back to menu. And this nice message about client integrity violation.

it's a fresh installation. Any help would be appreciated.

[Serano E'Stabant]

Check the game log files, may be there you will have a detailed information exactly what file it thinks is "wrong".

C:\Users\<<USERNAME>>\AppData\Local\SquadGame\Saved

[WarMask]

Thanks for the idea.

I backedup my old log and started the game to make a new one (old one had like 6MB of data).

I received a 900kb log after starting the game, connecting to a server, looking at the team selection page, then back to menu. Then exiting the game.

I've searched the log for the term "error". Here is what I've found:

First mention:
[2023.02.26-19.37.54:845][ 0]LogInit: FAudioDevice initialized.
[2023.02.26-19.37.54:872][ 0]LogAudio: Error: Submix buffer listener only works with the audio mixer. Please run with audio mixer enabled.
[2023.02.26-19.37.54:872][ 0]LogAudio: Error: Submix buffer listener only works with the audio mixer. Please run with audio mixer enabled.
[2023.02.26-19.37.54:874][ 0]LogNetVersion: Set ProjectVersion to V4.2.1.113377.353. Version Checksum will be recalculated on next use.

I think it's a sound device issue. But sound works fine. I don't think it's the problem I'm having.

Second mention: (and the problem I believe)
----
[2023.02.26-19.37.58:503][ 1]LogEOS: Error: [Category: LogEOSAntiCheat] [AntiCheatClient] Client Violation with Type: 2 Message: Corrupt Easy Anti-Cheat Hash Catalogue
[2023.02.26-19.37.58:503][ 1]LogEOS: Warning: Violation Detected: Integrity Catalog Error | Log: Corrupt Easy Anti-Cheat Hash Catalogue
[2023.02.26-19.37.58:503][ 1]LogSquadTrace: [Standalone] USQGameInstance::ShowLoadingScreen(): LoadingScreenModule:
[2023.02.26-19.37.58:503][ 1]LogStreaming: Display: FlushAsyncLoading: 1 QueuedPackages, 385 AsyncPackages
[2023.02.26-19.37.58:540][ 1]LogSquadTrace: [Standalone] USQGameInstance::ShowLoadingScreen(): SquadViewport:
[2023.02.26-19.37.58:540][ 1]LogNet: Browse: /Game/Maps/EntryMap
----

Anti Cheat is trolling me.

[Serano E'Stabant]

Are you running anything else than Win 10 by any chance?

Lets ignore the sound error for now:

Upload the full log to PasteBin, also find the EAC log and upload that too.
Not just the errors, but the full log.

Also try running the game as an Administrator, some people reported that this solved some problems, although it should run fine without elevated privileges.

[WarMask]

Originally posted by Serano E'Stabant:

Are you running anything else than Win 10 by any chance?

No, nothing special on my PC. I have many other games on my PC and some use EAC like War Thunder. Only this one is acting up.

So, here's what I did. I deleted the game and download it anew.

And now, it's working fine.

I don't think I've done anything else. Just fresh download after deleting all the SQUAD folder in the Steam Library (commonapps). The game I had was an updated version of the game. Meaning I left the computer off for a long time and it had to update it to the lastest version to play.

And checking the files from Steam isn't reliable apparently.

[Serano E'Stabant]

I guess something got screwed up with the cfg files or EAC itself.

You could have probably saved lots of time and SSD wear but it is too late now...

Don't forget to set the topic's header as "SOLVED"

[WarMask]

Originally posted by Serano E'Stabant:

I guess something got screwed up with the cfg files or EAC itself.

You could have probably saved lots of time and SSD wear but it is too late now...

Don't forget to set the topic's header as "SOLVED"

I'm just discovering this SSD wear phenomenon. Interesting.

And I only have a single SSD on my computer. I might have to change that.

Thank you for you support.