So I've already posted something along the lines of this under another thread, about crashing when you hit Done on a siege. It is also a known issue that after a siege sometimes the game crashes after you hit Done, I have done a lot of research on this, and will be reporting all my findings in this post. If anyone is willing to help out or has more information please do make sure to post it and I will also put it in this post.
Since I went on the 1.1.0 beta of 4/13/2020 I had numerous crashes when finishing a battle, both in auto-resolve as well as manually fighting the enemy. At first I thought it was just a bug of the new 1.1.0 beta, have NOT confirmed if this is also the case in the 1.0.11 version. I can however confirm a crash happens when the following criteria are met.
- Any fight, be it with another lord, bandits, peasants, siege, etc.
- You start with >1000 troops on your side (Would require some testing to see if it also happens if the enemy has >1000 troops)
- After the fight is done, you still have 1000 alive men (Don't know if its required for them to be on the battlefield, my performance is set to allow 1000 men at once, will be testing in a minute if it happens when you have this set to a lower amount)
- Click done
The game crashes.
I have noticed that every time it does crash, when I hit done, it displays 1000 under the 'remaining troops' on my side. I have run tests about 5 or 6 times, both fighting <1000 and >1000, both in auto-resolve and manual (manual I just used cheats to do CTRL + ALT + F4 to auto-finish it to speed it up). It crashed with 100% consistency if I had 1000 remaining men, and it didn't crash once when I had less than 1000.
Test 1:
- >1000 men
- Under performance tab, max amount units set to 901. (For the life of me I can't get it on 900 exactly)
Will report back after this test is done.
Result:
Auto resolve: Auto-resolve resulted in a crash. Game displayed 1214 remaining friendly troops. -- Tested twice
Manual: Manual resulted in a crash. Game displayed 901 remaining friendly troops. -- Tested twice
It looks like it is NOT the 'active troops' that causes the crash. I'm thinking it MAY be just your entire army having >1000 men after a battle. Maybe exactly 1000 will also crash, that'll be the next test.
Test 2:
- Exactly 1000 men
- Under performance tab, max amount units 1000. (Except last test where it will be 901 again)
Results:
Auto resolve: Auto-resolve resulted in a crash. Game displayed 932 remaining friendly troops. -- Tested twice
Manual: Manual resulted in a crash. Game displayed 1000 remaining friendly troops -- Tested once
Manual V2: Same setup, 901 as max units. Resulted in a crash. 901 remaining troops -- Tested once
So far, I have confirmed the game DOES crash if you have 1000 OR MORE units in your party at the START of the battle (troops dieing in combat does not counteract this)
Quick break:
While setting up the conditions for test 4: For some reason, when I have 1000 men in army, I donate a SINGLE unit to a garrison, and I have 983 in my army. This may have something to do with the crashing. Will be recruiting men up to 1000 again to test this.
Test 3:
- Bring men back up to 1000 from glitched 983.
- Under performance tab, max amount units 1000.
Results:
Auto-resolve: Auto resolve resulted in a crash. 978 remaining troops -- Tested twice
Manual; Manual resulted in a crash, 999 remaining troops -- Tested once
Manual: Manual resulted in a crash. 1000 remaining troops (shot one in the back of the head to see if ending with <1000 worked) -- Tested once
Test 4:
- Exactly 999 men
- Under Performance tab, max amount units 1000.
Results:
Auto-resolve: Auto resolve resulted in a crash. 928 remaining troops -- Tested twice
Manual: Manual resulted in a crash. 999 remaining troops -- Tested twice
I am confused, I was sure it had something to do with having over 1000 men in some way shape or form. Next test will be with less men until I find the tipping point.
Test 5:
- Exactly 900 men
- Under performance tab, max amount units 1000
Auto-resolve: Crashed. 809 remaining men. -- Tested twice
Manual: Crashed. 900 remaining men. -- Tested twice
So we go lower.
Test 6:
- Exactly 452 men (can't be arsed to go to 500 exactly)
- Under performance tab, max amount units 1000
Auto-resolve: DID NOT CRASH!!!!!!!!!! FINALLY
Manual: DID NOT CRASH!!!!!!!!!! FINALLY
The tipping point is somewhere between 452 and 900. **** me, this is gonna take a long ass time...
Test 7, Hypermode:
- Will be increasing/decreasing the amount of troops I bring into battle depending on if it crashes or does not to find the tipping point.
- Max units set to 1000.
- Will only be testing manual seen as this is more likely to crash (have had only 1 crash with auto-resolve, about 7 with manual over my 89 hours of playtime)
Another quick break:
It MAY be having >1000 men available at the start of a battle in general. (Adding up enemy and player). Will be documenting the total amount of units too.
452: Safe. 35 (452 + 35 == 487)
702: Crash. 745 (702+745 == 1447)
605: Crash. 745 (605+745 == 1350)
243: Safe. 758 (243 + 758 == 1001)
-- END DAY 1
God ****ing damnit. It's 1:29AM. I do not have the time to tinker around with these numbers at this time. I probably will be returning to this tomorrow. You can see the available numbers I have. I do not yet know which is causing the crashing. Whether it's the TOTAL amount of troops or FRIENDLY troops. Would require further testing (example take 702 men into a fight with 50 bandits and see if it crashes).
-- DAY 2
383: Safe. 760 (383+760 = 1143)
405: Safe 762 (405 + 762 = 1167)
Gonna need to start increasing these numbers a bit faster.
467: Safe. 760 (467 + 760 = 1127)
557: Crash. 769 (557 + 769 = 1326)
Somewhere between 1127 & 1326.
547: Crash. 769 (1336)
537: Crash. 769 (1326)
527: Crash. 769 (1316)
517: Crash. 769 (1306)
507: Crash. 769 (1296)
497: Crash. 769 (1286)
477: Crash. 769 (1266)
450: Crash. 769 (1219) -- maybe tipping point is 1200?
431: Crash. 769 (1200)
430: Crash. 769 (1199) -- **** SAKE
I give up. I don't have the patience to carry on with this. I hope I have documented enough to help the developers find the cause, although it's unlikely they'll actually read it.
If anyone would be willing to help out with this, a few things:
- Performance tab, 1000 max units (don't know if it will change anything, could try putting this to different values as well)
- Enable cheat mode (https://www.pcgamer.com/mount-blade-2-bannerlord-cheats/) and using CTRL + ALT + F4 you can knock out all enemies to make the battles go by instantly (instead of having to sit there fighting the enemy for 5 minutes)
- Please note any and all findings -- together, we are able to figure this out and save a lot of time for the developers!
Thank you.
Updating this thread as I do my research. Make sure to refresh once every few minutes, likely to have changed/added something.
Since I went on the 1.1.0 beta of 4/13/2020 I had numerous crashes when finishing a battle, both in auto-resolve as well as manually fighting the enemy. At first I thought it was just a bug of the new 1.1.0 beta, have NOT confirmed if this is also the case in the 1.0.11 version. I can however confirm a crash happens when the following criteria are met.
- Any fight, be it with another lord, bandits, peasants, siege, etc.
- You start with >1000 troops on your side (Would require some testing to see if it also happens if the enemy has >1000 troops)
- After the fight is done, you still have 1000 alive men (Don't know if its required for them to be on the battlefield, my performance is set to allow 1000 men at once, will be testing in a minute if it happens when you have this set to a lower amount)
- Click done
The game crashes.
I have noticed that every time it does crash, when I hit done, it displays 1000 under the 'remaining troops' on my side. I have run tests about 5 or 6 times, both fighting <1000 and >1000, both in auto-resolve and manual (manual I just used cheats to do CTRL + ALT + F4 to auto-finish it to speed it up). It crashed with 100% consistency if I had 1000 remaining men, and it didn't crash once when I had less than 1000.
Test 1:
- >1000 men
- Under performance tab, max amount units set to 901. (For the life of me I can't get it on 900 exactly)
Will report back after this test is done.
Result:
Auto resolve: Auto-resolve resulted in a crash. Game displayed 1214 remaining friendly troops. -- Tested twice
Manual: Manual resulted in a crash. Game displayed 901 remaining friendly troops. -- Tested twice
It looks like it is NOT the 'active troops' that causes the crash. I'm thinking it MAY be just your entire army having >1000 men after a battle. Maybe exactly 1000 will also crash, that'll be the next test.
Test 2:
- Exactly 1000 men
- Under performance tab, max amount units 1000. (Except last test where it will be 901 again)
Results:
Auto resolve: Auto-resolve resulted in a crash. Game displayed 932 remaining friendly troops. -- Tested twice
Manual: Manual resulted in a crash. Game displayed 1000 remaining friendly troops -- Tested once
Manual V2: Same setup, 901 as max units. Resulted in a crash. 901 remaining troops -- Tested once
So far, I have confirmed the game DOES crash if you have 1000 OR MORE units in your party at the START of the battle (troops dieing in combat does not counteract this)
Quick break:
While setting up the conditions for test 4: For some reason, when I have 1000 men in army, I donate a SINGLE unit to a garrison, and I have 983 in my army. This may have something to do with the crashing. Will be recruiting men up to 1000 again to test this.
Test 3:
- Bring men back up to 1000 from glitched 983.
- Under performance tab, max amount units 1000.
Results:
Auto-resolve: Auto resolve resulted in a crash. 978 remaining troops -- Tested twice
Manual; Manual resulted in a crash, 999 remaining troops -- Tested once
Manual: Manual resulted in a crash. 1000 remaining troops (shot one in the back of the head to see if ending with <1000 worked) -- Tested once
Test 4:
- Exactly 999 men
- Under Performance tab, max amount units 1000.
Results:
Auto-resolve: Auto resolve resulted in a crash. 928 remaining troops -- Tested twice
Manual: Manual resulted in a crash. 999 remaining troops -- Tested twice
I am confused, I was sure it had something to do with having over 1000 men in some way shape or form. Next test will be with less men until I find the tipping point.
Test 5:
- Exactly 900 men
- Under performance tab, max amount units 1000
Auto-resolve: Crashed. 809 remaining men. -- Tested twice
Manual: Crashed. 900 remaining men. -- Tested twice
So we go lower.
Test 6:
- Exactly 452 men (can't be arsed to go to 500 exactly)
- Under performance tab, max amount units 1000
Auto-resolve: DID NOT CRASH!!!!!!!!!! FINALLY
Manual: DID NOT CRASH!!!!!!!!!! FINALLY
The tipping point is somewhere between 452 and 900. **** me, this is gonna take a long ass time...
Test 7, Hypermode:
- Will be increasing/decreasing the amount of troops I bring into battle depending on if it crashes or does not to find the tipping point.
- Max units set to 1000.
- Will only be testing manual seen as this is more likely to crash (have had only 1 crash with auto-resolve, about 7 with manual over my 89 hours of playtime)
Another quick break:
It MAY be having >1000 men available at the start of a battle in general. (Adding up enemy and player). Will be documenting the total amount of units too.
452: Safe. 35 (452 + 35 == 487)
702: Crash. 745 (702+745 == 1447)
605: Crash. 745 (605+745 == 1350)
243: Safe. 758 (243 + 758 == 1001)
-- END DAY 1
God ****ing damnit. It's 1:29AM. I do not have the time to tinker around with these numbers at this time. I probably will be returning to this tomorrow. You can see the available numbers I have. I do not yet know which is causing the crashing. Whether it's the TOTAL amount of troops or FRIENDLY troops. Would require further testing (example take 702 men into a fight with 50 bandits and see if it crashes).
-- DAY 2
383: Safe. 760 (383+760 = 1143)
405: Safe 762 (405 + 762 = 1167)
Gonna need to start increasing these numbers a bit faster.
467: Safe. 760 (467 + 760 = 1127)
557: Crash. 769 (557 + 769 = 1326)
Somewhere between 1127 & 1326.
547: Crash. 769 (1336)
537: Crash. 769 (1326)
527: Crash. 769 (1316)
517: Crash. 769 (1306)
507: Crash. 769 (1296)
497: Crash. 769 (1286)
477: Crash. 769 (1266)
450: Crash. 769 (1219) -- maybe tipping point is 1200?
431: Crash. 769 (1200)
430: Crash. 769 (1199) -- **** SAKE
I give up. I don't have the patience to carry on with this. I hope I have documented enough to help the developers find the cause, although it's unlikely they'll actually read it.
If anyone would be willing to help out with this, a few things:
- Performance tab, 1000 max units (don't know if it will change anything, could try putting this to different values as well)
- Enable cheat mode (https://www.pcgamer.com/mount-blade-2-bannerlord-cheats/) and using CTRL + ALT + F4 you can knock out all enemies to make the battles go by instantly (instead of having to sit there fighting the enemy for 5 minutes)
- Please note any and all findings -- together, we are able to figure this out and save a lot of time for the developers!
Thank you.
Updating this thread as I do my research. Make sure to refresh once every few minutes, likely to have changed/added something.
Last edited:
