Confirmed.

Distro: Linux Mint 19 Tara
Processor: AMD Ryzen 7 1700
GPU: GTX 1070, Nvidia proprietary driver 396.54
RAM: 32GB
Kernel (custom) - 4.17.14 (optimized for Ryzen)
Resolution: 1920x1080
Proton 3.7-3

The game crashes at launch sometimes: https://paste.ubuntu.com/p/x5M5Q8KZfK/
System info: https://gist.github.com/vanyasem/f787469ec8c50cdd3728340ef4c73269
This seems totally random, but the log suggests that it's related to nvapi issue tracked here: https://github.com/ValveSoftware/Proton/issues/165. The workaround mentioned here fixes the crash issue.

However, using any graphics preset other than "very low" results in a black screen or glitchy textures (probably related to the fact that nvapi is a stub). I consider this game not being whitelist-ready as of now.

I only had issues with no audio in cutscenes (audio in menu and gameplay) and adding the launch option -forcesurround fixed it for me until I restarted the game.
The -forcesurrond option appears to be a bit of a hit & miss as it doesn't seem to be enforced every time the game gets launched.

Removing the launch option, start the game, exit the game, then re-add the launch option a couple of times eventually re-enabled audio in cutscenes again.

Once audio was working in cutscenes I managed to play it continuously for a few hours (approx. 4hrs) with a PS4 controller and experienced no additional issues.
Graphical preset was set to HIGH, which seems to have been auto-detected at install/launch.

• OS: Ubuntu 18.04.1 LTS (64 bit, 4.19.1-041901-generic)
• CPU: AMD Ryzen 5 2600X (6c/12t)
• GPU: RX Vega 56
• RAM: 32GB
• Driver: Mesa 19.0.0-devel - padoka PPA
• Proton: 3.7.8 (Steam System Information)

Seems to have the same "no sound in cutscenes" issue as Alan Wake https://github.com/ValveSoftware/Proton/issues/156#issuecomment-493785140 but worse. I was able to play Alan Wake with sound in cut-scenes after couple of restarts, but not with this game (I tried both -forcesurround and -forcestereo)

Intel i5 6500
16GB RAM
nVidia GTX 1060 6GB 418.74
Arch x64 5.0.13
Proton 4.2-5

@kisak-valve Woah, with 3.16-9 Beta, sound in cut-scenes started working without any parameters (again, it needs some restarts). It also crashes less. I will get you logs tomorrow.

Success of sound working in cut-scenes is ~10% of game starts with 3.16-9 Beta. Methodology is: if the sound in game intro works, it will also work in the game cut-scenes (had practice with this with previous Alan Wake game).
With 4.2-5 I wasn't able to get into the menu, game crashes either before the intro, or immediately after the intro.

proton3.16-9Beta_nosoundcutsc_1.log
proton3.16-9Beta_nosoundcutsc_2.log
proton3.16-9Beta_nosoundcutsc_3.log
proton3.16-9Beta_soundcutsc_1.log
proton3.16-9Beta_soundcutsc_2.log
proton3.16-9Beta_soundcutsc_3.log
proton3.16-9Beta_crash_1.log
proton3.16-9Beta_crash_2.log
proton4.2-5_crash_1.log
proton4.2-5_crash_2.log
proton4.2-5_nosoundcutscandcrash_1.log
proton4.2-5_nosoundcutscandcrash_2.log
proton4.2-5_nosoundcutscandcrash_3.log

@kisak-valve I hope my long list of logs will help to identify the issue. ;)

Sticking WINEDLLOVERRIDES="xaudio2_7=b,n" %command% into the launch options consistently fixes audio for me.

Proton 5.0-5b, Linux 5.5.10, nvidia 440.64.

Sticking WINEDLLOVERRIDES="xaudio2_7=b,n" %command% into the launch options consistently fixes audio for me.

Proton 5.0-5b, Linux 5.5.10, nvidia 440.64.

same here i used that launch option and i finished the game on nvidia proprietary driver
i didn't experience any issues except that one

Crashed on Steam Deck using the Epic Game version as Non Steam Game with Proton 7-2 GE and launch option "WINEDLLOVERRIDES="xaudio2_7=b,n" %command%". It appears this error:
Constant "g_mLocalToClip" has unknown class
Any advice?

Constant "g_mLocalToClip" has unknown class
Any advice?

Open winetricks and install missing windows component: d3dcompiler_47.dll

That fixed it for us

Hi @kisak-valve . Your suggestion fixes the game for Proton 9.0-2. Thank you

Game's not using my nvidia GPU no matter which Proton version I use.
the proton log says:

nfo: D3D9: Hiding actual GPU, reporting:
info: vendor ID: 0x1002
info: device ID: 0x73df
info: device description: AMD Radeon RX 6700 XT
which is pretty weird.

steam-202750.log

@matezoltanfarkas on steam's top bar you'll find "Help", click that and then "Steam Runtime Diagnostics", after a few minutes it'll print your system information. Copy that into a text file and upload it here.

@simifor , here's your magic JSON. Do you have any idea what's happening in the background?
runtime_info.json

thanks a million @kisak-valve ! that makes sense. I've written to Rico and will react with a rocket to this comment if the issue is solved.
Have a nice weekend!

The issue has not been fixed.
In fact, I had to install the both packages libnvidia-compute-575:i386 and libnvidia-gl-575:i386 of the 575 series to get it finally working.
Repo maintainer never answered.