Proton: Alan Wake (108710)

Created on 22 Aug 2018 · 32Comments · Source: ValveSoftware/Proton

Arch Linux
Kernel 4.18.3
Proton 3.7
Nvidia GTX 1070 - nvidia-vulkan 396.51
KDE Plasma 5.13.4
KDE Framework 5.49.0
Qt 5.11.1
GFX settings MAX

Alan Wake works without problems as tested so far.

Game compatibility - Unofficial

Source

tr37ion

👍1

Most helpful comment

I managed to solve the lack of audio in the cutscenes using PROTON 4.11-11 with
WINEDLLOVERRIDES="xaudio2_7=b,n"

Just in case, I use this for to play:
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_NO_ESYNC=1 WINEDLLOVERRIDES="xaudio2_7=b,n" PROTON_USE_D9VK=1 %command%

I detect some stuttering in the cutscenes when Vsync setting is ON but the gameplay is smooth.

CSahajdacny on 26 Dec 2019

👍4 ❤3 🎉2

All 32 comments

It's a shame most of us won't be able to play it; their music licenses expired and now they don't sell it anywhere :(

hadbabits on 23 Aug 2018

Edit: game now works for me since proton was updated.

My System Specs

LeJimster on 23 Aug 2018

Runs OK for me (performance wise) but I can see some light related glitches (some square-ish black shadows in the very beginning of the game). Tried various settings, still the same.
SteamOS, AMD 7970.

dubigrasu on 23 Aug 2018

