If BetterExceptionWindow doesn't trigger when a crash occurs, make sure this box is ticked. Or set "CatchNative2Managed": true in config.json in the mod folder.
What's new: Version 7.1.1 Feature: - Completed japanese localisation (Thank you S-Katagiri!) Bugfix: - Bugfix on attach dnspy due to missing module (it was dedicated server module that no longer exists in Modules directory) /!\ Only works for Bannerlord v1.2 (WILL CRASH ON version below it) /!\
I’m having trouble installing Better Exception Window 7.1.1 for Bannerlord 2. I keep getting an error that says, “this library is loaded before ButterLib, it should be the other way around.” When I switch the order, I get the opposite error: “this library is loaded after ButterLib, it should be the other way around.” According to the instructions, BEW should be placed right after Harmony, but I still get the same error no matter what I do.
I also noticed in the mod description that version 7.1.1 is only compatible with Bannerlord v1.2.0. My game is currently at version 1.2.12, so I’m wondering if this is the reason for the issue.
I am using BEW 7.1.1 with Bannerlord 1.2.12 and I suspect the version mismatch is causing these persistent load order errors. Can anyone confirm if BEW 7.1.1 is incompatible with 1.2.12, or is there a workaround I’m missing? I’d appreciate any advice or solutions!
I have a strange bug, the game crashes and the report screen appears normally but none of the buttons on it work, I can resize the screen but none of the buttons do anything when I click. Any tips to fix this?
Unfortunately, this mod doesn't seem to work that well on Linux Mint with Cinnamon desktop UI, I only see a completely white error screen with no text. I only have Vanilla, Harmony, this mod and Serve as a Soldier which crashes.
Most mods work fine with Linux edition. (Not this one because it requires some Windows stuff that's missing on Linux. THere's ways to make them compatible. But that requires knowing a lot about .Net libraries etc and ways to convert them to Linux, or use Wine...)
Generally a crash on Linux is result of the incompatibility between Mod Launcher (Such as Vortex or the new Nexus Mod App) and the proton tricks. To fix that issue do this:
1- Download your mods one by one.
2- At each new mod, deploy the mod configuration to game folder with Vortex or Nexus Mods App. Then Launch game directly from Steam.Not inside the Mod Launcher. The Taleworlds Bannerlord Launcher must be open. You will see an disorganized mod list. Order the mods to your liking. Then launch the game. The Official Taleworlds Launcher will remember your Mod Order. But for just in case, take screenshots of the Mod Order as backup. A game update might reorder the ModList.
3- Test to see if the mod you added is working by playing the game a bit. For example, for Diplomacy Mod, use cheats to quickly find a Kingdom and test the diplomatic options to see if they're working correctly. This bit is very important in both Linux and Windows. Many mods could have hidden incompatibilities or be outdated with new versions of Game. It's better to test each mod one by one and found the bugs at the beginning instead of encountering them inside a Save with 100s of hours already spent in it.
4- If you have other mods to add, to test them go back to step 1.
Here's an example ModList I use in my Linux (Bazzite OS) currently:
Oh ok, good to know. Thanks. Does it like keep track of mods that have called a certain method or something recently? Even if that call did not cause a crash but was somewhere down the line from the actual crash? Just can be frustrating when someone with a hundred mods in their load order says that your mod caused their crash. Most mod users don't take the time to learn programming or try to understand the situation. They see red they start demanding you do something. I suppose if you could share the logic behind the highlighting, it would be nice to be able to explain it better to the mod user. Or even list the determination in the report itself with a disclaimer. Thanks for your work though, it is a very useful tool!
Well, I'm sorry if people keep blaming your mods, some users also contacted me because they thought I could solve their issues. >Does it like keep track of mods that have called a certain method or something recently No, BEW doesn't keep track of crashes if the game is closed. It still tracks how many times "Attempted to continue" button was pressed in current session. Here's the algorithm to detect if mod is the cause, it's not perfect it just scan the callstacks against loaded mod and guess if one of those matches with the callstacks https://github.com/admiralnelson/bannerlord-error-detector/blob/5e34217920e92cbf94de4428a92876a31fa425d5/ErrorWindow.vb#L451C8-L478C20
>Thanks for your work though, it is a very useful tool! You're welcome, I'm glad it helped you.
When I click on atempt to continue I get this message "May have unwanted side effect" I say who cares at this point. This is the only mod I can play a campaign with for over 5 ingame years without the save permanently crashing. Let me finish the campaign my way instead of being locked out of it because of the crashfest. It is worth it to me.
577 comments
-
1
-
2
-
3
- ...
-
25
-
JumpThank you.
Thank you.
Version 7.1.1
Feature:
- Completed japanese localisation (Thank you S-Katagiri!)
Bugfix:
- Bugfix on attach dnspy due to missing module (it was dedicated server module that no longer exists in Modules directory)
/!\ Only works for Bannerlord v1.2 (WILL CRASH ON version below it) /!\
I also noticed in the mod description that version 7.1.1 is only compatible with Bannerlord v1.2.0. My game is currently at version 1.2.12, so I’m wondering if this is the reason for the issue.
I am using BEW 7.1.1 with Bannerlord 1.2.12 and I suspect the version mismatch is causing these persistent load order errors. Can anyone confirm if BEW 7.1.1 is incompatible with 1.2.12, or is there a workaround I’m missing? I’d appreciate any advice or solutions!
Any tips to fix this?
I only have Vanilla, Harmony, this mod and Serve as a Soldier which crashes.
Generally a crash on Linux is result of the incompatibility between Mod Launcher (Such as Vortex or the new Nexus Mod App) and the proton tricks.
To fix that issue do this:
1- Download your mods one by one.
2- At each new mod, deploy the mod configuration to game folder with Vortex or Nexus Mods App. Then Launch game directly from Steam. Not inside the Mod Launcher. The Taleworlds Bannerlord Launcher must be open. You will see an disorganized mod list. Order the mods to your liking. Then launch the game. The Official Taleworlds Launcher will remember your Mod Order. But for just in case, take screenshots of the Mod Order as backup. A game update might reorder the ModList.
3- Test to see if the mod you added is working by playing the game a bit. For example, for Diplomacy Mod, use cheats to quickly find a Kingdom and test the diplomatic options to see if they're working correctly.
This bit is very important in both Linux and Windows. Many mods could have hidden incompatibilities or be outdated with new versions of Game. It's better to test each mod one by one and found the bugs at the beginning instead of encountering them inside a Save with 100s of hours already spent in it.
4- If you have other mods to add, to test them go back to step 1.
Here's an example ModList I use in my Linux (Bazzite OS) currently:
Game Version 1.2.12:
>Does it like keep track of mods that have called a certain method or something recently
No, BEW doesn't keep track of crashes if the game is closed. It still tracks how many times "Attempted to continue" button was pressed in current session.
Here's the algorithm to detect if mod is the cause, it's not perfect it just scan the callstacks against loaded mod and guess if one of those matches with the callstacks
https://github.com/admiralnelson/bannerlord-error-detector/blob/5e34217920e92cbf94de4428a92876a31fa425d5/ErrorWindow.vb#L451C8-L478C20
>Thanks for your work though, it is a very useful tool!
You're welcome, I'm glad it helped you.
-
1
-
2
-
3
- ...
-
25
-
Jump