Unknown
WINE_CPU_TOPOLOGY=16 mangohud %command%
Limiting wine cores is mandatory on high-core systems. Otherwise it works great.
No issues at all
gamemoderun %command%
I couldn't pick a custom pattern for the detailer station. There is no way to select a file or foler. No other issues.
This game is awesome - Its definately worth getting - and if you limit your cpu cores (for high core machines, it runs great.
WINE_CPU_TOPOLOGY=16 game-performance %command%
I run the experimental version, and I have a 32 core CPU. I found that you have to limit the cores available to the game to make it playable. the launch contitions provided are how i managed to make it smooth when running at 3x speed.
High core count CPUs need to limit the number of cores available - and I founn that I had to start at core 0 to get smooth play. Starting from core 32-47 for example caused it to be slow and unplayable - but from 0 to 15, it was smooth.
Works well on default settings.
Installed from Steam, ran with no issues.
Works out of the box!
Crashes to desktop later in game now and then. Could be unrelated to Proton
Awesome game - had to disable SMT on my system for gaming to work properly (not just this game)
With SMT (Hyperthreading enabled) on a threadripper 3970x, the game was unplayable. When i disbaled SMT, the game ran smooth as silk with all 32 cores being used.
All my gaming problems (including on this one) appeared to all stem from having SMT enabled. When it was disabled in the CPU bios settings, the game ran beautifully with zero issues at all. With SMT Enabled - it was laggy, stuttery and unplayable at high speeds. As mentioned, not just this game, but all games, so for me it was a hardware issue.
gamemoderun taskset -c 0-7 %command%
Since update 6, playing at x2 speed causes serious slowdowns after a few minutes.
To avoid this, you need to limit the number of CPU cores the game can use, using the taskset command.
Personally, I've limited it to 8 cores and the problem seems to have been solved.
# Replace "<cores_range>" with the desired value,
# taking into account that CPU cores start at 0.
# For example: "0-1" for two cores, "0-7" for 8 cores.
taskset --cpu-list <cores_range> %command%
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%
game-performance %command%
When 2x fast-forewarding i experienced heavy stutters, normal and fast-foreward works fine
The game is great prior to update 6. Currently at the initlal release of update 6 only smaller maps can be played, 128x128 and large lag big
on 3x speed system slowed down to 6fps. 2x it was at 30-50fps, 1x 60fps which is what i set my framelimit to.
Flawless experience, download and go.
Works out of the box
Ultra Graphics settings were too much, had to go down 2 steps.
Changed to 9.0-2 cause steam default is experimental, but nothing major besides that
first time didnt work, reinstalled and let shaders compile then it worked
Le jeu fonctionnne très bien. Nécessite peut-être du matériel plus puissant que sous windows.
le framerate peut passer sour la barre des 20fps sur des cartes très chargées.
J'ai eu 1 crash (sur la version 6 experimentale)
Perfect
I've been playing on Timberborn's experimental branch for update6 and have no issues at all. Everything, including the modding preview, works great.
Experimental version 6 launches, but won't load. Shows unspecific Unity error.
Running in experimental mode for version 6
Version 5 of Timberborn runs well on my computer but, so far, version 6 doesn't.
Works flawlessly.
If I had another window opened next to it (swaywm), input would not work if put into full screen
If using tiling wm, put onto its own virtual desktop
First start took a while. Getting faster the next start. Did not try modding
gamemoderun mangohud %command%
A perfect experience from start to finish. No 'real' tinkering required (with my setup.) GG.
Perfect
Works absolutely perfect out-of-the-box
The game runs well without adjustments. It does freeze for a moment when loading a save, however.
Game stops responding when loading a save.
I always use proton experimental, never even tried the standard version of Proton
