+1 for support on this game. As far as I know it's only a matter of the EAC (Easy Anti Cheat)-System not working correctly through wine/proton.

tried the "trick" that worked with Squad (https://github.com/ValveSoftware/Proton/issues/938#issuecomment-655405271) - but no luck - game refuses to start when I set C:\\users\\steamuser\\Temp to read only (that helped with SQAD) and if I don't do it I get the same "Cannot create game client" EAC message. But I don't really know what exactly it does so maybe it can be adapted for HLL by someone smarter - like @imaami (original poster on squad issue)

for me, what I got is a test screen picture of like a TV thing and then followed up by an error message from Easy Anti Cheat "EasyAntiCheat Error: Failed to create IGameClient instance! Check that the game was run from the correct launcher. Online Play may not be available." but if you click OK, the game will launch normally. The performance is ok but can't play online. You can join servers and play but you will get kicked after a short time. Saying that "Anti-Cheat Authentication timed out (1/2)".

Same issue as @blyatmcnugget Is there any fix yet?
Error from EAC logs:
[2021.10.19-21.19.14] [Connection] Connect result: No error (0) Response Code: 200 Destination IP: 65.9.53.11 [2021.10.19-21.19.14] [HTTP Error Response] HTTP Response Code: 200 Curl Code: 0. [2021.10.19-21.19.14] Falling back to a secondary CDN path. [2021.10.19-21.19.14] [Connection] Connecting to URL: https://download-alt.easyanticheat.net/api/v1/games/167/client/wine64/download/?uuid={uuid} [2021.10.19-21.19.14] Download Progress: 0%. [2021.10.19-21.19.14] Download Progress: 0%. [2021.10.19-21.19.14] Download Progress: 0%. [2021.10.19-21.19.14] Download Progress: 0%. [2021.10.19-21.19.14] [Connection] Connect result: Couldn't resolve host name (6) Response Code: 0 Destination IP: Unavailable [2021.10.19-21.19.14] DNS resolve to the Content Distribution Network failed! [2021.10.19-21.19.14] [EAC Callback] Code 896. Message: 'DNS resolve to the Content Distribution Network failed!'.

And it seems that EAC URL just downloads the 0 byte file, since response code is 200

Hell Let Loose/EasyAntiCheat/easyanticheat_x64.so is provided in the game files now.

Unfortunately I'm unable to get past (buggy looking components of) the EAC launcher at what I think is 100%.

Attached proton log.
steam-686810.log

Edit: HLL dev posted on reddit that a game engine upgrade is required for them to move forward with allowing the game to launch on Linux.
https://www.reddit.com/r/HellLetLoose/comments/tevxzz/linux_support_not_enabled/i0ux2ks/?utm_source=reddit&utm_medium=web2x&context=3

I've submitted my request for them to support launching on linux using the form at https://support.team17.com/hc/en-gb/requests/new

I've been hitting them on twitter to open up for Linux PLEASE! Do the same the more they know we are interested the better.

Since update 12 I can now launch the game and connect to servers, servers kick me soon after for anticheat reasons.

I've been hitting them on twitter to open up for Linux PLEASE! Do the same the more they know we are interested the better.

A developer has said on reddit that the best course of action is to actually make Tickets to Team17 to show that there are people who are interested. Twitter won't do anything sadly.

Since update 12 I can now launch the game and connect to servers, servers kick me soon after for anticheat reasons.

Can also confirm. Game starts just fine, and I can play for like 15 seconds after connecting to server, but then EAC kicks me out.

Got this EAC message at the start:

Then, a few seconds into a session, I get kicked off because of anti cheat.

FIX: install Valve's Proton EasyAnticheat:

In case anybody else is struggling to find ProtonEasyAntiCheat you need to also enable "Tools" when searching.

After upgrading to Ubuntu 24.04 LTS Vivox does not work. Is anybody else experiencing this issue? I can see in Helvum that vivox is creating some devices but input or output does not get routed to the audio interface's output.

@kisak-valve Wanted to come back to this. Installed Ubuntu Desktop 24.04 and everything is working fine with no tweaks. What's interesting is on first install with Linux Mint 21.3 from above report, it worked fine for the first day, but later developed that issue.

@Dzuelu can you please double check for me if on Ubuntu 24.04 vivox works? i.e. please join a game and make sure you can hear unit voice chat or command chat.

@joobei Can confirm, all voice chat worked fine for me. I'm using a Logitech G533 Wireless headset and didn't have to configure anything for it to work if that helps too.

@kisak-valve Having the exact same sieeu/error with a GTX 1060 on Linux Mint. Any updates on this problem?

After recent update, after around a minute spawning in game I'm crashing with no message when running through the steam play button. Build ID: 15016075. Running on Linux mint now, tried with Proton 9.0-2 and Proton experimental. I'll try to see if I can get any info running through cli.

Crashed at (process:51685): GLib-GObject-CRITICAL **: 21:43:24.303: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

Setting breakpad minidump AppID = 686810
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561198025935611 [API loaded no]
Adding process 51508 for gameID 686810
Adding process 51526 for gameID 686810
Adding process 51547 for gameID 686810
Fossilize INFO: Overriding serialization path: "/home/kenny/.steam/debian-installation/steamapps/shadercache/686810/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/home/kenny/.steam/debian-installation/steamapps/shadercache/686810/fozpipelinesv6/steamapprun_pipeline_cache".
GameOverlay: started '/home/kenny/.steam/debian-installation/ubuntu12_32/gameoverlayui' (pid 51685) for game process 51547
08/03 21:41:14 minidumps folder is set to /tmp/dumps
08/03 21:41:14 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20240716232148)/tid(51685)
08/03 21:41:14 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(51685)

