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

[speakn2pabst]

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

• GPU: RX Vega 56
• Driver/LLVM version: Mesa 19.0.6/8.0.0
• Kernel version: 5.1.8-1
• Link to full system information report as Gist: https://gist.github.com/speakn2pabst/307ec107f594893afd8939a4eeacbba9
• Proton version: 3.16-4 and 4.2-7

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.

[speakn2pabst]

I'm happy to report that this input regression issue is not present in Proton 4.11-1 . I tested both examples that produced the issue in the past and maintained keyboard input responsiveness throughout.

Great to see and many thanks for advancing Proton and the Linux gaming ecology.

P.S. I also tested the D9VK option on this title and it rendered without issue and with good performance and the input issue was not present either.