Compatibility Report

Alternatively Instead of launching to the ingame window there is a desktop popup window that says:

Marathon
Marathon is not currently supported on the Steam Deck.
OK

Alternatively Instead of launching to the ingame window there is a desktop popup window that says:

Marathon
Marathon is not currently supported on the Steam Deck.
OK

Wow. I didn't think they'd give Steam Deck/Linux users that big of a middle finger.

Wow. I didn't think they'd give Steam Deck/Linux users that big of a middle finger.

This is consistent with their past behavior re: Destiny. Unclear if it is due to Bungie's own executives or those of their parent company Sony Entertainment Interactive, but it is very intentional and very coupled to a historical pattern of scapegoating Linux users as cheaters.

Wow. I didn't think they'd give Steam Deck/Linux users that big of a middle finger.

This is consistent with their past behavior re: Destiny. Unclear if it is due to Bungie's own executives or those of their parent company Sony Entertainment Interactive, but it is very intentional and very coupled to a historical pattern of scapegoating Linux users as cheaters.

With Helldivers 2 running on Linux, I think this may be a Bungie-exclusive approach.

Tested on void with GE 10-4, it launches, doesn't crash after the initial loading screen, however when it gets to the signin part, it fails with Marathon servers are not available W:12:00000057

Doubt this means anything, but the following messages show up in dmesg:

[  401.131662] umip: Marathon.exe[3714] ip:16fa13b00 sp:7f29f110: SIDT instruction cannot be used by applications.
[  401.131667] umip: Marathon.exe[3714] ip:16fa13b00 sp:7f29f110: For now, expensive software emulation returns the result.

Wow. I didn't think they'd give Steam Deck/Linux users that big of a middle finger.

I think that's a bit harsh. Especially given the user friendly nature of the Deck, it makes sense (to me at least) to implement a brief Deck-specific message instead of having the game seemingly run fine before showing a vague error.

I've looked into it and I think gearsovwar may have been right about it being WinHTTP initially.

Something is trying to call WinHttpQueryOption with option 147, which corresponds to WINHTTP_OPTION_SERVER_CERT_CHAIN_CONTEXT. Wine's WinHTTP DOES have a case for WINHTTP_OPTION_SERVER_CERT_CONTEXT, but nothing about chains whatsoever.

On the GnuTLS/Schannel thing, it looks like a similar situation where something is calling the functions get_cipher_algid and get_mac_algid of secur32.dll with cipher 23. Much less clear what cipher 23 is supposed to be, but in GnuTLS it matches GNUTLS_CIPHER_CHACHA20_POLY1305. Feels like a very odd obscure choice though, so I doubt it's correct.

EDIT: Very much looks like WinHTTP now to me. I've built Proton with WINHTTP_OPTION_SERVER_CERT_CHAIN_CONTEXT as just an empty case that returns true, and now instead of an error the game sits on the loading screen forever with the animation on the right of the screen continuing to play. Unfortunately ACTUALLY implementing it is well beyond my abilities.

EDIT 2: Oops! Not WinHttpSetOption, WinHttpQueryOption. With the test in the first edit I made a mistake and did not notice.

Not an engineer but I've somehow miraculously implemented WINHTTP_OPTION_SERVER_CERT_CHAIN_CONTEXT, and now the game logs in and briefly displays the lobby before showing this error message:

Shame.

Pretty sure no matter what you do locally, battleeye will always throw an error. It's a server side issue on battleeye side of things. Bungie has to whitelist the game running under linux. the battleeye client constantly sends signed packets back to the server, those packets are different when running on linux because it can't check everything it normally checks when running on windows. Right now, it's only allowing packets that come from the windows pipeline. It could start accepting the linux packets but that's entirely up to bungie.

On any Proton 11 version it just crashes before it can load the menu.
(Both experimental and the CachyOS proton 11 fork)
It keeps saying stuff about System.Security.Cryptography.CryptographicException: `MonoBtlsPkcs12.Import` failed.

steam-3065800.tar.gz

With the release of Season 2 I can no longer get past the first loading screen no matter what version of Proton I use. I've tried 11, Experimental, Hotfix, GE, etc. Most versions show this error:

Valve versions crash hard shortly after this message shows up, like how they did before. Curiously, GE does not display this error, instead freezing, even though GE compiled with the winhttp patch does. Not sure if this is an issue caused by the game or by my graphics drivers, although I'm on the latest official Mesa from the official Arch repos, so I doubt it.

Log file from patched GE: steam-3065800.tar.gz

EDIT: using proton-cachyos-10.0-20260330 (suggested by iFlxy in the Discord thread), I can get past this error and with the WINHTTP patch I get the exact same "Unsupported Platform" error from before. Shame.