ValveSoftware / ValveSoftware/Proton

Darkness Within 2: The Dark Lineage Director's Cut Edition (298950)

Open
#2,826 1 comment 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: Darkness Within 2: The Dark Lineage Director's Cut Edition
  • Steam AppID of the game: 298950

System Information

I confirm:

  • [ x ] that I haven't found an existing compatibility report for this game.
  • [ x ] that I have checked whether there are updates for my system available.

<PROTON_LOG>

steam-298950.log

Symptoms

Using Proton 4.2 the game becomes unresponsive to most keyboard input following in-engine cut-scenes, including being unable to use the Escape key to access the game menu which includes Save/Load/Options/Quit. The only keyboard keys that respond are F1 and F2 if you proceed to a point in the game where they are usable (picked up a flashlight and/or lamp).

The mouse is responsive as shown with the moving cursor and the right-click popup menu that appears, but the game is unplayable by these means without also keyboard movement or access to the game menu.

Alt-Tabbing is possible in my system and the most convenient means by which to shutdown the unresponsive game.

None of these problems are present using a 3.16 Proton prefix.

Reproduction

The problem can be reproduced by using a 4.2 prefix and starting a new game, allowing the cut-scenes to play out. At the point where the player should first gain movement control it will instead be unresponsive. This first encounter of unresponsiveness can be bypassed by pressing the Escape key during the cut-scenes and skipping ahead but this is not a viable workaround for the whole game because not all cut-scenes are skip-able.

Another example that isn't skip-able is available in the first room by picking up one the illuminating items (flashlight or lamp) and then shining light and approaching the trapdoor in the ceiling near the conventional exit door and left-clicking it (thus climbing up). No problem yet but then after left clicking the trapdoor from the attic area the return trip down is an in-game cut-scene and always reproduced the keyboard unresponsiveness for me, requiring an alt-tab to gain a means to quit the game.

Thanks for examining this issue.

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 linked steam-298950.log and reproducing the report with Proton 4.2 using a new game, then compare behavior with the working Proton 3.16 prefix. Check the cut-scenes and attic trapdoor sequence described in the report; done means keyboard input, including Escape and movement controls, remains responsive afterward.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.