Alan Wake is running here, but the performance is really low (I believe it's a DirectX 10 game, that's not yet enabled on DXVK) and the mouse control is very bad (could be related to #147).

libcg on 25 Aug 2018

I did a quick 10 minute test with Proton 3.7-3.

No audio in cut scenes, adding -forcestereo to launch options fixed that. Also a few minor graphical issues (some lighting & blur effects didn't look quite right), but nothing that was game breaking for what I tested.

OS: Ubuntu 18.04
GPU: GeForce GTX 970
Drivers: NVIDIA 396.54

rlac on 25 Aug 2018

👍1

@LeJimster Not sure, why you ask for DXVK. Proton is the DXVK implementation + Wineprefix for each game already. That is why we focus on Proton here not DXVK.

tr37ion on 26 Aug 2018

@tr37ion because the game currently uses Wines OpenGL and not DXVK. I've just raised a bug on the DXVK bug tracker, but it might be that the game doesn't use DX11.

Update: Seems like its a DX9 game only.

LeJimster on 26 Aug 2018

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

andrebadaia on 31 Aug 2018

Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-5 Beta:

Steam System Information

mimattr on 31 Aug 2018

Played for like 30 minutes and it worked ok. The performance was ok (~40 in high and ~55 in very low, it looks like a CPU bottleneck even though I have a i5 4670K that should run it 60fps+), there are graphical glitches like the grass (other transparent elements may have it too) - https://i.imgur.com/4EBUgzA.jpg - and I can't change the gamma using the in-game calibration. The game didn't crash and I used alt-tab to check other applications, changed a lot of graphics configs and Steam overlay. My GPU is a GTX 1060 6GB overclocked.

pedrofleck on 1 Sep 2018

The game crashes at launch on nvidia GPUs: https://paste.ubuntu.com/p/McYtrRVZdp/
System info: https://gist.github.com/vanyasem/f787469ec8c50cdd3728340ef4c73269
Proton log: steam-108710.log

The log suggests that it's a 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.

20180908141620_1

vanyasem on 8 Sep 2018

The game crashes at launch on nvidia GPUs: https://paste.ubuntu.com/p/McYtrRVZdp/
System info: https://gist.github.com/vanyasem/f787469ec8c50cdd3728340ef4c73269
Proton log: steam-108710.log

The log suggests that it's a NVAPI issue, tracked here: #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.

The crash with Nvidia GPUs wasn't present with Proton 3.7-3 and these graphical issues aren't present with me, only blocky grass textures

pedrofleck on 16 Sep 2018

The only thing in game nvapi used for is Nvidia 3D Vision (I suppose).
So if you don't expect this feature to work, than forget about nvapi (Proton 3.7-3 don't contain it).

NvAPI related logs

0009:trace:nvapi:DllMain (0x7b830000, 8, (nil))
0009:trace:nvapi:DllMain (0x7b830000, 1, (nil))
0009:trace:nvapi:nvapi_QueryInterface (150e828)
0009:trace:nvapi:NvAPI_Initialize ()
0009:trace:nvapi:nvapi_QueryInterface (33c7358c)
0009:trace:nvapi:nvapi_QueryInterface (593e8644)
0009:trace:nvapi:nvapi_QueryInterface (be7692ec)
0009:trace:nvapi:get_thunk_function (be7692ec)
0009:fixme:nvapi:unimplemented_stub function 0xbe7692ec is unimplemented!
0009:trace:nvapi:nvapi_QueryInterface (ac7e37f4)
0009:trace:nvapi:NvAPI_Stereo_CreateHandleFromIUnknown (0x158f58, 0x2ad08ac)
0009:trace:nvapi:nvapi_QueryInterface (4b708b54)
0009:trace:nvapi:NvAPI_D3D_GetCurrentSLIState (0x158f58, 0x33db64)
0009:trace:nvapi:nvapi_QueryInterface (1fb0bc30)
0009:trace:nvapi:NvAPI_Stereo_IsActivated ((nil), 0x33dccf)
0009:trace:nvapi:NvAPI_Stereo_IsActivated ((nil), 0x33dc8b)
...

The only thing the game do on my system with nvapi further: repeatedly called NvAPI_Stereo_IsActivate
Unimplemented_stub is NvAPI_Stereo_CreateConfigurationProfileRegistryKey

Also nvapi from wine-staging depends on d3d11, which probably will use DXVK's d3d11 and dxgi dlls (while running Proton), if PROTON_USE_WINED3D11 not set.

Tested on non-steam #125 , but there should be no big difference.

Using wine-3.16/wine-staging-3.16 , no matter is nvapi present or not, the game works fine using HIGH graphics profile.
No DXVK was set up, since game using dx9.

pchome on 16 Sep 2018

The grass with "blocky" textures seems to be present on Windows too, but it's related with AMD cards and AA or AF being forced by the driver. I don't have theses settings enabled and I'm using a Nvidia card and I have this bug though.
https://community.remedygames.com/forum/games/alan-wake/alan-wake-help-issues/7740-alan-wake-grass-textures-bug-help
https://steamcommunity.com/app/108710/discussions/0/828939978483402754/
https://steamcommunity.com/app/108710/discussions/0/864969953367987372/?l=turkish

pedrofleck on 23 Sep 2018

[REGRESSION] Alan Wake stopped launching in proton 3.16-3

Issue transferred from https://github.com/ValveSoftware/Proton/issues/1815.
@Patola posted on 2018-10-26T10:28:07:

Compatibility Report

Alan Wake (appid 108710) launches correctly in all proton 3.7 releases. When being run in 3.16-3, however, it clears the screen for a couple seconds then crashes.

System Information

Ubuntu 18.04 64 bits 16 GiB RAM, using LXDE as desktop environment
GPU: NVIDIA GTX 1070
Driver/LLVM version: NVIDIA binary driver 396.54.09
Kernel version: 4.15.0-38-lowlatency
Proton version: 3.16-3

I confirm:

[X] that I HAVE found an existing compatibility report for this game. It should run.
[X] that I have checked whether there are updates for my system available.

Symptoms

Click "Play". If it is the first time, it spends some time installing requisites. Then it clears the screen and enters fullscreen mode. Then it crashes. On versions of proton prior to 3.16, it launches correctly.
Note: Alan Wake's American Nightmare (a sequel) _works_ with the same setup, either in proton 3.7 or proton 3.16.

steam-108710.log

Reproduction

Install Alan Wake and click play.

@Patola commented on 2018-10-26T10:41:51

Game runs with launch options "PROTON_NO_ESYNC=1 PROTON_NO_D3D11=1 %command%". But it should run without them since it works that way on 3.7.

kisak-valve on 26 Oct 2018

Hi, I am very sorry, but further tests I made reveal that it works even without the launch options. Thing is, the game needs to be launched a half dozen times until he actually starts. It seems that as I wasn't able to launch at first and tried different options, it finally launched and I confused the options I made with something that was required to play the game.

Having said that, it is really odd that a game needs to be launched repeatedly until it finally "obeys". Computers were meant to be deterministic!

Patola on 27 Oct 2018

There is some glitching/artifacts on illumination. Here you can see the difference between a Windows system and a Linux with proton:
Linux: https://youtu.be/ECagCMGX95Y?t=157
Windows: https://youtu.be/2hIEFTcwtyI?t=165

I got the exact same bugged illumination as is showed on the first video using a RX 580 with Mesa 18.2.2 and Proton 3.16-3.

Marco-GG on 28 Oct 2018

@Marco-GG I'm not sure if this will be helpful as a fix for Proton. But I discovered the same bug when trying to run the game with gallium-nine, which has now been fixed. It's a real shame Proton doesn't have the ability to enable gallium-nine support, especially with VK9 being a year or two away at a minimum.

LeJimster on 4 Dec 2018

Weird lights
108710_20190104231932_1

And yes, is a DX9 game... VK9 project will be very usefull on Proton.

CSahajdacny on 5 Jan 2019

Hello community and devs,

this game are far to will add to a the white-list. It need resolved at least three bug, I make a list by order of importance:

1) No shafts or volumetric light at all. And this is one of the most characteristic features of the game design.
2) Lawn not show correct the transparency mask if Vsync is activated or it is configured during the game. Need to reset the game without Vsync to show correct, to tricky, but work for now.
3) Some issues whit sound at start or during the game. Some hang out it possible because this.
4) Performance. Bottleneck is important in this game. Is true, a lot of dx9 games in wine have this problem until. Is possible play between 20/30 FPS in most scenarios.

