Darth Banana
Published
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_D9VK=1 gamemoderun %command%
Alt-Tabbing crashes the game, at least in Wayland, though the fix is simple. Just run in windowed mode and fullscreen via your display manger. It works flawlessly under Plasma 5.27.
Towards the end of the game, especially in Awakening there are a few stutters sometimes, especially if there are a lot of effects running on screen (fire storm, dragon taking off animation, etc.).
The game has a memory leak of sorts and it relates to how many areas you transition to. The loading will become slower between areas until it will eventually crash. Not sure if it's related to the graphical improvement mods that I installed though it's not a huge issue, since it would occur every few hours and if you notice that loading between the areas takes ridiculously long you can just restart the game and the problem is gone.
I managed to finish the main game and all DLCs with no major issue. Modding is a bit harder though, I would suggest setting up a Wine prefix (can also be done via Lutris), different from the main game, where DAO Mod Manager can run since any tricks installed in a Proton prefix will prevent the game from launching.
The game runs a bit slower than on a Windows VFIO with the same GPU
Sometimes it crashes in 5 minutes, sometimes in 2h.
Starting from 1.5.4 the launcher would crash. Need to do a symlink to skip the launcher:
mv TaleWorlds.MountAndBlade.Launcher.exe TaleWorlds.MountAndBlade.Launcher.exe.backup
ln -s Bannerlord.Native.exe TaleWorlds.MountAndBlade.Launcher.exe
Would recommend a kernel that has Fsync patches for better performance. A good precompiled one that's easy to install for Debian/Ubuntu based distros that I'm partial to is Xanmod.
Proton-5.21-GE-1 provides a bit better performance and anecdotally less frequent crashes than Proton-5.9-GE-8-ST.
gamemoderun %command%
At 1st I had problems playing the game with either Proton9.0, GE or Experimental. I could only see a red screen with FIXME: WMP. After adding the suggested: PROTON_USE_WINED3D=1 WINEDLLOVERRIDES="dinput8.dll=n,b" %command" the red screen was still there and sometimes it would load the game but with no mouse.
I thought that maybe it's a driver issue so I updated Mesa to the latest stable but this did not produce any change.
The last thing I tried was switching from Wayland to X and after that everything worked as expected with any version of Proton and without any launch options. I guess there are some integrations with Wayland missing upstream in either Proton or Wine or maybe there's a bug with Wayland and KDE/Plasma 5.
I highly recommend using Feral Gamemode. Without it my processor would go into a very low power state while gaming and it made the game feel very framey. I'm guessing such an old game doesn't feel like a huge workload for my processor.
