ValveSoftware / ValveSoftware/Proton

Warhammer 40,000: Sanctus Reach (502370)

Open
#1,949 0 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: Warhammer 40,000: Sanctus Reach
  • Steam AppID of the game: 502370

System Information

  • GPU: GeForce GTX 1070
  • Driver/LLVM version: nvidia 396.54
  • Kernel version: 4.19.1
  • Link to full system information report as Gist:
  • Proton version: 3.16-4 Beta

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

After Intro the game crash with the message:
Failed to create device for rendering. Invalid resolution, or cannot run without at least shader model 3.0.

But if you create OPTIONS.TXT in
..../SteamLibrary/steamapps/compatdata/502370/pfx/drive_c/users/steamuser/My Documents/My Games/SANCTUS/OPTIONS.TXT

with this options from http://pastebin.com/RzYeqSCN the game start and is fully playable

The solution I found here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34764

Reproduction

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 reported failure after the intro on Proton 3.16-4 and inspect the OPTIONS.TXT workaround at the listed compatdata path, along with the linked WineHQ report. Reproduce it on the reported Linux, kernel, GPU, and driver details; the issue provides no log or reproduction steps, so completion criteria are not defined beyond launching the game without the manual configuration.

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
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.