(wine:51547): GStreamer-Video-CRITICAL **: 21:41:15.411: gst_video_info_from_caps: assertion 'gst_caps_is_fixed (caps)' failed
reaping pid: 50823 -- gameoverlayui
Adding process 51794 for gameID 686810
Adding process 51797 for gameID 686810

(wine:51547): GStreamer-Video-CRITICAL **: 21:41:19.053: gst_video_info_from_caps: assertion 'gst_caps_is_fixed (caps)' failed
08/03 21:41:54 minidumps folder is set to /tmp/dumps

(process:51685): GLib-GObject-CRITICAL **: 21:43:24.303: g_object_unref: assertion 'G_IS_OBJECT (object)' failed <-------- CRASHED HERE
pid 51459 != 51458, skipping destruction (fork without exec?)
Game 686810 created interface STEAMAPPS_INTERFACE_VERSION008 / 
Game 686810 created interface STEAMREMOTESTORAGE_INTERFACE_VERSION014 / 
Game 686810 created interface STEAMUSERSTATS_INTERFACE_VERSION011 / 
Game 686810 created interface SteamController007 / Controller
Game 686810 created interface SteamFriends017 / 
Game 686810 created interface SteamInput001 / Controller
Game 686810 created interface SteamMatchMaking009 / 
Game 686810 created interface SteamMatchMakingServers002 / 
Game 686810 created interface SteamNetworking006 / 
Game 686810 created interface SteamUser020 / 
Game 686810 created interface SteamUser020 / User
Game 686810 created interface SteamUtils009 / 
Game 686810 created interface SteamUtils009 / Utils
Game 686810 method call count for IClientConfigStore::GetString : 7
Game 686810 method call count for IClientConfigStore::GetInt : 7
Game 686810 method call count for IClientNetworking::AllowP2PPacketRelay : 1
Game 686810 method call count for IClientUserStats::GetUserStat : 3205
Game 686810 method call count for IClientUserStats::RequestUserStats : 4
Game 686810 method call count for IClientUserStats::GetAchievementDisplayAttribute : 531
Game 686810 method call count for IClientUserStats::GetAchievement : 177
Game 686810 method call count for IClientUserStats::RequestCurrentStats : 1
Game 686810 method call count for IClientAppManager::GetCurrentLanguage : 1
Game 686810 method call count for IClientAppManager::IsAppDlcInstalled : 2959
Game 686810 method call count for IClientMatchmaking::ReleaseGMSQuery : 7
Game 686810 method call count for IClientMatchmaking::GetGMSQueryResults : 7
Game 686810 method call count for IClientMatchmaking::PollGMSQuery : 82
Game 686810 method call count for IClientMatchmaking::BeginGMSQuery : 7
Game 686810 method call count for IClientMatchmaking::AddFavoriteGame : 1
Game 686810 method call count for IClientMatchmaking::GetFavoriteGame : 8439
Game 686810 method call count for IClientMatchmaking::GetFavoriteGameCount : 413
Game 686810 method call count for IClientUtils::RecordSteamInterfaceCreation : 14
Game 686810 method call count for IClientUtils::GetAPICallResult : 4
Game 686810 method call count for IClientUtils::IsAPICallCompleted : 44
Game 686810 method call count for IClientUtils::GetAppID : 454
Game 686810 method call count for IClientFriends::GetFriendRichPresenceKeyByIndex : 77
Game 686810 method call count for IClientFriends::GetFriendRichPresenceKeyCount : 102
Game 686810 method call count for IClientFriends::GetFriendRichPresence : 77
Game 686810 method call count for IClientFriends::ClearRichPresence : 21
Game 686810 method call count for IClientFriends::SetRichPresence : 108
Game 686810 method call count for IClientFriends::SetPlayedWith : 5
Game 686810 method call count for IClientFriends::RequestUserInformation : 4
Game 686810 method call count for IClientFriends::GetFriendGamePlayed : 25
Game 686810 method call count for IClientFriends::GetFriendPersonaState : 25
Game 686810 method call count for IClientFriends::GetFriendRelationship : 46
Game 686810 method call count for IClientFriends::GetPersonaName : 10
Game 686810 method call count for IClientUser::BIsSubscribedApp : 1
Game 686810 method call count for IClientUser::AdvertiseGame : 1
Game 686810 method call count for IClientUser::GetAuthSessionTicket : 2
Game 686810 method call count for IClientUser::GetSteamID : 114
Game 686810 method call count for IClientUser::BLoggedOn : 6
Uploaded AppInterfaceStats to Steam
Removing process 51797 for gameID 686810
Removing process 51794 for gameID 686810
Removing process 51547 for gameID 686810
Removing process 51526 for gameID 686810
Removing process 51508 for gameID 686810
Removing process 51495 for gameID 686810
Removing process 51488 for gameID 686810
Removing process 51476 for gameID 686810
Removing process 51466 for gameID 686810
Removing process 51463 for gameID 686810
Removing process 51461 for gameID 686810
Removing process 51458 for gameID 686810
Removing process 51457 for gameID 686810
Removing process 51454 for gameID 686810
Removing process 51453 for gameID 686810
Removing process 51357 for gameID 686810
Removing process 51356 for gameID 686810
Removing process 51355 for gameID 686810
Removing process 51354 for gameID 686810
reaping pid: 51685 -- gameoverlayui

