Blood Bowl 2

Blood Bowl 2 proton open 2 matching

• jwakely · 2019-03-29 · Blood Bowl 2
  Oh, except after switching away from the game with Alt-Tab and then back again, you need to press Alt once to re-enable the keyboard. I've seen a few comments saying that for different games on protondb.com. It's not a b...
• jwakely · 2019-03-29 · Blood Bowl 2
  @kisak-valve yeah that works, thanks. That's a perfectly good solution as far as I'm concerned, I can play BB2 without needing to run `steam` from a terminal and without worrying about disks filling up. Everything else w...
• kisak-valvemaintainer · 2019-03-28 · Blood Bowl 2
  Hello @jwakely, it may be worth trying `> /dev/null` (or `> /dev/null 2>&1` to include stderr) in the game's launch options. This always has to be the last thing in the launch options.
• jwakely · 2019-03-28 · Blood Bowl 2
  Could that redirecting be done on a game-by-game basis, e.g. via the launch options, so that output is only discarded for games known to spew too much?
• aeikum · 2019-03-28 · Blood Bowl 2
  Interesting. We could redirect stdout to /dev/null by default. It's been brought up before (Steam also logs games' stdout to /tmp/dumps/, which will grow just like your xsession file).
• jwakely · 2019-03-27 · Blood Bowl 2
  It's the Xorg server that writes it there, because that's what the file is for: capturing the output of X Windows processes. If I launch `steam` from an xterm then the output goes to that terminal, but that's not how I l...
• aeikum · 2019-03-27 · Blood Bowl 2
  Interesting. The game continually dumps that via OutputDebugString, so that's why your Steam log grows so fast. I have no idea how that message makes it into .xsession-errors, though... that doesn't happen on my Arch Lin...
• jwakely · 2019-03-25 · Blood Bowl 2
  ~~As a workaround, I have to ` rm ~/.xsession-errors` and reboot before the file fills my disk again.~~ The simplest workaround is to Exit t he Steam client and restart it from a terminal window, redirecting the output t...