ValveSoftware / ValveSoftware/Proton

Dead Space 3 (1238060)

Open
#4,004 7 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: Dead Space 3
  • Steam AppID of the game: 1238060

System Information

  • GPU: AMD Radeon VII
  • Driver/LLVM version: Mesa 20.1.1
  • Kernel version: 5.6.0-2-amd64
  • Link to full system information report as Gist:
  • Proton version: 5.0-9

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

Symptoms

Like all other EA-published titles I've tried since the inclusion of their former Origin-exclusives, this game seems to install correctly, but after the Origin thin client displays, it throws the error message about being unable to install the game in the specified folder, followed by another error window stating "We are unable to connect to EA servers to activate Dead Space 3 on this computer using your account. Please try again later." Clicking the "Exit" button on the window causes the game to exit.

Reproduction

This happens each time the game is installed and executed from Steam.

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

Begin with the linked steam-1238060.log and the reported Proton 5.0-9/Linux system details; reproduce the launch from Steam and inspect the Origin installation and activation errors. Done means Dead Space 3 can install and activate without the reported errors. The issue names no source file or test, so resolving it requires locating the relevant compatibility path.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.