UPDATE: still no idea why this is happening but there seems to be two workarounds:
1) Reduce the size of one of the text files, e.g. discard unused entries. Doing this with export_units, export_buildings or historic_events worked for me (did not try others).
2) Increase the size of one of the text files by adding a bunch of dummy lines (see post 27).
Strangely, increasing/decreasing the size of ANY text file seems to fix the problem (export_units, export_buildings or historic_events at least). That is, if you had only altered export_units when the CTD occurred then you do not necessarily need to increase/decrease export_units to fix the problem: you could alter historic_events instead, for example.
~~~~~~~~~~~~
Help!
I am getting a CTD every time I start a new campaign - as soon as the faction selection menu's "start" button is clicked - UNLESS I delete strat.txt.strings.bin first. That is, I need to delete that file every time I start a new campaign. I don't understand why because I have never had this problem before.
If I delete it and run the game then no problem. If I quit then I get a CTD every time I try starting a campaign from then on (not just the first attempt).
I had changed strat.txt but I reverted it back to how it was and I still have the problem. What really has me stumped is that I took both strat.txt and strat.txt.strings.bin from vanilla Third Age (I'm working on a submod) and put them in my folder and I still get a CTD. So it isn't a problem with strat.txt itself otherwise TATW would have this problem too, right?
If I delete both strat.txt and strat.txt.strings.bin then no CTD any time (the log says found it in the packs and the texts are missing in-game).
I do have some changes in other files but I can't spot any problems and in any case why would they only cause a CTD when strat.txt.strings.bin is present? They don't throw any log errors when the game does start (beyond a few that I have always had).
Any help would be very much appreciated because I'm utterly stumped.
The log is attached. These errors are not the cause because I have had them for a long time:
Spoiler Alert, click show to read: