Call of Duty: Modern Warfare 2 (10180/10190)

[Lampan-git]

The game works perfectly, except an annoying issue with the mouse were the sensitivity is varying, slowing down and accelerating making it hard to aim in game. Feels a bit like having dust under your mouse sensor(this is not the case).

• Arch Linux 4.18.5
  Gnome
• Intel Core i5-4670K
• GeForce GTX 970, Nvidia proprietary 396.54
• RAM 8GB

Tested on both proton version: 3.7-3 and 3.7-5 beta

[markmorris]

Game ran stable for me with the same issue as above (mouse is very weird) performance was also poor at times. The mouse issue reminds me of Windows mouse acceleration.

Ubuntu 18.04
Ryzen 5 1500x
AMD R9 390
16B RAM

Tested on both versions of proton 3.7.3 and 3.7.5.

[mausworks]

I solved this on my machine:

• OS: Arch Linux x86_64
• Kernel: 4.16.14-1-ck

What I did was to change the mouse polling frequency from "mouse decides" to "max 500 Hz".

Here's the Wiki entry I used: https://wiki.archlinux.org/index.php/mouse_polling_rate
I suggest reading it high.

First I ran sudo evhz to see what the polling rate of my mouse was. It usually stayed around 500 Hz, but sometimes went all the way up to 1000 Hz.

Then I went and plugged the mouse into a USB v2 port on my computer, as the Wiki states:

The USB 3 driver xhci-hcd may be ignoring the usbhid mousepoll setting.

I then then created /etc/modprobe.d/usbhid.conf with the following content:

# Use 500 Hz mouse poll interval.
# "Free" polling rate causes tracking issues in-game
# 1ms = 1000 Hz, 2ms = 500 Hz, 4ms = 250 Hz, 8ms = 125 Hz
# https://wiki.archlinux.org/index.php/mouse_polling_rate

options usbhid mousepoll=2

Then I ran:

sudo modprobe -r usbhid && sudo modprobe usbhid

And then finally, to confirm the fix worked:

$ systool -m usbhid -A 

Module = "usbhid"
    mousepoll           = "2"

However, upon running sudo evhz again, i still noticed some 1000 Hz reported, so I did what the wiki said:

You may have to unplug the mouse and plug it back in for the change to take effect.

Much better tracking in-game now. :)

EDIT: After reboot it's just as bad again, and I can't repeat the fix...

[kisak-valve]

Call of Duty Modern Warfare 2 (10180) Single Player does not Start.

Issue transferred from #2668.
@Sickday posted on 2019-05-10T21:16:33:

Compatibility Report

• Name of the game with compatibility issues:

Call of Duty: Modern Warfare 2

• Steam AppID of the game:

10180

System Information

• GPU: GTX 1070
• Driver/LLVM version: NVIDIA 430.09
• Kernel version: 5.1.0
• Link to full system information report as Gist:
• Proton version: 4.2-3

I confirm:

• [*] that I haven't found an existing compatibility report for this game.
• [*] that I have checked whether there are updates for my system available.

Symptoms

Single Player does not launch. Steam indicates the game is running, but it does not start at all and eventually stops running with no error messages.

Reproduction

Download the Game via Steam
Press "Play" once the download has completed.

steam-10180.log

[AwesamLinux]

Distro: Linux Mint 19.1 Tessa (64 bit)
GPU: Vega 56
Driver/LLVM version: Mesa 19.1.0-devel/9.0.0
Kernel version: 5.1.0-050100-lowlatency
Proton version: 4.2-3

I can confirm that the single player does not launch, Steam client just says running and then nothing happens. (no difference with WineD3D, Large adress aware, no esync or onethread)

Logs from trying to launch it with different proton versions:
steam-10180_proton-3.16-9.log
steam-10180_proton-4.2-3.log
steam-10180-proton-3.7-8.log
system_info.txt

[GH-A-CC]

Confirmed not working for me either. The Binary starts, hangs with nothing on screen, then eventually self-terminates after about 30 seconds.

I've tried Wine 4.7-staging, via Proton 3.16-9, Proton 3.7.8, andProton 4.2-4

Fedora 30, kernel: 5.0.11-300.fc30.x86_64
Nvidia Unix Driver 418.74.

[NerosTie]

My report on ProtonDB:

About Singleplayer: it's a DRM issue which is not yet supported (CEG, probably). It works if you replace iw4sp.exe with a cracked one.

[GH-A-CC]

My report on ProtonDB:

About Singleplayer: it's a DRM issue which is not yet supported (CEG, probably). It works if you replace iw4sp.exe with a cracked one.

Got any instructions on how to crack it?

Assuming we're not getting an official fix from IW?

[kisak-valve]

Hello @GH-A-CC, CEG support is being tracked at #753. You might be able to workaround the issue by copying iw5sp.exe from a steam-on-wine install on the same system.

[celphy]

I can successfully start the game and play Spec Ops on my own. The two player spec ops mode however does not work and I get stuck at "Connecting to IWN..." whether I click the button in the menu or get through Steam.

[Raklodder]

The singleplayer campaign, special-ops and multiplayer works (though had to be launched twice). However the two player online spec-ops remains stuck at "connecting to iwn"): https://gist.github.com/0be1186fb8b69c74c8bc9c6646d2240c

[Scramblejams]

Confirming two player Spec Ops stuck at "Connecting to IWN...". Tried with latest Steam beta client and Proton Experimental.

[deutschepost]

I have a Problem with this game not starting. It just shows a black splash screen. It works on the steamdeck, so i thought this was weird.

Distro: Manjaro Linux (64 bit) - Gnome
GPU: RTX 4070 Ti
Driver Version: 4.6.0 NVIDIA 550.67
Kernel Version: 6.1.85-1-MANJARO
Proton version: 9.0-1

One of the "non-standard" aspects of my system is, that i have an external audio interface. I attached the proton log and my pipewire config file. But I don't know if that's the problem because other games seem to work with this config.

steam-10180.log
pipewire.zip