Edit: Sorry, nvm. Looks like it was a DX11 issue with proton and using the protondb -dx12 fixed the crashing issue.

Game runs great for me, but none of the in-game voice chat channels work. I can't hear audio, and nobody in-game can hear me.

Using CachyOS (arch-based) with the latest drivers and pipewire with a standard USB DAC. Other games do not have this issue for me, so I believe it to be a game-specific bug.

Change the audio settings. Once launched in a game go to options > audio > check then add your input and output devices.

This worked for me with the same issue.

On Thu, Aug 29, 2024 at 1:51 AM, Daktyl @.***(mailto:On Thu, Aug 29, 2024 at 1:51 AM, Daktyl < wrote:

Game runs great for me, but none of the in-game voice chat channels work. I can't hear audio, and nobody in-game can hear me.

Using CachyOS (arch-based) with the latest drivers and pipewire with a standard USB DAC. Other games do not have this issue for me, so I believe it to be a game-specific bug.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Re: Audio Settings
In my case none of the devices listed in hell let loose audio settings worked on Ubuntu 24.04 LTS (Noble Numbat), Noble Numbat broke Vivox for me. Vivox worked fine on Ubuntu 22.04.4 LTS (Jammy Jellyfish).

Change the audio settings. Once launched in a game go to options > audio > check then add your input and output devices. This worked for me with the same issue.

Can confirm that this does NOT work for me. I've tried setting output to both of my available outputs with no change, and I also changed to the only input with again no results.

UPDATE (21 OCT 2024) - This has now been resolved.

Compatibility Report

• Hell Let Loose
• 686810

System Information

• GPU: 6800XT
• Video driver version: Mesa 24.2.4-arch1.1
• Kernel version: Linux 6.11.3-arch1-1
• Link to full system information report as Gist
• Proton version: GE 9-16 (also tried Experimental Bleeding Edge)

I confirm:

• [X] that I haven't found an existing compatibility report for this game.
• [X] that I have checked whether there are updates for my system available.

PROTON LOG ATTACHED

steam-686810.log

Symptoms

NEW EAC Compatibility Issue

Hell Let Loose had a game update, October 17th, 2024. Linux/Steamdeck users are no longer able to play (access servers) after the update, and get an in-game "AUTHENTICATION TIMED OUT 1/2" & "ANTI-CHEAT CLIENT PROTECTION NOT ACTIVE (NullClient)" errors upon attempting to load into a server in-game (immediately or within 10-15 seconds).

Reproduction

See above.

Same problem as @maximvh2 mentioned. After newest Hell Let Loose update not playable anymore.

I guess the wine64 binary flavors are not distributed to the cdn's, because not 'enabled' for the builds.

The EAC compatibility issue seems to have been resolved as of today. Everything appears to be working normally again.

The EAC compatibility issue seems to have been resolved as of today. Everything appears to be working normally again.

Can confirm it works perfectly again.

Hi fellas, I regret to inform you that the since the update number 16 from today, they broke it again. Although this time it does not seem to have anything to do with EAC as far as I can tell. I just get a "Fatal Error" messagebox. Proton Logs are not conclusive either. Does anyone else have that problem or is it just me?

EDIT: Issues seems to be with Proton version >=9. Proton 8.0-5 works without issues.

Hi fellas, I regret to inform you that the since the update number 16 from today, they broke it again. Although this time it does not seem to have anything to do with EAC as far as I can tell. I just get a "Fatal Error" messagebox. Proton Logs are not conclusive either. Does anyone else have that problem or is it just me?

EDIT: Issues seems to be with Proton version >=9. Proton 8.0-5 works without issues.

Also the error popped up for me, I just ignored it and still loaded in and am playing

Edit: I have a mini-heart attack every time a report for HLL comes in. One of my favorite games on Linux.

Edit:: Yes game crashed after I ignored, and can confirm Proton 8.0-5 works.

Replying to https://github.com/ValveSoftware/Proton/issues/2901#issuecomment-2504136039

Yeah same thing for me. Regarding the ignoring thing. I noticed that as well, but after a few minutes the game crashed anyways. But as mentioned using Proton 8.0-5 works for whatever reason.

@DaniloMurer @bitbucket90 In addition to what Kisak mentioned above, I have a few questions to help us figure out this issue. Would you be able to share where the crash is happening? Does it happen on the main menu? Do you have to be in a match? How long does it take to crash?

Here's my PROTON_LOG for when the game crashed.
steam-686810.log
steam-runtime-system-information.txt

The crash happened once I loaded into a server and selected to join a squad but I've had it happen while joining a server as well I think.
This crash log is with Proton Experimental Build ID 16489034.

I can attach logs later, but it's within the first few seconds of entering the in-game server browser.

They added a new UI element that shows your position in a server queue while attempting to join a server, allowing players to browse the menus while waiting for a queue. I think it's an issue with GL overlay rendering and that new feature.

It isn't EAC, since you can use Steam's built in server browser to join a server without issue.

I played all yesterday no issues. I saw there was an update today, and can also confirm that clicking enlist for the in-game server browser crashes it.

Steams server browser works fine. It also loads way faster than the in-game browser too.

This should work once again with the just updated Proton Experimental Bleeding Edge (https://github.com/ValveSoftware/Proton/wiki/Proton-Versions).

Hi I've news. I've tested the bleeding edge branch of proton and while the issue doesn't occur anymore right when enlisting, after joining in the splashscreen of the map the game crashes with a UE4 crash report. I couldn't copy the next nor screenshot it in time. But it said something about an error getting pixels of sorts. However I wanted to mention that T17 is also aware of this issue (the one which I reported originally) and they're looking into it as well.

Hi I've news. I've tested the bleeding edge branch of proton and while the issue doesn't occur anymore right when enlisting, after joining in the splashscreen of the map the game crashes with a UE4 crash report. I couldn't copy the next nor screenshot it in time. But it said something about an error getting pixels of sorts. However I wanted to mention that T17 is also aware of this issue (the one which I reported originally) and they're looking into it as well.

Original issue is fixed in Proton and unlikely related to this next one. For this one, could you please do the following if possible to give us a chance to guess what's going on there:

• attach compressed Proton log (reproduce with launch options "PROTON_LOG=1 %command%" without quotes, compress and attach ~/steam-686810.log);
• describe exact reproduction steps;
• list basic system info, like in the 'System Information' in the original issue report.

Here's updated details, this time again with proton experimental but without the -dx12 argument.
There doesn't seem to be any particular reproduction steps for the crash, the game seems to just crash after a short time.
In this instance, I was just in the server menu scrolling through servers when the game crashed.

steam-686810.log
Steam Runtime System Information
System Information

Edit: I've been playing for a little while without crashing after joining a server via the steam browser so perhaps the issue is related to the in-game server browser.

experimental-9.0-20241121b

you are not using Experimental [bleeding-edge]

On Sat 30 Nov 2024 at 10:38 Chris Lane @.***> wrote:

Here's updated details, this time again with proton experimental but
without the -dx12 argument.
There doesn't seem to be any particular reproduction steps for the crash,
the game seems to just crash after a short time.
In this instance, I was just in the server menu scrolling through servers
when the game crashed.

steam-686810.log
https://gist.github.com/ChrisLane/a245e57b2459816703b9c40b1800e1f6
Steam Runtime System Information
https://gist.github.com/ChrisLane/4b56c44d056dce4a2185bb9bd7e1b4d8
System Information
https://gist.github.com/ChrisLane/1d13f871ea63317cdebecdd43e59d4c8

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2901#issuecomment-2509029919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4WL3O67MPF5V3DNEM4PSL2DHSYXAVCNFSM4IFY3HZ2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENJQHEYDEOJZGE4Q
.
You are receiving this because you commented.Message ID:
@.***>

steam-686810.log
SteamRuntimeDiag.txt
SystemInformation.txt
SystemReport.txt

Running proton experimental, I get the small ~unreal engine~ fatal error dialog window, was able to join a server and spawn ignoring the error but then crashes in under a minute.

Screenshot of fatal error dialog window

EDIT: Apologies for the duplicate report, running experimental w/ bleeding-edge does not crash!

Game crashes when entering server browser, tried proton 8.0.5 (which used to work earlier but not anymore), 9.0.5 and experimental....

steam-686810.log

Compatibility Report

Name of the game with compatibility issues: Hell Let Loose
Steam AppID of the game: 686810

System Information

GPU: RTX 3080
Video driver version: 570.153.02-3
Kernel version: 6.15.0-2
Proton version: Ge-Proton, same happens on experimental
Link to full system information report as https://gist.github.com/pollux78/1a26508732fd4df74850212b6f7f901c

Log

bOdX3sM7e.log

Symptoms

Hard crash on startup after intro movies

EDIT: solved, mesa update solved the issue as the amd igpu was active