ValveSoftware / ValveSoftware/Proton

Lost Ember (563840)

Open
#6,003 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Game compatibility - Unofficial XAudio2
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: Lost Ember
  • Steam AppID of the game: 563840

System Information

  • GPU: RX 6800 XT (desktop) and Steam Deck APU
  • Driver/LLVM version: mesa 22.1.3 (Arch Linux) and mesa 22.0.0_devel.148041.radeonsi_20220224-1 (Steam Deck)
  • Kernel version: 5.18.11-264-tkg-bmq (Arch Linux) and 5.13.0-valve15-1-neptune-02197-gf6ec7ad3762a (Steam Deck)
  • Link to full system information report as Gist: https://gist.github.com/Patola/e51e3af1be3c7d233b8f14fb21be1aa6
  • Proton version: 7.0-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

  • Start the game
  • A small animation appears on a black screen with some scratching sounds. Then it stops with a black screen.
  • Same thing on the Steam Deck and on my Desktop.
  • Can also try on my laptop with nvidia if you think it could give useful information.

Reproduction

Same as symptoms

steam-563840-steam-deck.log
steam-563840-5900x-5x600xt-proton703.log

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 reviewing the attached steam-563840-steam-deck.log and steam-563840-5900x-5x600xt-proton703.log, then reproduce the black-screen launch failure with Proton 7.0-3 on the listed systems. Done means identifying the compatibility cause and confirming a working launch, but the report does not name a source file, test, or implementation entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
operating-systems, tooling
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.