protonscr

Deadlight: Director's Cut

protonopen appid 423950Game compatibility - UnofficialXAudio2.NET
ValveSoftware/Proton#2571 · opened 2019-04-21 by omicron-b · updated 2020-02-09 · 3 comments · github · game page · search this game
Oomicron-b 2019-04-21 github

Compatibility Report

  • Name of the game with compatibility issues: Deadlight: Director's Cut
  • Steam AppID of the game: 423950

System Information

  • GPU: GTX 1060
  • Driver/LLVM version: nvidia 418.56
  • Kernel version: 5.0.0-13
  • Link to full system information report as Gist
  • Proton version: 4.2-3

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.

steam-423950.log.zip

Symptoms

  1. On first run, "Preparing to launch" window always hangs until you restart Steam.
    Happened on 2 systems.
  2. White, black, or black and white artifacts of screen all the time except menus.
    20190421064321_1

Reproduction

Start a new game or load a saved game.

RRiantAnda 2019-04-21 github

I have the same issue with the original Deadlight (211400), see
#910
Seems to be an Nvidia issue :-(

In the logs I can see:
19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader [#11](/issue/ValveSoftware/Proton/11): 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log Vertex info 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log ----------- 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[1]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[2]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[3]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[4]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[5]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[6]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[7]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[8]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[9]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[10]" might be used before being initialized 19341.069:0028:0042:fixme:d3d_shader:print_glsl_info_log 0(23) : warning C7050: "vs_out[11]" might be used before being initialized

Oomicron-b 2019-08-23 github

graphical issues are fixed with Proton 4.11-2 and PROTON_USE_D9VK=1 for me, will retest the hang on first run issue.

Oomicron-b 2019-08-24 github

first start also works fine for me

Proton versions

Launch options