ValveSoftware / ValveSoftware/Proton

Call of Duty 2 (2630)

Open
#2,693 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Game compatibility - Unofficial
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Compatibility Report

  • Name of the game with compatibility issues: Call of Duty 2
  • Steam AppID of the game: 2630

System Information

  • GPU: GTX 960
  • Driver/LLVM version: Nvidia 418
  • Kernel version: 5.0.015
  • Link to full system information report as Gist:
  • Proton version: 4.2-4

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.

steam-2630.log

Symptoms

Movies arent visible. You can hear them but cannot see them. Some people are able to get the game to launch, but it almost never works for me. Instead after skipping the (not visible) movies, I get a black screen and it hangs. I have to hard reset my computer.

Reproduction

Play the game, try to go in game

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached steam-2630.log and reproduce Call of Duty 2 (Steam AppID 2630) using Proton 4.2-4 on the reported Linux/Nvidia setup. Compare the invisible movies and black-screen hang with the reported behavior; done means the game launches, movies render, and it no longer hangs.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.