Always crashes after long battles

[need help]

So annoying every freaking time after a long battle this game crashes. I am on version2.03e it's ridiculous, I get a heroic victory and then I crash and have to use cheats to simulate the win because I know it will crash again. It always crashes when loading back to campaign map after a large battle.

[QuintusSertorius]

Do you wait 10-15 seconds after the end, before clicking to continue?

[Wulfburk]

I didnt had 1 crash after the end of battles ever since the first release of EB 2, and i never wait 10 or so seconds. Did you had these crashes in earlier versions?

[Auxor]

This has been happening to me. As soon as I get back from the battle to the strat map the game crashes.

[z3n]

The problem is hardware and or operating system related. Mtw2 does many complex calculations on one core. Hence the reason people with older cpu's and even newer must wait 10+ seconds or 30+ to be safe.

What is going on is trait trigger, loss count, animation and file accessing, script execution and many final battle related queries and file caching getting updated, msemory reallocation.. The list goes on.

Personally I do not get crashes with ebii however certain other mods I must play on windows xp (I made a dual boot operating system via a partition) or they are not stable.

[HaHawk]

To EBII's credit, I get far more crashes in other mods — sometimes before the battle even ends! As others have said, just to be safe, wait about 10 seconds at the end of the battle before continuing (I usually do this anyway to look at the battle stats page).

Also, I'm not entirely convinced that all crashes are CPU related. Some crashes happen with large (more than 10,000 units) battles on the highest graphics settings, whereas turning the unit detail to lowest prevents the crashes fairly reliably... So if you are crashing a lot, you might want to consider turning down some of the graphics settings just in case and see if it helps.

[QuintusSertorius]

I didn't even think about graphics settings; I tend to have mine set pretty low because I don't really care what the units look like, gameplay is more important to me than cosmetics.

[Thuycidides]

One of the main reasons for EB2 (I thought) would be better stability compared to EB1. In EB1 crashes at the end of battles became chronic once you progressed through the campaign 40-60 years.

Now battles are freezing on me with 2.03f (haven't tried g yet), so that is a new bug introduced into EB2. And it is a serious bug.

The problem is hardware and or operating system related. Mtw2 does many complex calculations on one core. Hence the reason people with older cpu's and even newer must wait 10+ seconds or 30+ to be safe.

I tried a few campaigns with MTW2 while I waited for EB2 to release, and it never crashed once. Mods cause crashes because humans introduce bad instructions where they did not exist before. It has nothing to do with how complex a calculation is, or whether it is on one core or two or four. CPUs don't get intimated by complexity and they don't start making errors because of fatigue.

I understand that the EB team has a grand vision for this mod, but take a step back and recognize that you're introducing game breaking bugs where they did not exist before.

[z3n]

Incorrect, in this circumstance. Too many instructions at once that cannot be completed crash the app, not bad instructions. Think of a getstatus ddos on a computer server.

If it were bad instructions the crash would happen before the game starts or before the battle loads or at a very specific point in time during a battle or campaign repeatedly.

Edit: just wait the recommend time 30+ seconds if it does not crash problem solved and honestly this problem is very well known. So I doubt you're encountering something completely new as the mtw2 mod community is well aware of this issue.