Greetings!

David Gámiz Jiménez

PD: Run in Proton 3.16-8 Beta. 4.2 not work sound in intro or game, not both at same time, maybe Faudio minor issue.

My Hardware:
AMD Phenom(tm) II X6 1055T Processor × 6
8GB RAM DDR3-1333
SSD Sata3 KINGSTON 120Gb / Seagate Sata3 HDD 1TB
Nvidia GeForce GTX 1060 OC 3072MB VRAM DDR5
Ubuntu 16.04 LTS (Last updated) / Unity 7
Driver Nvidia: 415.27 official graphics ppa
Gamepad Xbox360 Wired USB
Steam Gamepad
Webcam Logitech QuickCam E 3500

corvusd on 31 Mar 2019

I have no sound in cut-scenes. Any idea how to fix this? Sound in game-play and menus works.

Intel i5 6500
16GB RAM
nVidia GTX 1060 6GB 418.74
Arch x64 5.0.13

roman-bronis on 15 May 2019

In case someone reads this, the issue in my case was fixed by changing launch option to:
%command% -forcesurround
(even if you have stereo headphones, like I do)
If this ain't helping, according to what I read, -forcestereo is also worth trying.
EDIT: too soon. Even with parameter the sound in cut-scenes is not every time. If the game starts with sound on Remedy logo, the sound in cut-scenes works. If not, no sound in cut-scenes. Only thing which helps me is restarting the game till the point when the sound starts to work...

roman-bronis on 19 May 2019

For the adventurous... The game is now running pretty well on D9VK. You can grab up-to-date binaries here.

Extract the 32-bit d3d9.dll into Alan Wakes folder and add this to your Launch Options for the game in steam:
WINEDLLOVERRIDES="d3d9=n" DXVK_HUD=full %command%

You can remove the DXVK_HUD=full part if you don't want to see the stats, I just find it useful to verify the game is actually running d9vk.

LeJimster on 20 May 2019

With D9VK performance seems better, but I found at least one graphical glitch - in game, when activating special TVs, image is not displayed. Sound issue stays the same... ;)
Proton 4.2.4
20190521225528_1
Proton 4.2.4 with D9VK dll
20190521225743_1

roman-bronis on 21 May 2019

Hello @roman-bronis, graphical issues with D9VK should be reported to that project as it is not included in Proton.

kisak-valve on 21 May 2019

Hello @roman-bronis, graphical issues with D9VK should be reported to that project as it is not included in Proton.

Sorry, it wasn't supposed to sound like report of the issue. I meant it like status report for anyone interested in trying D9VK. ;)

roman-bronis on 21 May 2019

@kisak-valve D9VK is in proton yet. These issues now is OK, no?
For other way, the sound in cutscenes is the only real annoying bug for me. Is very strange. Because work in one way not in both. Fmod project can be help here?

corvusd on 14 Aug 2019

PD: Run in Proton 3.16-8 Beta. 4.2 not work sound in intro or game, not both at same time, maybe Faudio minor issue.

Nobody tried to install XNA instead of FAudio? Maybe this will fix sound issues?

RussianNeuroMancer on 24 Aug 2019

System Information

GPU: RX VEGA 56
GPU Driver: 19.1.0+aco+git1568912505-b738bf06917-1bionic2 (Valves PPA)
Kernel version: 5.3.1-050301-lowlatency
Distro version: Linux Mint 19.2 Tina (64 bit) (Cinnamon)
Proton version: 4.11-6

Compatibility Report

Out of the box there are rendering issues with foliage transparency, and game launches minimized.

But with D9VK (launch option "PROTON_USE_D9VK=1 %command%") the game looks correct, and launched fullscreen like it should.

aland9vk
Left is with D9VKsteam-108710-proton-4.11-6.log
steam-108710-proton-4.11-6-d9vk.log
system_info.txt

Using D9VK I have so far not encountered issues. Also I did not hear any audio crackling (that was a problem with some older Proton version I tried before, however it could be fixed with PULSE_LATENCY_MSEC=60).

steam-108710-proton-4.11-6.log
steam-108710-proton-4.11-6-d9vk.log
system_info.txt

AwesamLinux on 25 Sep 2019

The graphics are work ok, since few months thanks to Josh work in d9vk. But the main issue, at least for me, It is the sound in cinematics or FMV not work at all.

corvusd on 26 Sep 2019

👍2