However I'm getting fairly frequent hangs on loading screens with this reported in steam's terminal:Things I've done so far to run game on ArchLinux:
1-) install linux-fsync from AUR with this patch applied so I can use FUTEX_WAIT_MULTIPLE patch on linux 5.6.3
2-) install proton-ge-custom-bin from AUR (I am too lazy to wait until build from source finishes)
3-) cd into Bannerlord install direcotry in steam library and create symlinks forBannerlord.exe
andBannerlord_BE.exe
Bash:cd ~/.steam/steam/steamapps/common/Mount\ \&\ Blade\ II\ Bannerlord/bin/Win64_Shipping_Client ln -s Bannerlord.exe ManagedStarter.exe ln -s Bannerlord_BE.exe ManagedStarter_BE.exe
4-) run game from steam as usual and let steam install its things.
So far it seems running OK. Only drawback that I observed is saving game takes a few seconds longer than the setup with dotnet48 and no fsync patch in kernel. But I am pretty happy bit a few seconds longer save time when I don't have frequent crashes.
CPU Brand: AMD Ryzen 7 1800X 8c 16t @ 3850MHz
RAM: 32111 Mb
Kernel Version: 5.6.3-arch1-1-fsync
Driver: NVIDIA GeForce GTX 1080
Driver Version: 4.6.0 NVIDIA 440.82
Number of Monitors: 2
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 3840 x 108
Storage: Samsung 960 EVO 1TB NVMe M.2 SSD
P.S. Game is behaving well with multiple monitors so far, but I didn't tried to play it on secondary monitor yet.
P.S.2. Also I don't know if it matters but, I am using e1.1.0 from beta branch of Bannerlord
update: experinced first freeze/crash after about 6 hours of continuous gameplay
* Assertion: should not be reached at /vagrant/mono/mono/utils/mono-threads.c:1066
I've gotten Bannerlord working almost perfectly on Manjaro following the same process as Silverlight here:
However I'm getting fairly frequent hangs on loading screens with this reported in steam's terminal:
Code:* Assertion: should not be reached at /vagrant/mono/mono/utils/mono-threads.c:1066
Can you post your system specs and driver versions, as it would be helpful to diagnose your problem. I noticed you are running Ubuntu, which often has quite outdated versions of Mesa drivers and such. I would recommend upgrading to the newest versions, there should be ppas for it that you can find.Hi, i tried all the above and none worked. So i guess people might have done something they found trivial and maybe forgot to mention it.
+I tried the protonfix combo :
proton GE5.1 + vcrun2019 + dotnetcore + dotnet48
=> Game crashes, impossible to go further than training grounds
+Then i tried the fsync kernel, i folowed Valve thread for my ubuntu system
so, fsync + protong ge .
=> Game crashes, impossible to reach even the training ground ...
So i wonder, what you guys exactly did to have it running for an hour ?
Can you post your system specs and driver versions, as it would be helpful to diagnose your problem. I noticed you are running Ubuntu, which often has quite outdated versions of Mesa drivers and such. I would recommend upgrading to the newest versions, there should be ppas for it that you can find.
Hi, i tried all the above and none worked. So i guess people might have done something they found trivial and maybe forgot to mention it.
+I tried the protonfix combo :
proton GE5.1 + vcrun2019 + dotnetcore + dotnet48
=> Game crashes, impossible to go further than training grounds
+Then i tried the fsync kernel, i folowed Valve thread for my ubuntu system
so, fsync + protong ge .
=> Game crashes, impossible to reach even the training ground ...
So i wonder, what you guys exactly did to have it running for an hour ?
protontricks 261550 annihilate
in order to try running game in a clean prefix.PROTON_LOG=1
will create a file named steam-261550.log
in your user's home directory, and that file will contain proton's console logs. (you can simply right click game on steam library -> properties -> "Set launch Options" then write PROTON_LOG=1 %command%
to box then click "ok" button to save)Is there a chance that you forgot to add symlinks? ( ManagedStarter.exe -> Bannerlord.exe and ManagedStarter_BE.exe -> Bannerlord_BE.exe )
also make sure that you runprotontricks 261550 annihilate
in order to try running game in a clean prefix.
Also running the game withPROTON_LOG=1
will create a file namedsteam-261550.log
in your user's home directory, and that file will contain proton's console logs. (you can simply right click game on steam library -> properties -> "Set launch Options" then writePROTON_LOG=1 %command%
to box then click "ok" button to save)
/singleplayer _MODULES_*Native*SandBoxCore*CustomBattle*Sandbox*StoryMode*DistinguishedService*First Person View Tweak*FightingTogetherRelationship*KillBanditsRaiseRelations*HideoutSendTroops*_MODULES_
Sorry for necro, but does it mean there is no way to start another mod than vanilla, when playing on Linux?sup guys,
as of the 1.5.6 beta (and for a little while now i'm guessing) the launcher doesn't work on linux, meaning you can't mod the game
has anyone figured out a workaround to this? a way to get the launcher working, or manual mod installation? thanks in advance.
edit: found out how you're able to do it. you gotta go into bannerlord's config in steam, and add the below line into launch paramaters. this is just what i have, replace the mods with your mods. everything after "storymode" and prior to "_MODULES_" are mods. none of them really work however, seems like i just crash after a few seconds. oh well.
Code:/singleplayer _MODULES_*Native*SandBoxCore*CustomBattle*Sandbox*StoryMode*DistinguishedService*First Person View Tweak*FightingTogetherRelationship*KillBanditsRaiseRelations*HideoutSendTroops*_MODULES_
My game uses anti-cheat, which currently doesn’t work with Proton - how do I get around this for Steam Deck?
We’re working with BattlEye and EAC to get support for Proton ahead of launch.