PlayableShow Details
Unknown
Everything works the same as before, almost out of the box. However there are few slowdowns regarding loading the game.
Loading takes longer than on windows. Loss of 20-30 fps in comparison to Windows 10.
Use Incremental saves. and you may only lose less then one turn.
Occasional Segmentation errors.
Random fps drops. dGPU usage drops to close 0% for 1-5s and runs normal afterwards
Occasional Crashes and Segmentation errors.
gamemoderun %command%
Crashes if I tab out during loading screens, otherwise no crashes.
Crashes if running the Native version. Works if I force Proton. The game crashes if I tab out during loading screens, otherwise no crashes.
Crashes and unplayable. Playable in Proton at first, loading save game crashes though, so unplayable overall.
Using native it crashes immediately. I tried Proton 7, 9, and Experimental as well. This gets me to the menu. When I try to load a saved campaign it crashes, which makes playing the game impossible if I can't load a save. CPU utilization is at 48%, and 10 out of 24 cores are pegged at 100% just sitting at the menu. On my Macbook Pro, it runs native and 1 core is at 50%.
It is a native linux game, it is going to work, sadly, oficially does not support fedora, but most of the time it has not been an issue.
After 30 hours of gameplay it crashed twice, once while creating a new campaign, I alt tabbed and it crashed, and the second time was during a siege.
Ran best on Proton 8.0-5 for me
Native version will eventually crash with segment fault and corrupt your save file, better to force proton and use it like that.
segment fault and corrupt your save file
Native didn't launch, but forcing Proton on Windows version works great.
- Native Linux version crashes on startup. Forced proton works.
- Opening Steam overlay was an immediate crash.
The Native version isn't stable, it crashes pretty frequently. With proton GE it has been very stable though not 100%.
DXVK_FRAME_RATE=60 gamemoderun %command%
I feel like turning off overlays (steam overlay, mangohud, discord etc) improved stablity. Might be some issues with the compositor.
Works better with default Proton than native
I was getting about 24 fps on native, flat 60 fps with Proton.
Do not use the native version. It is not able to load saves past the first 6-7 turns, and crashes when you get there (segfault). It also has graphical issues with the unit models on the world map. The proton version is good.
Altough games run on Native there is the bug of saving in campaign. With proton no Issues !!
The game runs great with proton 7.04. I did not have to lower graphics compared to native to still have 60fps. No more annoying segmentation save file bug which occured way to much in native and basically broke your campaign. With proton none of these issues. Also the menu feels way faster with proton compared to native (altough it was a minor issue). Definitly better tu run this game with proton compared to native (due to the corrupt save bug)
v-sync does not work
The game crashes about every 2-3 hours.
The game crashes or hangs indefinitely on the campaign load screen when any kind of mod from the Steam workshop is installed, even though you can officially install and activate them in the game launcher.
Using the Windows version with proton mostly works, but there are some random crashes every few hours.
I played on high settings with acreen resolution of 2560x1600 and about 50-60 FPS most of the time.
gamemoderun %command%
Until yesterday it was working with proton 6.8. Today it did not start. Proton experimental worked perfectly with the "gamemoderun %command%" launch options. I did not try without.
gamemoderun %command%
Native instead sometimes hangs, at least during battles. Other times it becomes so slow to be unplayable. It did not corrupt the save though. Until a week ago, Proton experimental was working without launch options. Now it exits before showing anything. Same for GloriousEggroll 7-29.
gamemoderun %command%
I have now installed Steam's flat pack version.Since then I no longer have segmentation Fault Crashes. Don't forget to free the Steam Library with Flateal. Also no more crashes to desktop with Proton.Performance with Proton is well but native is better.I have now played with Flatpak version about 2 days. Before that I couldn't play an hour without crash
DXVK_ASYNC=1 gamemoderun %command%
Observed what seemed like slight hitching/stuttering while running a stable around 90fps. Someone on the Warhammer 3 page suggested adding DXVK_ASYNC=1 to Steam launch options for that game. Tried adding it for Warhammer 2 and obersved an improvement to the above.
As of time of writing the native version still has the Segmentation Fault issue. As others have said it does not occur on Proton, only on native.
Game minimizes itself if you alt-tab. You can fix it by setting the game to fullscreen.
Once, I could not see settlement names and other parts of the game were missing. I fixed the issue by deleting the prefix.
Multiplayer seems to work fine.
I highly recommend playing on Proton over native if you care to play the game for longer than 20 turns or want to play multiplayer. Native has a very notorious bug, that I have yet to run into on Proton, that will basically brick your save as you'll get the segment fault almost no matter what you do. The game has also not crashed yet due to running out of RAM which happens to me frequently with the native version.
gamemoderun %command%
At some point, the campaign map stutters quite badly. Restarting the game fixes the problem.
The game briefly opens the launcher which immediately crashes. I tried both native and proton 7.0-3.
Game will run natively, but I kept running into the segmentation fault which corrupted my saves. Switched to proton and never had a single issue, runs perfectly and never crashed.
The native version runs very well and fast but crossplay doesn't work... STUPID!
The native version is basically useless. With Proton the game runs very well
Games launches and works well out of the box.
Every so often, sound does cut out and comes back after a couple of seconds.
The game can crash when alt-tabbing, moreso than Windows.
Main menu is 15 FPS, however this does not effect gameplay.
I had more desync issues in modded multiplayer than I did on Windows, however it still only happens every 40-50 turns.
Game runs natively, however I occasionaly get the infamous 'SIGSEGV(11) Segmentation fault' error, right after a battle. What is worse, after a crash there is chance that the last save game gets corrupted and cannot be loaded. So if you start getting this error, make sure to check the Incremental autosaves options, this way you will never lose more than 1 turn of progress.
Tried running the game with latest Proton 7.0.1 and it works flawlessly! Not a single crash and the framerate is much more stable, even on Ultra settings.
Honestly, I've read bug reports on most TW games that have Linux port, and all of them have this stupid crash - I own Shogun 2 and it is there as well. I really cannot comprehend why Feral keeps refusing to fix this error after so many years. (FYI, this error never seems to appear on Intel integrated GPUs, only on Nvidia.)
gamemoderun %command%
Game minimizes when Alt-Tabing, thats why I switched to Fullscreen Window
Unlike the Native version that has a limited multiplayer and sometimes strange bugs, the Proton version runs fine, it also only took a couple of minutes to switch the game from Native to Proton.
For me the SIGSEGV(11): Segmentation fault error continued reoccurring with the Native version, after restarting my PC or just randomly after loosing a battle, that's why I switched to the Proton Version.
From the ~16 hours I played 6 with the Native version and 6 with Proton(and ~4 also half half on my old PC, back than I think I hadn't had issues with the Native version except that the Multiplayer is split) and I will continue using the Proton version of this game Until Feral properly fixes the Native version. Though I manually activated the Feral gamemode for it. Also DX11 runs with more FPS than DX12(Beta) for me.
Runs fine after fixing SIGSEGV(11): Segmentation fault
At first launch on a new device I got a SIGSEGV(11): Segmentation fault error, after starting the game from the launcher.
Following this advise didnt work, but after switching the Steam client to Beta the game worked and continued working after switching back to non-Beta.
Native version crashes
Just crashes with a crash report
Works fine
Aside from the weird mouse inaccuracy from time to time it works pretty well, and I didn't experience a single crash like I did with the Native version.
Mostly unplayable due to black screen. Sometimes it works though.
Something is really fucking strange. As soon as I click in-game, the screen goes black. But sometimes, after serious alt-tabbing, it starts to work. Other users claim there is some sticky alt-key thing. Maybe that is what I'm experiencing. Not so fucking easy to solve though. I have no idea what to do. Native works somewhat better but tends to crash after battles.
Black screen. Se other comment.
Runs out of the box
The game supports linux natively, but i had better experience running it under Proton.
Also i mostly play with a friend who uses Windows exclusively, and as far as i know there is no cross-play support between the native linux client and windows, Proton solves this exact issue.
Runs good
Crashed after a battle.
Ran with Proton to play multiplayer with friend on Windows.
