CoD4 Modern Warfare on Proton nonfunctional?

[HellsBells]

Linux Distribution: Pop!_OS
Desktop Environment: GNOME
Graphics Card: Nvidia RTX 2070 Super (Founders)
GPU Driver Version: 455.38

I recently loaded Pop!_OS onto a gaming PC I built with the intent of running DVDs and everything that can be run on Proton on the Linux side, and Blurays and games that won't play nice on the Windows side. Since under taking this project, I've run into issues with Call of Duty 4 Modern Warfare, which I've successfully run on previous Linux boxes and are classified Platinum by ProtonDB.

Upon launch attempts First Time Setup, bringing up some sort of Punkbuster dialogue that subsequently fails, followed by a pop up reading "Application Load Error (0x02)." Deleting the PB folder in the CoD folder will skip the installation, but the Application Load Error will still occur. I've tried different Proton versions, validating content, uninstalling, reinstalling, even booting Windows, installing there, and then moving the files over to my Linux partition, all of which have failed to successfully launch the game.

Anyone ever seen anything like this? Thanks in advance for any help that can be provided!

[class101 [OLED deck]]

Have you tested the launch options PROTON_LOG=1 %command% and look in the home folder for a steam-APPID.log file.

[ripper81]

Maybe you should try forcing Proton 5.0-10. It seems that Proton 5.13 has problems with this title.

[HellsBells]

https://gist.github.com/HellsBells24/ad03bb3d5bb626d1a8b01adaf4686252

There's the contents of the log, if that helps.
Tried to force 5.0-10, but no joy there.

[Marlock]

steam > help > system info > copy-paste here...

also run "vulkaninfo" on the terminal and paste output here or to another gist.github.com entry

[Marlock]

and for broad help getting proton to run, check out item [4] here:
https://steamcommunity.com/app/221410/discussions/0/1636417404917541481/

[class101 [OLED deck]]

Publicado originalmente por HellsBells:

https://gist.github.com/HellsBells24/ad03bb3d5bb626d1a8b01adaf4686252

There's the contents of the log, if that helps.
Tried to force 5.0-10, but no joy there.

the log shows that there is no missing libraries, but not relevant errors so except that it starts unloading modules right after loading d3dx9_34.dll so something is wrong around that.

24932.123:00b8:00bc:trace:loaddll:load_native_dll Loaded L"Z:\\mnt\\33de0755-49c8-4af7-8f85-0f1245d6775e\\SteamLibrary\\steamapps\\common\\Call of Duty 4\\d3dx9_34.dll" at 0x61d00000: PE builtin
24932.124:00b8:00bc:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\ucrtbase.dll" : builtin

test this launch option

WINEDLLOVERRIDES=d3dx9_34=n,b or try deleting it from the CoD4 dir as this file is already in system32

the fact it unloads at that points might also indicates you have a graphic issue, like a game display setting (windowed/fullscreen?) etc..

[HellsBells]

Publicado originalmente por class101 linux:

Publicado originalmente por HellsBells:

https://gist.github.com/HellsBells24/ad03bb3d5bb626d1a8b01adaf4686252

There's the contents of the log, if that helps.
Tried to force 5.0-10, but no joy there.

the log shows that there is no missing libraries, but not relevant errors so except that it starts unloading modules right after loading d3dx9_34.dll so something is wrong around that.

24932.123:00b8:00bc:trace:loaddll:load_native_dll Loaded L"Z:\\mnt\\33de0755-49c8-4af7-8f85-0f1245d6775e\\SteamLibrary\\steamapps\\common\\Call of Duty 4\\d3dx9_34.dll" at 0x61d00000: PE builtin
24932.124:00b8:00bc:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\ucrtbase.dll" : builtin

test this launch option

WINEDLLOVERRIDES=d3dx9_34=n,b or try deleting it from the CoD4 dir as this file is already in system32

the fact it unloads at that points might also indicates you have a graphic issue, like a game display setting (windowed/fullscreen?) etc..

No luck with that launch option or deleting the file, I'm afraid

Publicado originalmente por Marlock:

steam > help > system info > copy-paste here...

also run "vulkaninfo" on the terminal and paste output here or to another gist.github.com entry

Here is the vulkan gist https://gist.github.com/HellsBells24/7a31c51dfbbd3d7a02d7017019399d64
and the system info gist https://gist.github.com/HellsBells24/8a3ea7bdbd0b5e476219c8fa2582c6fe

[class101 [OLED deck]]

Try to load only the native version since I see in the logs it loads both before stopping

WINEDLLOVERRIDES=d3dx9_34=n

out of idea else, I think you have to look around system logs like ~/.xsession-errors , there should be some logs of what is wrong somewhere else

[HellsBells]

Darn, still a no go. Thank you for your help though

[class101 [OLED deck]]

Well I know how to go deeply but you will have to investigate into a few GB of logs with +relay

PROTON_LOG=1 WINEDEBUG=+timestamp,+pid,+tid,+debugstr,+loaddll,+mscoree,+msgbox,+setupapi,+relay,-snoop,+seh

this will generate a huge log of system calls, that's only way i know to get more logs of what is going on at the point of the d3dx9 dll is unloading.

Hope you will find the solution