ValveSoftware / ValveSoftware/Proton

Sid Meier's Civilization IV: Colonization (16810)

Open
#4,547 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: Sid Meier's Civilization IV: Colonization
  • Steam AppID of the game: 16810

System Information

  • GPU: Intel Skylake GT2 (Intel HD Graphics 520)
  • Driver/LLVM version: Mesa 20.2.6
  • Kernel version: 5.4.0-60-generic
  • Link to full system information report as Gist: link
  • Proton version: 5.13

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-16810.log

Symptoms

Game won't start after Proton 5.13 update

Reproduction

  1. Update Proton 5.13
  2. Start game through Steam
  3. After a while, "stop" button becomes "play" again

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 by reproducing the launch failure with Proton 5.13 using the listed steps, then inspect the attached steam-16810.log and linked system information for the failure point. Done means identifying a confirmed compatibility cause or a validated change that lets Sid Meier's Civilization IV: Colonization start.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
game-dev, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.