The Walking Dead: Saints & Sinners (916840)

[frostworx]

Compatibility Report

• Name of the game with compatibility issues: The Walking Dead: Saints & Sinners
• Steam AppID of the game: 916840

System Information

Distro:Arch Linux
Kernel:5.4.15-arch1-1
RAM:16 GB
GPU-Treiber:NVIDIA 440.44
GPU:NVIDIA GeForce RTX 2080
CPU:Intel Core i7-8700K @ 3.70GHz
Proton: 1578946641 proton-4.11-12

I confirm:

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

the only relevant line from PROTON_LOG=1 %command% is:

856.043:0031:0032:err:module:import_dll Library RTWorkQ.DLL (which is needed by L"Z:\media\B4-1\SteamLibrary\steamapps\common\TWDSaintsAndSinners\TWD\Binaries\Win64\TWD-Win64-Shipping.exe") not found

Symptoms

The game does not launch as RTWorkQ.DLL is missing.

Reproduction

install the game and try to launch it

EDIT: protondb entry submitted, currently pending

[frostworx]

added a native RTWorkQ.DLL to native, but not enough to get it working.
first relevant line in the log seems to be

307.620:002f:0030:warn:debugstr:OutputDebugStringA "LowLevelFatalError [File:Unknown] [Line: 819] \nRendering thread exception:\r\nFatal error!\r\n\r\nUnhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000000\r\n\r\n0x00007f102754ccf4 ivrcompositor_submit() []\r\n\n"

btw setting windows version to win10, installing xact and installing mf also didn't help
SteamVR Beta 1.10.8

attached log is from a clean wineprefix after installing RTWorkQ.DLL and setting it to native with winecfg

steam-916840.log
.10.8

[frostworx]

wow, must have read that the new proton 5.0-3 fixes this! thank you very much!
I'll buy the game again and report back :)

[frostworx]

I can confirm that this issue is fixed - the game loads very fine. There's another problem though (copy paste from my new, pending protondb entry):

Input:Other
the default knuckles settings were not used. so I got stuck in the main menu. My hands or controllers were not visible as well. I had to load a custom community setting (via SteamVR dashboard) which fixed that for that session. after a 2nd start of the game, the settings were gone, and I wasn't able to load other settings (probably SteamVR dashboard bug, and not a game bug).

Proton 5.0-3 got a special "Fix crash on launch in The Walking Dead: Saints and Sinners" and the game is playable very fine, when the knuckles are detected correcty (see above). I hope the knuckles problem will be fixed as well.

[zaggynl]

Thanks Valve for the fix in 5.0.3, I played for 45 minutes without issue with frostworx's tip about the controller bindings.
Short howto:

Howto:

-Make sure you use Proton 5.0.3: go to the properties of the game, check 

"Force the use of a specific Steam Play compatibility tool" and select Proton 5.0.3.

AMD users only: Make sure you have latest Mesa, I use the Kisak PPA: 

https://launchpad.net/%7Ekisak/+archive/ubuntu/kisak-mesa
Change the game's launch options to: RADV_PERFTEST=aco %command% 

Controller fix (menu does not work):

-go to SteamVR Dash by pressing menu button on Knuckles controller

-Manage controller bindings

-Active controller binding->Default to Custom

-Choose Another

-Search for the "The Walking Dead: Saints & Sinners Active Sprint while  Right Trackpad" custom binding and press View

 -Select this Binding

[mimattr]

the default knuckles settings were not used. so I got stuck in the main menu.

@frostworx @zaggynl Also experiencing the same issue though the Valve Index Controllers appear to be detected (motion control/pointer), it's the buttons/inputs that don't work as expected.

System Information

• GPU: RTX 2060
• Driver/LLVM version: NVIDIA 455.38
• Kernel version: 5.4.0-54-generic
• Link to full system information report as Gist
• Proton version: 5.13-2
• SteamVR version: 1.15.11

I confirm:

• that I have checked whether there are updates for my system available.

steam-916840.zip

[Patola]

Great... Game was working perfectly, now the 21 GB update that adds hours of contant to the game (Aftershocks Update) made the VR hands disappear and I can't interact with the menus to even start the game. Anyone else having this problem?

Tried with both proton 6.3-6 and experimental.

Attaching both proton 6.3-6 log and proton experimental log
steam-916840-proton-experimental.log
steam-916840-proton-6.3-6.log

GPU: AMD RX 6800 XT, Driver/LLVM version: Mesa 21.2.2, kernel: 5.14.7-202-tkg-bmq, SteamVR version: Beta 1.20.1

[Patola]

Ok... Got some progress in the issue, it seems Windows people are having the same issue here. They are solving it by choosing the now official bindings for Valve Index from the workshop, but this binding is not working on Linux! It is not activating, for some reason. I am attaching a screenshot: you can see that I am using the old "Legacy" Valve Index bindings ("Index Controller Legacy Defaults"), and there is also other personal binding at the bottom ("WDSS Patola Sprint trocado") that I can activate instantly by clicking on it. So I can switch back and forth between these two, no problems. But if I click on the official "My TWD-195264 [UE Editor] configuration for Index Controller", nothing happens! Why? It's not lag, I waited for almost 10 minutes and it doesn't activate. If I select "view" and try to overwrite the current bindings, it also does not change anything. This is an issue that I have seen in other games, but not as clearly as now. Why does this happen? Anyone has the explanation? The proton 6.3-6 log of my frustrated attempts to select this binding is attached.
steam-916840.log

[Patola]

Ran the game with WINEDEBUG=+vrclient, maybe it can offer useful information... The log ended up with 213 MB though, so I had to compress it.
steam-916840-WINEDEBUG-+vrclient.zip

[Patola]

Got it to work by going back and forth through overlay menus until the correct name of the game appeared "Walking Dead: Saints & Sinners" instead of "OpenXR Test Instance" or something like that. Then from the community bindings that finally appeared, selected "Liam's Foot Bindings", and now the game works again.