Getting around CTD

[Darviathar]

I've suffered from this to the point I have learned to fix it in almost all cases. I save my game every single turn now, using 8 slots on a rotating basis in case I need to go further back. The problem is usually a rebelling city, but today I discovered that the game doesn't seem to crash on me if I have *any* units inside of the city; it has to move them out, and this seems to be enough to keep the game on track. I discovered this today while conquering interior Carthaginian cities and forcing them to revolt in order to give Numidia possession. As for crashes that occur for a computer faction, I find that exposing the map and watching movement often gets around it. It takes a few minutes, but is well worth it when compared to the prospect of losing a 40 hours-played game.

[Marcus Camillus]

Now that you mention it, someone else noted and mentioned to me that if they selected to "watch AI movement", their campaigns either did not CTD at all or as much. Perhaps this is why in my own campaigns I have not seen the kind of CTD problems others seem to experience. I know they are getting them from the CTD_Savegame files they have sent to me, but my own campaigns do not have these problems. I have always used the "watch AI movement" option during my campaigns. This option only lets me watch AI movement within visual range of one of my characters/agents/armies/cities.

[Darviathar]

Its almost as if the computer is forced to slow down and think a bit longer about what its doing, that it doesn't come "untracked". Since I started this, I've only had one fatal CTD, and because I back up every turn, it really didn't cause any trouble. I just wish I'd known this months ago when I lost so many good campaigns!

[Mathius]

This fix seems to work fine for me except when playing Seleucia, then CTD within a few turns every time. RTRPE seems if anything to have got less stable with each revision on my aging desktopn :-(