Updated to Kernel 4.18.10, LLVM8 still installed;
Updated to NVIDIA 410.57
Issue persists.
Sysinfo https://gist.github.com/simpleauthority/886c12521758a63bc26145e77077dd23
Game log: steam-292730.log
Updated to proton-git 20180928b.1-2, kernel same version, LLVM same version, nvidia same version; issue persists. Have not attempted flags.
Sysinfo https://gist.github.com/simpleauthority/adf702825e1dbf6f8dcef5a76387d464
Game log steam-292730.log
(p.s. just updating, not complaining)
My bad. Misclick
Persists with proton 3.7.8-beta.
Kernel: 4.18.12
LVM same
Nvidia same
No flags.
Sysinfo https://gist.github.com/simpleauthority/994c6d0233b5c692b7ed7faa245c2c2f
Game log steam-292730.log
Still not working with proton 4.11-8
There is a bug report at winehq with some kind of patch/hack which never got tested.
The current log is really huge steam-292730.log
There is stuff like:
27062.150:002f:0030:err:ole:CoGetClassObject class {f3bdfad3-f276-49e9-9b17-c474f48f0764} not registered
27062.150:002f:0030:err:ole:CoGetClassObject class {f3bdfad3-f276-49e9-9b17-c474f48f0764} not registered
27062.151:002f:0030:err:ole:create_server class {f3bdfad3-f276-49e9-9b17-c474f48f0764} not registered
27062.151:002f:0030:fixme:ole:CoGetClassObject CLSCTX_REMOTE_SERVER not supported
27062.151:002f:0030:err:ole:CoGetClassObject no class object {f3bdfad3-f276-49e9-9b17-c474f48f0764} could be created for context 0x17
27058.228:002f:0030:fixme:wbemprox:wbem_locator_QueryInterface interface {00000126-0000-0000-c000-000000000046} not implemented
And a giant load like this:
27058.182:002f:0030:trace:seh:call_vectored_handlers calling handler at 0x14b635acb code=80000003 flags=0
27058.182:002f:0030:trace:seh:call_vectored_handlers handler at 0x14b635acb returned ffffffff
27058.206:002f:0030:trace:seh:NtRaiseException code=c000001d flags=0 addr=0x14b792e9d ip=14b792e9d tid=0030
27058.206:002f:0030:trace:seh:NtRaiseException rax=000000000022fb18 rbx=0000000147b78aa8 rcx=000000007bd4e4e0 rdx=000000007bd4e4e8
27058.206:002f:0030:trace:seh:NtRaiseException rsi=0000000147b78aa8 rdi=0000000000000005 rbp=000000000022fac0 rsp=000000000022fa88
27058.206:002f:0030:trace:seh:NtRaiseException r8=0000000000000002 r9=00000000000b9850 r10=00000000000b97f0 r11=00000000000b97f0
27058.206:002f:0030:trace:seh:NtRaiseException r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000
Still broken as of Proton 5.0.7.
Same Error.
Kernel: 5.6.11
Manjaro XFCE
Works with Proton 5.13
No it's still borked, COD: IW says that steam needs to be running and shows it in a generic wine popup with Proton 5.13-1

Long time, no update. I can confirm, using the Proton Experimental branch & the Steam Runtime Soldier Beta at the least (I have not done comprehensive testing prior to this version) that Infinite Warfare runs.
Ok, I've found an incredibly strange regression that might be in Mesa rather than Proton, but I don't have the capacity to test it at the moment. The above screenshot was taken on the 21.7 Mesa revision. I've since updated to 22.0 Oibaf PPA... and the game no longer works. It crashes before ever launching. Here's the log:
steam-292730.log
gist.txt - old SteamInfo
gist2.txt - new SteamInfo
...disregard, an update published today fixed this.
Anyway of fixing the vram maxing out? This causes performance issues.
proton experimentalx1 2022-08proton 5.13-1x1 2020-10proton 5.13x1 2020-10proton 5.0x1 2020-05proton 4.11-8x1 2019-11proton 3.7x2 2018-10
Compatibility Report
System Information
I confirm:
steam-292730.log
Symptoms
"DirectX encountered an unrecoverable error. Check the readme for possible solutions"
Reproduction
Try to run the game.