protonscr

Into the Breach rendering stalls if vertically truncated

protonopen appid 590380
ValveSoftware/Proton#2108 · opened 2018-12-19 by Tele42 · updated 2020-04-20 · 5 comments · github · game page · search this game
TTele42 2018-12-19 github

Compatibility Report

  • Name of the game with compatibility issues: Into The Breach
  • Steam AppID of the game: 590380

System Information

  • GPU: Ivybridge / Radeon HD 6310
  • Driver/LLVM version: Mesa 18.2.7/6.0.1
  • Kernel version: 4.19.10 (Ivybridge) and 4.14.82 (Evergreen)
  • Link to full system information report as Gist:
  • Proton version: 3.7-8, 3.16-4, 3.16-5 Beta

I confirm:

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

Symptoms

When running Into The Breach on Gentoo + Mate (software compositing enabled), the game renders fine on the test boxes here that have discrete vram, but stalls when on an integrated graphics system. I can get the game to render a couple more frames every time I alt-tab in and out of the game. If I disable software compositing in Mate's settings, the game no longer refreshes the rendered frame on alt-tab.

The rest of the DE and other applications remain responsive throughout testing and the game maxes out one cpu core. Nothing of real interest in the proton log spew.

I've been seeing this behavior since the initial release of Proton.

Reproduction

Run Into The Breach on Mate (1.18) and an integrated graphics system.

UUnaccounted4 2018-12-30 github

I have a similar issue with my Ivy Bridge Thinkpad X230. Accoring to the terminal output, DXVK is crashing when attempting to call on unsupported Vulkan extensions in the Ivy Bridge driver. Though, in your case, the issue seems to be the AMD R600 driver which doesn't support Vulkan at all.

For example in my Thinkpad X240 which has a Haswell processor, the game works fine.

TTele42 2018-12-30 github

There's no references to DXVK in the Proton log at all and the game's requirements say it's an OpenGL 2.1 game. Are you getting confused by https://github.com/ValveSoftware/steam-for-linux/issues/5423?

UUnaccounted4 2018-12-30 github

Right you are! I have no idea, then.

TTele42 2019-03-30 github

I think I have a better hypothesis on what's going on here. On the three affected systems I have here, they all have 1366x768 (or lower) screens. I didn't notice it before, but the game engine wants to render to 1280x720, but it's getting cut off at the bottom. The combination of top/bottom DE bars + title bar + minor window chrome means that the game isn't getting the full height it wants and MATE is restricting the game's window to the visible area.

I was able to mash alt-tab until I could get to the options and set fullscreen, then the game started behaving.

It would be nice to know what the expected behavior is when the game is given a window smaller than it requested.

Kkisak-valve maintainer 2020-04-20 github

Tracking note: This game was removed from the whitelist today, and the game is now being unofficially tracked at #204, but the issue described here does not read like a game-specific issue, so I'm just dropping the Game Compatibility label so the issue report falls into the generic, unsorted issue set.

Upstream links