Compatibility Report

Works for me.

• Nvidia 1070, driver 440.66.08
• Ryzen 5 3600
• Archlinux, kernel 5.6.11
• Proton 5.0-7

Game runs for me with Proton 5.13-6.
But intro does not work and neither ingame VHS-Videos display on ingame TV-Screen.
And performance is not such as good than windows.
Gist

Runs mostly smoothly, after a couple tweaks:

• It needs media foundation dlls to play intro and in-game movies
• Mouse motion is jerky (stutter), Fixed by manually disabling mouse smoothing in Breathedge WindowsNoEditor/Input.ini (couldn't find in-game setting) (Tested with a mouse at 500Hz polling rate, tested 1000dpi to 3000dpi)
• (Got a couple freeze-and-crash but I did not save crash log: when alt-tabing (i3-wm), and maybe because of steam update popup... GPU memory usage was very high, looked like out of gpu memory crashes. Did not play on Windows to compare.)

(Proton 6.3-1, Archlinux Linux kernel 5.11, nvidia 460.67)

Hangs with TV test pattern animation after "tell him" without media foundation, hangs with black screen with media foundation installed.

Proton 6.3-2
nvidia 460.67
Ubuntu 20.04.2 LTS
Linux 5.4.0-70-generic

Works on former version of Proton.

Proton 5.13-6
nvidia 460.67
Ubuntu 20.04.2 LTS
Linux 5.4.0-70-generic

Hello @taisph, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the test pattern hang, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

What's the correct way to reset a game/proton prefix that was custom patched to make media foundation requirements work? Is it necessary to remove and reinstall the game?

To reset your Proton prefix for a game, browse to ~/.local/share/Steam/steamapps/compatdata/ and rename (or delete) the folder named after the game AppID, in Breathedge case it is 738520. Be careful when doing so, if the game doesn't save the gamesave to Steam cloud, the gamesave file is usually located within the prefix, (I still didn't play this game, it is currently installing so I don't know, hence the recommendation to rename the prefix folder instead of deleting it, for safe keeping, just in case).

It is not necessary to reinstall the game when resetting the Proton prefix for a game.

This game locks up after starting, shortly after the interactive torture session, when the character is explaining the situation. Works the same with regular Proton-7.0-6, 44, GE-Proton7-44 or Proton-7.0-6 with mfplat libraries installed. Attached is the proton log when the animation hangs and a screenshot of the frame where it hangs.
steam-738520.log

When the hang occurs, one process stays at 100% CPU the whole time in the call (caught by strace):
futex(0x7fc9d3e267a4, FUTEX_WAIT_PRIVATE, 12, NULL

Using PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 doesn't change anything

Does it crash if you (all of them):

• delete the prefix (or rename it, to keep the old files just in case, the savegame for example)
• use standard 7.0 Proton not experimental or beta
• use standard kernel instead of TKG patched one
• do not use ANY startup option in the game properties in Steam

Prior to testing I deleted the prefix and set it to standard 7.0-6 proton with no startup options as I said. I've only added PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% in a later attempt exactly to offset the fsync-patched kernel I have (although all kernels higher than 5.16 already have futex_waitv patched in, so I don't think this would be the cause). The only remaining action for me seems to try and use a vanilla kernel, but I don't think that would make a difference not only because I used the settings to turn off fsync but also because there are many reports on protondb describing that exact hang I have with different versions of the vanilla kernel.

I don't know I can play well I just tested and loaded different saves too.

The rest of the game seems to work well for me, the only part where I detected the hang was in that particular moment at the starting cinematics. What is your hardware and distro?

OK if I start a new game, even on fresh prefix I also can reproduce the hang. If I start a new game and tick the skip intro box, it loads properly to the game without having the 'torture' intro.

For the record, I also tried the "legally problematic" workaround and it did not work.