I tested Dishonored. The game itself works fine, controller is detected and saves can be stored/loaded. I experienced some sluggishness in the menus until shaders were loaded, and I had a small problem with full screen (changing to windowed mode and then full screen again fixed it), but this could be my set up. I'd consider this ready for whitelisting :woman_shrugging:.
EDIT: Updating to mesa-git made it work!
Dishonored is crashing for me, with the following error:

* Arch Linux
* R9 Fury (Mesa 18.1.6)
Works fine. Minor glitches when changing windows (e.g. blacks screen for a few secs). Controller not tested. Performance is not great.
flatpak
OpenGL renderer string: AMD Radeon(TM) HD 8800 Series (PITCAIRN, DRM 3.26.0, 4.18.0, LLVM 6.0.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.6
Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-4 Beta:
Test | Result
-- | --
Singleplayer | Working as expected
Local Co-op | _N/A_
Online Multiplayer | _N/A_
Configuration | ...
-- | --
Input | Steam Controller
Display | 1920x1080^
Fullscreen | Yes
Preset | Medium
VSync | Off
API | DX9
^ Default display resolution 800x600
some extra data if it may help:
gentoo, nvidia gtx 1070, proton 3.7-3:
Test | Result
-- | --
Singleplayer | Working as expected
Local Co-op | N/A
Online Multiplayer | N/A
Configuration | ...
-- | --
Input | Afterglow prismatic (xbox one)
Display | 3840x2160^
Fullscreen | Yes
Preset | high
VSync | Off
API | DX9
^ Default display resolution 800x600
I had a 100% reproducible crash in Dishonored that I managed to find a workaround for. This crash seems to be the same one reported by several people for Dishonored at spcr.netlify.com.
The symptoms may seem unrelated, but I suspect they are in fact not, as the crash workaround is in fact save-related.
Copying the Windows save files fixed it:
$ cp -r /path/to/windows/partition/Program\ Files\ \(x86\)/Steam/userdata/*/205100/* ~/.steam/steam/userdata/*/205100/
I can also confirm that Dishonored works perfectly for me. CentOS 7, 1080Ti, latest 390.xx driver.
Tested all the way up to 5K resolution.
On my setup, switching the desktop from the game and back causes the game to stop rendering.
i3 window manager, arch linux, 4.18.5-zen1-1-zen, nvidia 396.54-5
I had a problem starting the game where it crashed after initial loading but before the main menu. I solved it by enabling Steam Cloud. I also had a set of Cloud saves (on Steam, not locally) from a previous Windows installation. May be related to pvaret's observation.
Manjaro Linux
Ryzen 7 1800X
Vega64 Mesa 8.2.1 with LLVM 6.0.1
Proton 3.7-7 beta
Runs great, 60fps at 4k everything maxxed out. No discernible rendering issues or bugs.
Works well enough for whitelisting on my Debian (Testing). Here is a templated report :
Play button in the Steam client is sufficient.I ran into persistent issues with the game crashing right before the main menus. Disabling/enabling Steam cloud had no effect. When I checked out the files inside ~/.steam/steam/userdata/${STEAM_USERID}/205100/remote/, all of them had a size of 1 (I'm guessing at some point they were corrupted and that was backed up). I didn't have a windows partition to restore from, so I removed all the files and let the game recreate them. Now everything works flawlessly.
Something to note: I couldn't get Dishonored to work back when I was using Windows either. I'm guessing it's for the same reason. I suspect this is the cause of most of the Garbage reviews on protondb.
Update:
After playing for a few hours, everything's pretty much good. Steam Cloud wants to resync the corrupted files when I close and reopen the game, but removing them before the game gets to the menu works fine. Disabling steam cloud or just overwriting the corrupt files with working saves would probably fix it for good.
Works great out of the box.
Dishonored (205100)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3889.
@MetalNeo posted on 2020-05-18T15:34:43:
The credits do not roll at the end of the game.
After more thorough testing, I realized that the video files were not being played because of an ini file setting that I accidentally changed (bForceNoMovies=true). After changing the value to false, I am no longer experiencing playback issues.
That being said, I would now like to recommend this game for whitelisting. I have completed a full playthrough of the base game and the DLCs. Performance was very good/stable and I did not encounter any additional issues that weren't also present in the native Windows version (primarily gameplay-related).
Most helpful comment
Manjaro Linux
Ryzen 7 1800X
Vega64 Mesa 8.2.1 with LLVM 6.0.1
Proton 3.7-7 beta
Runs great, 60fps at 4k everything maxxed out. No discernible rendering issues or bugs.