Boet Fighter (App ID 1108350)

Compatibility Report

• Name of the game with compatibility issues: Boet Fighter
• Steam AppID of the game: 1108350

System Information

• GPU: GTX 760
• Driver/LLVM version: 435.21
• Kernel version: 4.15
• Link to full system information report as Gist: https://gist.github.com/lengau/08a3d19261184ba33cdfd68b06ad13c0
• Proton version: 4.2-9, 4.11-7, 3.16

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.

steam-1108350.log

Symptoms

1. Cut scenes don't work. This seems to be a symptom of #1464, as the media files fit this. The first relevant error message can be found on line 3957 of the log.
2. At the point where you meet "kim", either that cutscene freezes the game or something else happens. (This happens after the second scene. First scene is in the night club, second in the pool hall.) You can see issues with it loading KIM.mp4 at line 19403 of the error log, followed by repeated "Has reached kim1" and "has reached kim2" messages.
3. The menu screen only partially displays when using dxvk
4. On Proton 4.11 with DXVK, the first time a punch happens (either if I dock an oke or if he docks me) the game freezes. xorg, plasmashell, and the game all start using massive amounts of resources and makes the X session basically unusable (frozen - mouse can still move, but no mouse events occur). Ctrl+Alt+Escape to open the window killer doesn't work, but SIGTERM to Boet Fighter from an SSH session restores my graphical session to normal. Log attached:
   proton_4.11_dxvk.log

Workarounds

Menu screen looks better (though not the same as in Windows) when using Wine's Direct3D implementation.

Without PROTON_USE_WINED3D:

Log:
PROTON_DXVK_MENU.log

With PROTON_USE_WINED3D=1:

Log:
PROTON_WINED3D_MENU.log

Failed workarounds:

• PROTON_NO_D3D11 and PROTON_NO_D3D10 make the game fail as it's only built with Direct3D 11 support.

Reproduction

Menu graphical issues:

Open the game with default settings (no PROTON_USE_WINED3D) in any version of Proton

Freeze with systemwide consequences upon punch:

NOTE: The punch needs to actually hit somebody. Punching the air does not count.

1. Open the game in Proton 4.11 with DXVK (make sure PROTON_USE_WINED3D=0 or similar).
2. Choose Single Player
3. Choose New Game
4. Press spacebar to skip the opening cut scene
5. Wait for an enemy to appear and punch it.

Cutscenes don't occur

1. Open the game with any version of Proton, seemingly with any settings (default settings are fine, also works with PROTON_USE_WINED3D)
2. Choose Single Player
3. Choose new game
4. Note that the opening cutscene is skippable, but doesn't actually play.

Stops working upon meeting Kim

Play through the first two levels (nightclub and pool hall). It gets stuck (indefinitely?) after the pool hall.

Start by reproducing the reported menu, cutscene, Kim, and punch failures with the listed Proton versions, then inspect steam-1108350.log around lines 3957 and 19403 and proton_4.11_dxvk.log. Compare DXVK with PROTON_USE_WINED3D=1 and use the attached logs to verify each reported symptom and its resolution.