Crash Report

[LS777]

Game crashed fully in split second in the middle of normal turn (clicking units, moving). 2nd turn. Main campaign (3.6 TOE Mod), German side.
Crashdump and DxDiag attached.

[Joel Billings]

Sorry to hear the game is crashing for you. Has this happened to you again, and if so, do you see any pattern re what you are doing when it happens?

I've put this on our bug list, but I don't think we're going to be able to look at the crash dump for at least two weeks as the programmer is leaving for vacation.

[Joel Billings]

Pavel got a chance to look at the crash dump before he left on vacation. He was able to see the cause of the crash, and made a few adjustments that should help (although he can't guarantee they fix the bug). I should be getting a new possible beta exe from him soon, that would be good for you to use if possible. If you could email me at 2by3@2by3games.com or PM me, we can discuss how best to get it to you. He also has three quick questions for you:

1. What is your in-game UI scale set to? (Options → display.)
2. Does the mod replace any of the game's fonts, or are you using custom fonts?
3. Roughly how long did you play before it crashed?

If you do get a new beta exe from us, Pavel would like you do the following:

Please play on the next beta build ,
ideally a long session with the same 3.6 TOE Mod campaign.
Then send us engine.log — whether it crashes or not. Even a clean session
is genuinely useful: it tells us whether memory climbs steadily over the hours or
is simply high from the moment the game loads. We currently cannot tell those
apart, and that determines where we look next.
You'll find engine.log in your game folder, next to WarInTheEast2.exe:
C:\Program Files (x86)\Steam\steamapps\common\Gary Grigsby's War in the East 2\
Please copy engine.log somewhere safe before relaunching the game.
It is wiped and started fresh every time the game starts, so if you crash and
then immediately restart, the useful one is gone.
If it does crash again, please send both the crash dump and engine.log from
that same session.

Thanks.

[Joel Billings]

Pavel got a chance to look at the crash dump before he left on vacation. He was able to see the cause of the crash, and made a few adjustments that should help (although he can't guarantee they fix the bug). I should be getting a new possible beta exe from him soon, that would be good for you to use if possible. If you could email me at 2by3@2by3games.com or PM me, we can discuss how best to get it to you. He also has three quick questions for you:

1. What is your in-game UI scale set to? (Options → display.)
2. Does the mod replace any of the game's fonts, or are you using custom fonts?
3. Roughly how long did you play before it crashed?

If you do get a new beta exe from us, Pavel would like you do the following:

Please play on the next beta build ,
ideally a long session with the same 3.6 TOE Mod campaign.
Then send us engine.log — whether it crashes or not. Even a clean session
is genuinely useful: it tells us whether memory climbs steadily over the hours or
is simply high from the moment the game loads. We currently cannot tell those
apart, and that determines where we look next.
You'll find engine.log in your game folder, next to WarInTheEast2.exe:
C:\Program Files (x86)\Steam\steamapps\common\Gary Grigsby's War in the East 2\
Please copy engine.log somewhere safe before relaunching the game.
It is wiped and started fresh every time the game starts, so if you crash and
then immediately restart, the useful one is gone.
If it does crash again, please send both the crash dump and engine.log from
that same session.

Thanks.