Search results for query: *

Gave it a quick spin and DNSpy gave me some kind of error in Sandbox.MapScene.GetNavigationMeshCenterPosition and crashed straight to desktop.

The save is quite far along, likely some bug from an earlier version that 1.8.1 crashes on. If you're determined to try and finish that run you might want to try downgrading to 1.7.2 to play it. Just be aware that if you use version 1.7.2, steam will leave behind a few files that will cause it to crash on launch, so you'll have to manually delete any instances of language_data.xml

This still sounds a lot like a OneDrive issue. It's possible for it to have replaced your engine_config file immediately after you made the change, so can you double-check that the line you changed hasn't changed back? Can you tell us where you did end up finding the file? If it includes your user name or anything potentially sensitive, you censor that portion, e.g., C:\Users\<my name>\

Hm, do you close steam before trying to launch directly? Trying one particular executable or all of them?

Does it still crash when launching from all the executables mentioned earlier directly? Unfortunately I think this one will need developer attention for a proper fix, but so far all other threads with this problem have been able to work around it that way.

Right click steam tray icon -> Library -> right-click Mount & Blade II: Bannerlord -> properties -> "Local Files" tab on the left -> Verify integrity of game files

It's a fairly large game and will take a good 5+ minutes just to check, but fortunately since that one folder is less than 1GB it won't take long to redownload the mission portion.

I've seen this error a few times but unfortunately never seen a surefire solution. One user was able to fix it by deleting the contents of <installation directory>\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client and then verifying on steam to re-acquire the deleted files. You can also try running Windows Update and making sure that Microsoft OneDrive hasn't been signed out or is currently having issues with syncing.

If none of that works, most users with this issue seem to end up working around it by launching the game directly without using the steam shortcuts. Inside <installation directory>\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client\ you should try running the executables named "TaleWorlds.MountAndBlade.Launcher.exe", "Launcher.Native.exe", "Bannerlord.Native.exe", and "Bannerlord.exe" to see if any of them can launch and play the game without crashing.

Oh dear. When you can see the file, right-click and select open. It should bring up some kind of text editor like Notepad. You should be able to right-click inside the window and select "select all" and then "copy". You should then be able to paste this text in the big window on PasteBin. At the bottom of pastebin a button should say "Create new paste" and after clicking on that, copy the address from the address bar and paste that here.

I'm not sure what you mean. How are you pasting what exactly? What is opening a new tab and where?

Can you grab the files named launcher_log_(numbers).txt and rgl_log_(numbers).txt located in C:\ProgramData\Mount and Blade II Bannerlord\logs and put them into a PasteBin to link here?

If this is indeed through steam, you can right-click on the name in library, select Properties, then the Betas tab to select the version to use. Selecting None just keeps it up to date with whatever the latest stable version is.

Often times that can be cleared up by clearing steam's download cache. Right click steam -> settings -> downloads -> clear download cache
You may also want to check your OneDrive and make sure it isn't signed out or having errors.

1.5.1 is a rather old version. If you're determined to run it and this is through steam, you may have extra files left in the installation folder that the older version crashes while trying to load. I know that at least for 1.7.x users have to delete language_data.xml to not crash on launch. If the version number isn't a typo, you might want to just update to 1.8.1 and avoid the headache.

No matter where the game itself is installed, it will try to write configs to your user folder, which Windows by default will have on C:
If it's not there it should definitely be creating a new one. You may want to paste %USERPROFILE%\Documents\Mount and Blade II Bannerlord\Configs into an explorer window address bar in order to go there directly in case you were checking a different user's directory.

If it's certainly not present, you may want to check OneDrive to see if you got signed out or are it's having syncing issues, as problems with OneDrive can mess with user folder permissions, but normally that kind of issue would cause the game to simply crash on launch.

You should be able to find it in C:\Users\ (your user name) \Documents\Mount and Blade II Bannerlord\Configs

Can you double-check engine_config.txt around line 14 for "cheat_mode = (0 or 1)"? This is the normal behavior if cheats are enabled.

Sorry that BEW didn't help any. I haven't seen the error
The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at TaleWorlds.MountAndBlade.Launcher.Library.LauncherModsDLLManager.GetDLLVerifyReport(String[] dlls)
in any other reports. If you uninstall BEW/Harmony, is this error still present in your launcher_log?

Can you pastebin the rgl_log and launcher_log for this new crash? Also I see on the workshop page for BEW that the System.IO.DirectoryNotFoundException thing should be fixed now, can give the workshop versions another try.

Can you elaborate some more on what the problem is? Walk us through what you're doing in the game, and what's happening that's not expected.

Never seen that one before, unfortunately I'm not familiar with problems related to steam workshop and that error message looks like a new unrelated error that many workshop mod users get. Should be more reliable to unsubscribe from the workshop version and install the nexus versions manually.

There's a workaround mod for that one, OnGovernorChanged Workaround has an optional file below the main files called OnHeroHealedWhileWaitingWorkaround