protonscr

Call of Duty Modern Warfare II Open Beta

protonopen appid 2075730Game compatibility - Unofficial
ValveSoftware/Proton#6184 · opened 2022-09-24 by fontivan · updated 2022-09-26 · 3 comments · github · game page · search this game
1 matching comments, n / p to jump
Ffontivan 2022-09-24 github

Compatibility Report

  • Name of the game with compatibility issues: Call of Duty Modern Warfare II Open Beta
  • Steam AppID of the game: 2075730

System Information

OS: Fedora Linux 36 (Workstation Edition)
KERNEL: 5.19.9-200.fc36.x86_64
CPU: AMD Ryzen 9 5900X 12-Core
GPU: NVIDIA GeForce RTX 3080
GPU DRIVER: NVIDIA 515.65.01
RAM: 32 GB
Full report gist: https://gist.github.com/fontivan/4e9beefd0203aac1cef66a2bd646eaa4

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.

Log files

steam-2075730.log.proton-7.0-4.txt
steam-2075730.log.proton-experimental.txt
steam-2075730.log.proton-ge7-35.txt

Symptoms

Game crashes pretty much immediately after launch regardless of the Proton version used

Reproduction

Launch the game, observe crash

Additional notes

Although this is the Open Beta version of the game, I would expect the final release (AppID: 1938090) to exhibit the same behaviour unless something changes between now and launch on Oct 28th. I would also expect the crash is probably related to the kernel level Ricochet anti cheat that Activision has been adding to their recent Call of Duty games (https://support.activision.com/articles/ricochet-overview)

Ffontivan 2022-09-24 github

I did some slight digging and I was expecting to find some Ricochet information in the executable, but I didn't. I do see references to Warden though which I believe they use in like Overwatch and works fine in Proton?

[12:18:00] user@user-linux {/home/user/.steam/steam/steamapps/common/Call of Duty Modern Warfare II Beta} 
$> strings cod.exe | grep -i 'cheat'
TAC_DBG: Anticheat initialization failed.
TAC_DBG: Cheat detection initialization failed.
TAC_DBG: Undefined anticheat state.
Failed to retrieve antiCheat instance from lobbyService to start task bdAntiCheat::reportExtendedAuthInfo().
Failed to start task bdAntiCheat::reportExtendedAuthInfo()
Reload_CheatAmmo
[12:18:43] user@user-linux {/home/user/.steam/steam/steamapps/common/Call of Duty Modern Warfare II Beta} 
$> strings cod.exe | grep -i 'warden'
WARDEN_DBG: Generating battle.net UID.
WARDEN_DBG: Initialize hooks.
WARDEN_DBG: Memory page unfolding failed.
WARDEN_DBG: Memory session on sysid seeding failed. Check with Blizzard if that affects unpacking.
WARDEN_DBG: Benchmark CPU performance for delayed rogue loads.
WARDEN_DBG: Make sure the sysid is seeded for the memory session before we call Warden.
WARDEN_DBG: System bit tag triggered.
[12:20:03] user@user-linux {/home/user/.steam/steam/steamapps/common/Call of Duty Modern Warfare II Beta} 
$> strings cod.exe | grep -i 'ricochet'
[12:20:09] user@user-linux {/home/user/.steam/steam/steamapps/common/Call of Duty Modern Warfare II Beta} 
$> 
Ffontivan 2022-09-24 github

Attempting to launch using winedbg always results in the same exception at the same address
Interestingly though, the address is different for the Steam vs Battle.net (Lutris) versions of the game

Steam:

Unhandled exception: 0xc0000409 in 64-bit code (0x000001481f79a1).

Battle.net:

Unhandled exception: 0xc0000409 in 64-bit code (0x00000148433379).
LLepaBrenaa 2022-09-26 github

If I am not mistaken, new COD will definitely use Riccochet, and that is kernel level anti cheat. Pretty much the same as Valorant.
Therefore it won't run on Linux. Nothing can be done here.
Someone correct me if I am wrong.

Proton versions

Error codes