Compatibility Report

Looks like EAC is also in this one. Also of potential interest is winhttp, which may be referenced from HttpClient for Xbox Live support (similar to Halo MCC).

I do also see x3daudio/xapofx, but it doesn’t get far enough to create an XAudio2 object, so I can’t tell if they use stock UE4 audio or a middleware.

It also doesnt launch for me. I see a EAC pop up for a second and then the game closes. I've attached log files from my attempt at running it.
steam-1097840.log

Something that may be of interested once the bcrypt issue is resolved: Word on the street is the game requires D3D12 even on Windows 7? I'm not sure how or why but they appear to depend on the new D3D12on7 runtime that recently went out. The engine still appears to load d3d11 but I'm seeing lots of Windows reports about it :/

I get the bcrypt.dll.BCryptSignHash error with vanilla Wine too.

Same bcrypt.dll errors here :(

BCryptSignHash has been implemented in upstream:

https://github.com/wine-mirror/wine/commit/b2bbb6f48f24ada876f952e9c0921ca584fe307d
https://github.com/wine-mirror/wine/commit/98b230f851f859e9240e8381e3deec5016082ceb

Be warned though: The EAC launcher behavior for this particular game appears to be to restart the program, so while you won't hit a stub anymore, you will instead get an infinite boot loop on the EAC launcher. You can test this if you really want to, but have killall -9 Gears5.exe ready if you do that.

Tried to run Gears 5 without EAC and it's shows few seconds of xbox game studios intro

• Lutris
• Proton-4.21-GE-1 with disabled DXVK
• Rename EasyAntiCheat folder to anything in %gamefolder%/GearGame/Binaries/Steam
• Run Gears5.exe

Something crashes the game, if run with WINEDEBUG=relay, I can watch full xbox game studios intro.

I think this is an EAC or anti-debug check, but maybe not

There’s a very good chance that the bcrypt work for #2907 will be related to this game as well.

I attempted to run Gears 5 using the MCC patch for issue #2907 because it involves bcrypt. After pressing launch it pops up a small windows that says "File not found" and then exits the game. I've attached the steam log.

steam-1097840.log

Tried to run Gears 5 without EAC and it's shows few seconds of xbox game studios intro

• Lutris
• Proton-4.21-GE-1 with disabled DXVK
• Rename EasyAntiCheat folder to anything in %gamefolder%/GearGame/Binaries/Steam
• Run Gears5.exe

Something crashes the game, if run with WINEDEBUG=relay, I can watch full xbox game studios intro.

I think this is an EAC or anti-debug check, but maybe not

How did you get the Proton version like that though Lutris? It keeps failing to talk to Steam.

How did you get the Proton version like that though Lutris? It keeps failing to talk to Steam

Installed or custom versions displayed in the Wine list

For running game without steam I used steam emulator, for running with steam, need to rename Gears5.exe to Gears5_EAC.exe

How did you get the Proton version like that though Lutris? It keeps failing to talk to Steam

Installed or custom versions displayed in the Wine list

Image

For running game without steam I used steam emulator, for running with steam, need to rename Gears5.exe to Gears5_EAC.exe

Is that with the Runner set as Wine (Runs Windows games) or Wine Steam (Runs Steam for Windows games)? The first one fails to init Steam and the second one can't detect my GPU.

Is that with the Runner set as Wine (Runs Windows games)

This

The first one fails to init Steam

I used steam emulator (codex or mr.goldberg) for running without steam

the second one can't detect my GPU

If it is written by Gears 5, disable DXVK and rename EasyAntiCheat folder to anything

Btw, it doesn't crash for me now with last update and Proton 5.0-5 and no problems with "no gpu" with DXVK
https://streamable.com/j3p1uw
OBS doesn't record intro

Reproduce:

• Rename EasyAntiCheat folder to anything in %gamefolder%/GearGame/Binaries/Steam
• Rename Gears5.exe to Gears5_EAC.exe (original Gears5_EAC.exe rename to anything)
• Disable esync (PROTON_NO_ESYNC=1 %command%)

Looks like game still crashing but in background, without exit, seh exception in log and 0MB ram used in htop after few seconds of intro
With steam emulator (codex or mr.goldberg) I don't have symptoms above, but anyway black screen after intro

I can confirm that it loads with the default Steam version though I'm also using Proton 5.0-5 Next so basically 5.0-6. It doesn't seem to like GE or TDK builds though. Thanks @ga2mer for sharing!

It just loads that intro video then black screens for me too. Progress!

this is my log file.
i did the steps above, only the game launch picture will appear, and that's it
steam-1097840.log

@McMarius11 looks like Options: {'forcelgadd'} you did not disable esync

Where would that option do? In the launcher options?

any progress...?

@sinaflan maybe later it will run, but game still has issues with vkd3d

https://www.gamingonlinux.com/2020/10/collabora-expect-their-linux-kernel-work-for-windows-game-emulation-in-kernel-5-11

EAC via 5.11 & go play @ proton, right?

Btw, it doesn't crash for me now with last update and Proton 5.0-5 and no problems with "no gpu" with DXVK
https://streamable.com/j3p1uw
OBS doesn't record intro

Reproduce:

* Rename EasyAntiCheat folder to anything in %gamefolder%/GearGame/Binaries/Steam

* Rename Gears5.exe to Gears5_EAC.exe (original Gears5_EAC.exe rename to anything)

* Disable esync (`PROTON_NO_ESYNC=1 %command%`)

Looks like game still crashing but in background, without exit, seh exception in log and 0MB ram used in htop after few seconds of intro
With steam emulator (codex or mr.goldberg) I don't have symptoms above, but anyway black screen after intro

It seems that with newer proton it doesn't matter if you disable esync, fsync but the game still crashes right after Xbox Game Studios logo once it starts up if you follow what ga2mer said.
steam-1097840.log

Hello everyone, finally managed to launch the game in Proton. (although maybe I'm the only one with such a problem, because there is one report on protondb with a successful launch of the game without EAC)

WORKS ONLY WITH VERSION 1.1.122.0 (latest patch on April 26)

Steps:

• Rename EasyAntiCheat folder to anything in %gamefolder%/GearGame/Binaries/Steam
• Rename Gears5.exe to Gears5_EAC.exe (original Gears5_EAC.exe rename to anything)
• Rename GFSDK_Aftermath_Lib.x64.dll in %gamefolder%/Engine/Binaries/ThirdParty/GFSDK_Aftermath/x64/ to gfsdk.dll
• Place this dll (GFSDK_Aftermath_Lib.x64.zip) to the %gamefolder%/Engine/Binaries/ThirdParty/GFSDK_Aftermath/x64/

If you don't trust someone who suggests you use a dll, then you can build it yourself
gfsdk_source.zip (new value for patching is 0xE8, 0xb1, 0x3a, 0x31, 0x03, 0x90)
x86_64-w64-mingw32-gcc -shared -o GFSDK_Aftermath_Lib.x64.dll gfsdk.c GFSDK_Aftermath_Lib.x64.def -s

Of course EAC doesn't work (multiplayer may not work)

I turned this into a protonfixes/protontricks/winetricks verb:

https://github.com/GloriousEggroll/protonfixes/commit/3a06121f0bd065b084d9ce7d6bb60f975c9ea7c8

Replying to https://github.com/ValveSoftware/Proton/issues/3042#issuecomment-1046904681

This seems to be working great so far, the only side effect(which I think was because I left tiled resources on in-game) is that after a while the game performance diminishes to something like 10 fps until you go to the main menu and load the save game again.

Tried the workaround (thanks for all the info btw) and it works pretty well, other than some rendering issues, which I created a ticket in vkd3d-proton about.

Both, standard Proton and GE do this for me: Video

@kisak-valve Any word on compatibility for this improving? (Also surprised there isn't an EAC tag for related reports)

WORKS ONLY WITH VERSION FROM FEBRUARY 1 (1.1.119.0) (latest patch on February 21)
Doesn't work with patch from April 26, a fix will be in a while (most likely over the weekend)

@ga2mer Did you ever "update" your solution?

Did you ever "update" your solution?

I updated the dll, try it (I hope it still works)
If you have already used this patch, then just follow step 4 (should also work with proton-ge, but maybe protontricks will put the old version in (if it works, GE will most likely update the dll))

Did you ever "update" your solution?

I updated the dll, try it (I hope it still works) If you have already used this patch, then just follow step 4 (should also work with proton-ge, but maybe protontricks will put the old version in (if it works, GE will most likely update the dll))

Could you update the sources too? (some people are picky about compiled binaries without sources) -- thanks
-edit-

nevermind i see just the byte value needs to be changed

someone could help me my game version is 1.1.15.0 does it matter? I tried to follow step by step what @ga2mer said but the game closes after Xbox Game Studios Logo...

Replying to https://github.com/ValveSoftware/Proton/issues/3042#issuecomment-1046904681

This still works with the latest build which is nice. I wasn't sure how to use that protonfixes/protontricks/winetricks verb that you made @GloriousEggroll .

The game seems to not work at all on the latest proton experimental and proton 7.0, could be due to the Halo Infinite shared resources patches. Works just fine on proton 6.3-8

EDIT: If it helps out I'm attaching a log
steam-1097840.log

Sure thing, here it is - https://gist.github.com/kodatarule/baa6f7b50e8d2acddf6aa845bf51e3b4

@kodatarule Unfortunately, the game has EAC and has not chosen to work with the Valve EAC bridge for Proton support, so there is not much that we can do. The shared resources patches are not currently on 7.0-stable, so if 7.0-3 or 7.0-4 (now in public beta) fails, that is not the source of the regression. It is more likely that the workaround that you are using is no longer viable on 7.0 :/

Most probably VKD3D regression, works on 1660192387 experimental-bleeding-edge-7.0-22241-20220811-pabb98e-wb63e23-d5cdee4-vd00d03 with vkd3d from Proton 7.0-3

0138:info:vkd3d_get_vk_version: vkd3d-proton - applicationVersion: 2.6.0.
0138:info:vkd3d_instance_init: vkd3d-proton - build: 3e5aab6fb3e18f8.

Most probably VKD3D regression, works on 1660192387 experimental-bleeding-edge-7.0-22241-20220811-pabb98e-wb63e23-d5cdee4-vd00d03 with vkd3d from Proton 7.0-3

0138:info:vkd3d_get_vk_version: vkd3d-proton - applicationVersion: 2.6.0.
0138:info:vkd3d_instance_init: vkd3d-proton - build: 3e5aab6fb3e18f8.

I do believe so as the build with the Halo Infinite shared resources of vkd3d(in proton experimental) seems broken on even 7.0-4 the game launches once again.

EDIT: With that VKD3D build I also noticed problems in forza horizon 4...

@ga2mer Could you report that to the vkd3d-proton devs? https://github.com/HansKristian-Work/vkd3d-proton

@kodatarule Same request for the forza horizon 4 regression :)

Hello
Is work quacked version 097 on steam deck?

proton ge 7-43 is coming (it have some fixes for gears 5)

There appears to be a staging branch that may include the relevant EAC files, and the runtime has been added as a dependency in the Steam configuration. It may be worth keeping a close eye on this so that existing workarounds are prepared for EAC being fixed in a future update.

Because it's a private branch I don't know if the Aftermath SDK issue has been fixed - if someone understands what causes this game and not others to break when using this DLL, I would definitely send the information to The Coalition via their official support channels as they've been very responsive re: the anticheat side of things. (To be fair though, it's currently broken on Windows too because of hardware-enforced stack protection rejecting the driver...)

Aftermath SDK issue

There is no issues with Aftermath SDK, main issue is EAC and (probably) Arxan, my fix just bypasses EAC initialization (that probably encrypted by Arxan and it's crashes) and jump into game initialize

Aftermath is used because it is useless dll and through it you can change the game code (which again is protected by Arxan and you can't just change the hex of the executable)

Went ahead and forwarded this information to the support ticket, thanks for clarifying!

Game now verified as Steam Deck Playable, tested build is 10731442 and it's retail-staging/cert-staging, so probably patch soon

I bought the Game for My linux pc but the EAC is in a loop and never finishes. Will test on my steam deck downloading it now.

https://github.com/ValveSoftware/Proton/assets/9307070/ded0a7a8-336a-4279-b6a4-7559540d25a9

https://github.com/ValveSoftware/Proton/assets/9307070/125fa61a-42af-45a3-87f9-7efa337ab635

Reporting back from my steam deck: same thing.

Yes, the game is marked playable, but that requires a patch, on which Valve tested the game and that patch is still unreleased and unknown when it will be released (usually releases on Tuesday at 17:00 UTC, but as we see, that did not happen this week)

Also tested both on PC and Steam Deck, no changes have been made on the EAC side and the .so is not downloaded from their servers (and it seems it shouldn't be, if the game uses the old EAC)

Yes, the game is marked playable, but that requires a patch, on which Valve tested the game and that patch is still unreleased and unknown when it will be released (usually releases on Tuesday at 17:00 UTC, but as we see, that did not happen this week)

Also tested both on PC and Steam Deck, no changes have been made on the EAC side and the .so is not downloaded from their servers (and it seems it shouldn't be, if the game uses the old EAC)

Nice to know I hope they patch it soon! thanks for the reply.

Yes, the game is marked playable, but that requires a patch, on which Valve tested the game and that patch is still unreleased and unknown when it will be released (usually releases on Tuesday at 17:00 UTC, but as we see, that did not happen this week)

Also tested both on PC and Steam Deck, no changes have been made on the EAC side and the .so is not downloaded from their servers (and it seems it shouldn't be, if the game uses the old EAC)

Good to know, i bought the game sometime ago and just discovered it did not boot at all. Will wait for the fix

Update released
https://steamcommunity.com/games/1097840/announcements/detail/3660911636356230752
UPD: doesn't work for me on PC and Deck after update, but looks like my hack still works (and GE should too), trying to completely reinstall the game on Deck
UPD2: works on Steam Deck after reinstalling

Works well for me on my desktop, haven't tried on deck yet. I did have to remove all of my files, uninstall, and then re-install, as the first time I tried it crashed in the intro videos.

It looks like logging in works, but the online support depends on some security features not yet implemented. The most relevant lines:

[0621/163213.707:WARNING:cert_verify_proc_win.cc(111)] Unknown error -2146762482 mapped to net::ERR_FAILED
646.627:003c:0050:fixme:mountmgr:enumerate_credentials not supported
646.628:0184:0280:fixme:bcrypt:BCryptCreateHash ignoring object buffer
649.493:0184:0614:fixme:winhttp:request_query_option unimplemented option 94
650.292:0184:0280:fixme:bcrypt:BCryptGenerateSymmetricKey ignoring object buffer

The unknown error is CERT_E_REVOCATION_FAILURE, and option 94 is WINHTTP_OPTION_CLIENT_CERT_ISSUER_LIST. A lot of this seems to be coming from the CEF process but I would be surprised if this wasn't linked to the connection issues.

If someone crashed on the intro, try to delete the folder _CommonRedist and remove the prefix for this game (Developer->Delete proton files on Steam Deck), if it does not help, then run a file integrity check the game, if still not, just delete and reinstall the game (preferably after that delete the folder Gears5 in steamapps)

Update released https://steamcommunity.com/games/1097840/announcements/detail/3660911636356230752 UPD: doesn't work for me on PC and Deck after update, but looks like my hack still works (and GE should too), trying to completely reinstall the game on Deck UPD2: works on Steam Deck after reinstalling

So does multiplayer work on steam deck?

It looks like logging in works, but the online support depends on some security features not yet implemented. The most relevant lines:

[0621/163213.707:WARNING:cert_verify_proc_win.cc(111)] Unknown error -2146762482 mapped to net::ERR_FAILED
646.627:003c:0050:fixme:mountmgr:enumerate_credentials not supported
646.628:0184:0280:fixme:bcrypt:BCryptCreateHash ignoring object buffer
649.493:0184:0614:fixme:winhttp:request_query_option unimplemented option 94
650.292:0184:0280:fixme:bcrypt:BCryptGenerateSymmetricKey ignoring object buffer

The unknown error is CERT_E_REVOCATION_FAILURE, and option 94 is WINHTTP_OPTION_CLIENT_CERT_ISSUER_LIST. A lot of this seems to be coming from the CEF process but I would be surprised if this wasn't linked to the connection issues.

Following up on this, as I'm reasonably certain the error sits here, in the XBL HttpClient (so I was kinda right 4 years ago!):

https://github.com/microsoft/libHttpClient/blob/1c8386866fb180dd31890186291d4dbb9dc50811/Source/HTTP/WinHttp/winhttp_connection.cpp#L640

Implementing this feature in winhttp will likely be necessary for XBL services to work long-term.

Filed two upstream issues:

https://bugs.winehq.org/show_bug.cgi?id=55105
https://bugs.winehq.org/show_bug.cgi?id=55106

If you're having trouble connecting to online services, you will want to monitor these reports!

@flibitijibibo I'm getting a similar but slightly different looking log (towards the bottom) on Arch:
steam-1097840.log

If someone crashed on the intro, try to delete the folder _CommonRedist and remove the prefix for this game (Developer->Delete proton files on Steam Deck), if it does not help, then run a file integrity check the game, if still not, just delete and reinstall the game (preferably after that delete the folder Gears5 in steamapps)

are you referring to the Xbox Game Studios logo? because my game crashes there.

are you referring to the Xbox Game Studios logo? because my game crashes there

Yes, the only difference between the updated version and installed from scratch is the deleted (and installed in game prefix) vcredist and dx files from _CommonRedist, removing _CommonRedist and game prefix helped me to run this game on PC without reinstalling the entire game

You should also see if you have EasyAntiCheat Runtime installed (and if it works in other games)

Also if you used my hack before or ProtonGE (although it seems like it should work with new patch), you should switch to Proton 8 and run the game file check

If none of this helps, you should delete the game via Steam, then delete the prefix and the game folder completely and install the game, if after that the game crashes on XGS logo, perhaps the problem with EAC (check EAC step)

I can confirm that now after the new update works online but you have to manually select proton 7.0 not the one that defaults to (proton 8.0) Using Proton 7.0 I was able to matchmake and play online. This should be the default not 8.0

I can confirm this as well... I can't get a log at the moment, a log showing a full login in the main menu would be great if someone can grab it (a character model should pop in when it succeeds).

I can confirm this as well... I can't get a log at the moment, a log showing a full login in the main menu would be great if someone can grab it (a character model should pop in when it succeeds).

Does it work on desktop linux? Because for me it crashes when the xbox video comes up, but on the steam deck it works. 🤷🏻

Did a quick check of winhttp's commits, which is about the only thing I can think of as to why an older version works when the issue is an unimplemented feature, and it looks like 7.0 has three patches that 8.0 does not:

https://github.com/ValveSoftware/wine/commit/d8c2086d0e34450c9b8b5a85466a307a7fc708de
https://github.com/ValveSoftware/wine/commit/6d4dbf0762863f6f1f9dc4738258e98af05f06ec
https://github.com/ValveSoftware/wine/commit/7f18691e39d8de6668e3451f63b0326352b964f1

That last one in particular seems to be the reason this works: instead of passing the error back to the application it renegotiates on behalf of the client, skipping the whole roundtrip through libHttpClient - this is what allows login to work.

@ivyl, do you happen to know why these got removed?

I can confirm this as well... I can't get a log at the moment, a log showing a full login in the main menu would be great if someone can grab it (a character model should pop in when it succeeds).

Does it work on desktop linux? Because for me it crashes when the xbox video comes up, but on the steam deck it works. 🤷🏻

crashes for me also, going to try another driver

@flibitijibibo the patches were originally for Gears Tactics, specifically to speed up network connection. Those were dropped during the rebase as no longer needed for that purpose. We weren't aware that they were needed by Gears 5 too.

Thanks for finding the reason for the regression! We'll bring the patches back :-)

gears 5 work on proton ge 7-17 on proton 7 its give me an error message no GPU found and crashes on logo on any version 8 tkg or experimental

Did a quick check of winhttp's commits, which is about the only thing I can think of as to why an older version works when the issue is an unimplemented feature, and it looks like 7.0 has three patches that 8.0 does not:

ValveSoftware/wine@d8c2086 ValveSoftware/wine@6d4dbf0 ValveSoftware/wine@7f18691

That last one in particular seems to be the reason this works: instead of passing the error back to the application it renegotiates on behalf of the client, skipping the whole roundtrip through libHttpClient - this is what allows login to work.

Valve should hire @flibitijibibo . This guy is a beast.

@flibitijibibo the patches were originally for Gears Tactics, specifically to speed up network connection. Those were dropped during the rebase as no longer needed for that purpose. We weren't aware that they were needed by Gears 5 too.

Thanks for finding the reason for the regression! We'll bring the patches back :-)

Great to hear, thanks for the response! I'm not very good with web/security stuff so it's good to hear that the patches weren't omitted for some scary security reason or something 😅

Valve should hire @flibitijibibo . This guy is a beast.

If Valve ever gets into the business of developer outreach, happy to make myself available for native Linux builds! This was a weird exception for me, but my brother and I just really like Gears and Halo... (Of course, I do like being able to afford doing odd jobs like this every now and then!)

@flibitijibibo Thank you so much for the investigation :) This should be fixed in the latest experimental-bleeding-edge.

@flibitijibibo Thank you so much for the investigation :) This should be fixed in the latest experimental-bleeding-edge.

Confirmed on my test lab, thanks for the update!

Was able to test the game, as per suggestion switched to proton 7, made clean install of the game and it worked ootb with EAC on. Managed to play a few matches without issues. Seems like it is ootb experience without the need of hacky solutions to bypass eac to make it run + fully functional online MP + Horde + Coop.

U can right click on proton experimental and switch it to bleeding edge and play gears5 online. Worked for me, and there is a new proton ge8-6 u can try it also.

Hi all!
I tried to play the game both with Proton Experimental (Bleeding Edge as suggested) and with Proton 7.0-6.

With Proton 7.0-6 it worked flawlessy and I could play in multiplayer without any issues, basically ootb experience as mentioned before.
With Proton Experimental it gives me a runtime assertion failed as shown in the pic here.

I'm running Arch with kernel 6.4.1-arch2-1 and driver RADV 23.1.3 and my system is composed by a Ryzen 5900X and a RX 7900 XT. Also, as launch options I'm using gamemoderun and MANGOHUD=1.

Is anyone experiencing this too? This happens only with Gears 5, while the other games run without any problem.

Here are the logs of both Proton Experimental and Proton 7.0-6:
steam-1097840-Proton-Experimental-be.log
steam-1097840-Proton-7.0-6.log

P.S. By briefly looking at both logs, Proton Experimental sees my GPU as "Null hardware (RADV NAVI10)", while the other one sees it correctly as "AMD Radeon RX 7900 XT (RADV GFX1100)". Maybe this could be the culprit?

Hi @kisak-valve, here it is the link of the gist: https://gist.github.com/fumbio/7b8ab2e02a474851b0dc6a93423884e3.

I also tried the solution mentioned in the comment you linked and it actually made Gears 5 finally work with Proton Experimental.

However, I don't know if this is the right place to ask, but isn't this behavior strange (by my computer I mean)? I have never installed the AMDVLK driver, so I thought it would always point to the RADV driver as default choice with no conflicts like the one just happened.

Regardless, thank you very much! Really appreciating your help in this one and especially your work in Proton!

Arch has a history of suggesting the first alphabetical choice when asking the user to select between multiple dependency options. Your extended diagnostics information shows that lib32-amdvlk is installed.

I see. It's more clear to me now.

It should be noted that I'm a moderator, and not a Proton dev myself. Credit should go to the devs who are doing the actual work on the project.

Oh, sorry about that, you are completely right. Anyway, thank you regardless!

Gears 5 should work on both proton experimental and GE-Proton8-5 or higher. If you used a GE-Proton version lower than 8-5 you will need to remove these files:

/GearGame/Binaries/Steam/EasyAntiCheat-backup
/Engine/Binaries/ThirdParty/GFSDK_Aftermath

then verify your game files because the workaround prior to that involved moving game files around:

GE-Proton8-5

As noted:

    Gears 5 now works with EAC without any workarounds needed. If you previously used proton-ge to play, 
go into the game folder and remove these folders:

/GearGame/Binaries/Steam/EasyAntiCheat-backup
/Engine/Binaries/ThirdParty/GFSDK_Aftermath

Then verify the integrity of the game files so that it re-downloads the originals.

Hi. I'm getting a crash as the game attempts to go from the splash screens to the main menu (infinite loading cog, until that freezes up and the game crashes).

I've only managed to get to the main menu one time (and in-game!), out of roughly 100 attempts. Had it working one day, went to play it the next and nada. What's going on?

I've also tried a complete fresh install (of the game and my OS), wiped out all shader caches and proton compat data. The microsoft account login window never pops up, and it's supposed to pop up prior to getting to the main menu. So I believe that's where the issue lays?

Even worse, half the time the game will freeze up my whole OS and I have to hold the power button down on my PC to get it to turn off.

Proton Log: https://gist.github.com/dannyglover/ea583f46697f053c2074b59ff72ea096

System Info:

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.14-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 46.9 GiB of RAM
Graphics Processor: AMD Radeon RX 6750 XT

Replying to https://github.com/ValveSoftware/Proton/issues/3042#issuecomment-1711928815

Ok. After days of re-installing my OS, changing between different Linux distro's, proton versions etc, I've finally got it working (still using Fedora 38). The problem was the Mesa version. Fedora 38 currently has version 23.1.6, I switched to using mesa-git and my current version is now 23.3.0-devel.

After switching to the latest mesa driver, the game went into the menu really fast and works in-game too. I've tried booting it multiple times, rebooted the OS etc and it always seems to work now. Still using the latest Proton-Experimental as the compatibility layer.

Hope this helps others!

Replying to https://github.com/ValveSoftware/Proton/issues/3042#issuecomment-1711928815

im getting freeze up on mesa 23.2 think ill just wait for the official 23.3 to release

I have problem, Gears 5 just closes itself randomly. It may play for a few seconds or a few hours. I have tried GE Proton 8.31 and Proton 8 and experimental. Nothing seems to help. I can actually get into the game, why it closes itself is another question.

@Perfectlynk without more information, it's very hard to find out what's wrong. If you go to steam's help menu, there's a system information option, you should put that info in a Gist. For the game itself, add PROTON_LOG=1 %command%, this will generate a log file in your home folder, upload it here when the game crashes.

Hello,
Yes you are correct. Silly of me not to put log files in. I had to add Gears 5 as a gist as it was too big to add as an attachment.

I played Gears 5 for a bit and left to for 20 mins or so to do something and it had crash when I came back. I hope it helps.

https://gist.github.com/Perfectlynk/c7f2accd77aed273e737eb9d72c06da3 - Gears 5 crash

https://gist.github.com/Perfectlynk/a48603f146e9f23bc7020898774a7c7a - System

Any luck solving the random crashes?
Linux mint 21.3, i5 10600k, and Nvidia rtx 2060 here.

@nipnipj could you say more about your experience? What proton versions have you tried? Any patterns for the crashing? Or range of time for them to occur?

@nipnipj could you say more about your experience? What proton versions have you tried? Any patterns for the crashing? Or range of time for them to occur?

Proton versions? I've tried the available proton options in steam --- Default Proton, then Proton 7 --- then I tried latest Proton GE, 9-1. With any of them, the game crashes randomly. In one of them I manage to reach what I think is half of the first mission.
Any patterns? I don't think so. I was playing when, suddenly, the game just freezes and the close itself.
Time range? I just tried twice. It seems very random.

@Perfectlynk @nipnipj I couldn't reproduce the issue, I beat both the tutorial and first chapter without any crashing after having the game open for over an hour.

Checking protondb I could only find one reporting random crashes, and the system with those crashes happens to use linux 5.15, just like lynk. @nipnipj as you're using mint too, are you also on linux 5.15? If so, you could try updating to a newer kernel and see if the problem continues.

@Perfectlynk @nipnipj I couldn't reproduce the issue, I beat both the tutorial and first chapter without any crashing after having the game open for over an hour.

Checking protondb I could only find one reporting random crashes, and the system with those crashes happens to use linux 5.15, just like lynk. @nipnipj as you're using mint too, are you also on linux 5.15? If so, you could try updating to a newer kernel and see if the problem continues.

Mission one completed. I changed to Kernel: 6.5.0-25. No crashes. Thanks @simifor.

I'm using Endeavour OS with an RTX 3060 and it crashes every time I want to open the game, no matter which Proton version I'm using. Does it happen with anyone else?

steam-1097840.log

I'm using Endeavour OS with an RTX 3060 and it crashes every time I want to open the game, no matter which Proton version I'm using. Does it happen with anyone else?

The issue still happens, I'm using the 580.xx Nvidia Driver (open) and the issue happens after the Xbox logo is loading.

I'm using the Steam version.

I'll attach the log using the latest Proton GE 10-25.

I'm getting a crash (game freezes) pretty much every session anywhere from 30 seconds to 10 mins in. The log is here.

Game runs fine on Windows 11. In both Windows and Ubuntu, I'm streaming the game using Sunshine. Same thing happens using Proton Experimental and 9.0-4 with this system:

OS: Ubuntu 24.04.3 LTS
KERNEL: 6.14.0-35-generic
CPU: AMD Ryzen 7 5700X3D 8-Core
GPU: AMD Radeon RX 7800 XT (radeonsi, navi32, LLVM 20.1.2, DRM 3.61, 6.14.0-35-generic)
GPU DRIVER: 4.6 Mesa 25.0.7-0ubuntu0.24.04.2
RAM: 32 GB

EDIT: It looks like I was able to fix the crashes by switching to AMDVLK, so this (my crashes at least) are a Mesa issue rather than a Proton one.

@seadowg you should open an issue here https://gitlab.freedesktop.org/mesa/mesa/-/issues

@seadowg you should open an issue here https://gitlab.freedesktop.org/mesa/mesa/-/issues

Will do! I've not had a chance to this week, but will hopefully be able to next week.

Mesa issue here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/14438.

I've also found that AMDVLK crashes further into the game as well sadly. That obviously won't be fixed as the project has been discontinued.

steam-1097840.log

My updated logfile. I'm still having the same issue of crashing after the XBox Logo.

UPDATE: Nevermind, I had to delete the folders EasyAntiCheat and GFSDK_Aftermath_Lib, checked files and now it's working again. Actually the folders path to delete are:

• GearGame/Binaries/Steam/EasyAntiCheat
• Engine/Binaries/ThirdParty/GFSDK_Aftermath_Lib

Then check files with Steam and after those are missing, it will be downloading them again.

After that, open the game and it works again.

Thanks to GE himself.