jamjalopie
Published
Standard issues with xwayland using the incorrect primary monitor resolution - fixed by setting primary monitor with xrandr, then deleting cached settings (config.bin) in compat data dir.
commands:
xrandr
(check output for which monitor you want, in my case XWAYLAND0)
xrandr --output XWAYLAND0 --primary
rm ~/.local/share/Steam/steamapps/compatdata/323190/pfx/drive_c/users/steamuser/AppData/Roaming/11bitstudios/Frostpunk/config.bin
then start game.
Game did not start at all at first, with confusing errors. Seems that pipewire is not supported!
I had to use normal pulseaudio (not pipewire's replacement). Couldn't find anything particular in the logs that caused this, beyond quite a number of lines about discovering various audio channels - more than I expected.
taskset -c 0-1 %command%
Used to work fine without tinkering, but since update 6 I had some huge framedrops at high load (large maps, presumably high population on small maps).
From older discussions on the discord, seems like an issue with some CPUs with many cores. Dev recommended limiting to 8, but I found limiting the game to 2 cores was required. Depending on CPU, feel free to tweak the numbers in the taskset command - cores start from 0 and you can provide ranges or individual cores comma delimited.
taskset -c 0-1 %command%
