First off, hats off to Zappara and all the folks who have made ROM what it is, all the way to 2.3. Anyone who realizes the scope of this mod is playing with gratitude never ending.
The late game CTD is the issue I wish to address in this thread. Firstly, if those who do not play with Revolutions on and never CTD, please make that clear. Playing with Revolutions and completing a game is also something to add, though the circumstances of the game should be noted. Memory allocation crashes have nothing to do with this issue.
When you first encounter these CTDs, you will want to save your python debugging file, PythonDbg.. C:\Users\user\Documents\My Games\Beyond the Sword\Logs(windows vista path). Once you reload the game all of the previous turns are lost to the file and there is valuable information there like player numbers. PythonDbg is extremely important when troubleshooting why your game is crashing as you attempt different ways to fix it.
It is possible to find how and why a late game crashes. The first thing I like to look at are single city civs. These civs are likely spawned from mismanagement or neglect and more often than not they're mad about it.
Your first step is 'erasing' these cities with your world builder. By the time this is an issue your espionage and maps should make this a non-issue to gameplay. Erasing these cities will tell you if this is the problem and you can easily troubleshoot to find which one it is and why. At this point you should post your findings to the rest of us.
Unfortunately, it is extremely likely you will not get a single clue to why your ROM civ game crashed.. in which case, you need to get down and dirty and never take prisoners. Create a save game with all of your intentions ready for the next turn.. now you're ready to mess around on a large scale.
Take a scientific approach. It is very likely there is a city somewhere that is making the world crash. Begin with continents.. and the first thing to accomplish is the next turn past your CTD. Once you have erased something and you have continued to the next turn, you have succeeded because the problem is there somewhere. What is most important is that you narrow down to the smallest reason the CTD occured.. and letting us all know how your game crashed. Then you can keep playing and now here is my example:
PythonDbg initial:
After new world erase(continued game):
after s. hemisphere new world erase(continued game):
CTD erasing bottom half of s. hemisphere(dead end)
after top half s. hemisphere new world erase(continued game):
Russia and Arabia are vassals of Assyria(which has a rebel problem); erased the two(continued game):
Russia's erase causes a CTD while Arabia's erase does not:
Updated:
After continuing on for one turn after deleting the Arabians the game crashes once again without warning, even after deleting two cities headed for imminent rebellion. I'm at a loss
Still I encourage anybody with CTDs to post any workings about how to fix them here since the only possible way it may be fixed is with data from many sources and examples.
The late game CTD is the issue I wish to address in this thread. Firstly, if those who do not play with Revolutions on and never CTD, please make that clear. Playing with Revolutions and completing a game is also something to add, though the circumstances of the game should be noted. Memory allocation crashes have nothing to do with this issue.
When you first encounter these CTDs, you will want to save your python debugging file, PythonDbg.. C:\Users\user\Documents\My Games\Beyond the Sword\Logs(windows vista path). Once you reload the game all of the previous turns are lost to the file and there is valuable information there like player numbers. PythonDbg is extremely important when troubleshooting why your game is crashing as you attempt different ways to fix it.
It is possible to find how and why a late game crashes. The first thing I like to look at are single city civs. These civs are likely spawned from mismanagement or neglect and more often than not they're mad about it.
Your first step is 'erasing' these cities with your world builder. By the time this is an issue your espionage and maps should make this a non-issue to gameplay. Erasing these cities will tell you if this is the problem and you can easily troubleshoot to find which one it is and why. At this point you should post your findings to the rest of us.
Unfortunately, it is extremely likely you will not get a single clue to why your ROM civ game crashed.. in which case, you need to get down and dirty and never take prisoners. Create a save game with all of your intentions ready for the next turn.. now you're ready to mess around on a large scale.
Take a scientific approach. It is very likely there is a city somewhere that is making the world crash. Begin with continents.. and the first thing to accomplish is the next turn past your CTD. Once you have erased something and you have continued to the next turn, you have succeeded because the problem is there somewhere. What is most important is that you narrow down to the smallest reason the CTD occured.. and letting us all know how your game crashed. Then you can keep playing and now here is my example:
PythonDbg initial:
Spoiler :
layer 34 Civilization Barbarian State Unit Rifleman was killed by Player 1After new world erase(continued game):
Spoiler :
after s. hemisphere new world erase(continued game):
Spoiler :
CTD erasing bottom half of s. hemisphere(dead end)
after top half s. hemisphere new world erase(continued game):
Spoiler :
Russia and Arabia are vassals of Assyria(which has a rebel problem); erased the two(continued game):
Spoiler :
Russia's erase causes a CTD while Arabia's erase does not:
Spoiler :
Updated:
After continuing on for one turn after deleting the Arabians the game crashes once again without warning, even after deleting two cities headed for imminent rebellion. I'm at a loss
Still I encourage anybody with CTDs to post any workings about how to fix them here since the only possible way it may be fixed is with data from many sources and examples.
