Dishonored®: Death of the Outsider (614570)

[tr37ion]

Compatibility Report

• Name of the game with compatibility issues: Dishonored®: Death of the Outsider
• Steam AppID of the game: 614570

System Information

• GPU: GTX1070
• Driver/LLVM version: Nvidia 410.57
• Kernel version: 4.18.10-arch1-1-ARCH
• Proton version: 3.7-6
• KDE Plasma 5.13.5

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.

Proton Log

I add the Proton log of the game running just fine. Maybe it helps with debugging Dishonored 2:

Gist - Proton Log

Symptoms

1.First start it crashed immediately with black screen.
2. Start was just fine. No issues staring the game. Really great!

I set GFX to ultra and turned off Motion Blur (not bc. of issues, just bc. I don't like it). Started playing the campaign. First some stuttering, I suggest, it's because of compiling shaders or caching textures. when entering new scene.

Then game performance is great. I have the impression it is even smoother as the main game Dishonored 2 was with DXVK 0.7 and Wine-Staging.

Maybe it's worth copying over this Prefix to Dishonored 2, too and try if that helps running it, too.

[liberodark]

Work for me but slow fps on 1050Ti !

[zvbarev]

Always crash during moving carriage from ship to other disctrict. The problem in first mission was cured by deleting shadercache for game. In second mission still can't resolve.

[kisak-valve]

Hello @Sebastian1978, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the crash, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[zvbarev]

Hello @kisak-valve, see error log
steam-614570.log

[zvbarev]

Also the same problem as with Dishonered 2. Sometimes after loading new locations I see game items on the white screen. After that I always clear shadercache folder of game and it helps.

It seems background textures don't load.

[kisak-valve]

Looks like DXVK is failing to allocate memory, then the game falls over with a null pointer: wine: Unhandled page fault on read access to 0x00000000 at address 0x6a35c805 (thread 0030), starting debugger...

Can you check if adding WINEDLLOVERRIDES="dxgi=n" %command% to the game's launch options has an effect? I suspect Proton 4.11-9 is trying to use the Ivybridge chipset instead of the GT 735M in a similar way to the issue being tracked at #3215.

[zvbarev]

Here is my new parameters: WINEDLLOVERRIDES="dxgi=n" PROTON_LOG=1 PROTON_NO_ESYNC=1 %command% +com_showLoadingScreen 0

Still crash... See new log
steam-614570.log

[zvbarev]

Hi @kisak-valve I tried to pass the same area in Dishonored DOA in Windows using the save file. I had crashes until I entered in Nvidia 3D settings and changed some parameters.

I changed MAXIMUM PRE-RENDERED FRAMES to 1. Also setup default GPU to Nvidia. Additionally Streaming optimisation to Enabled, Maximum energy efficiency mode, OpenGL rendering GP to Nvidia.

I assume the main parameters were MAXIMUM PRE-RENDERED FRAMES and default GPU = Nvidia. Is it possible to tune MAXIMUM PRE-RENDERED FRAMES in Proton?

[zvbarev]

Also I went to new area in Windows version DOA and made new save file. After that I tried to load this save file in Linux and got crash again. See my log
steam-614570.log

[zvbarev]

Hi @kisak-valve I solved the problem of loading new area using environment variable __GL_MaxFramesAllowed=1. It seems WINEDLLOVERRIDES="dxgi=n" is not needed.
See my param string for launch game:
__GL_MaxFramesAllowed=1 DXVK_HUD=fps PROTON_LOG=1 PROTON_NO_ESYNC=1 %command% +com_showLoadingScreen 0 -high +cvaradd r_skipfog1

The problem with not loading background textures still exists.
UPD: I had only 1 successful launch with these parameters. After that I got only crashes((

[melo0187]

More than 2 years later this game doesn't even launch when using Proton (tested 7.0.6, experimental and GE-7-48 using EGS version).
Any ideas on how to look into this?