Consistent CRASH before entering battle (and perhaps a solution)

Hi:

I have a problem of quitting to desktop about 1/5 of the time whenever I start a battle. I can't even play a custom game / quick battle because it guarantees to quit to desktop. In the campaign game it also causes a lot of pain, because I HAVE TO use auto-resolve which gives me a lot of extra losses. I also have to save every time before entering a battle, so I don't lose any progress. :furious3:

Last night I tried to set all of the video preference to minimum, and what used to 100% cause a crash (in my save game) turned ok OK. I haven't tested this to other occassions. Just reporting here so you might want to give a try.

(It will be nice if this can be fixed in a patch. ~:) )

If I understood you correctly, turning the graphics options down to minimum fixed the problem. If this is the case, the problem seems to be with your system (most likely your graphics card) rather than the game. Head over to the apothecary where more tech-minded people will be able to help out.

Yes, this sounds like an issue with vid drivers, directx, your vid card, BIOS settings, etc. When you post about a problem like this (even when presenting a solution) it is best to list basic system specs as well: vid card, CPU, motherboard, system memory, OS, DX version, and anything else of relevance.

I have the exact same problem

I have the exact same problem in late game, when the armies become full stack. Early in the game with not full stack armies it is OK.

~:cheers:

Ok, could you all try listing some specs? :help: It is going to be tough to find a common thread if we have to play 20 questions to find out what systems you have. ~D Probably should add what unit size setting you are using, as well as basic info about resolutions and game settings. For all we know you might all have the same vid card... or be running with minimal memory, etc.

This sounds like a lack of video texture memory or something like that. Having it happen in large vs. small battles suggests as much. Could be lack of system memory too. Or could be the drivers or BIOS settings.