Announcement

Collapse
No announcement yet.

Game crashes

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Game crashes

    When I play CTP2, the game runs smoothly for a long time, but once I get beyond the year 2000 or so, the game crashes. This happens no matter the size of the map. I have installed the CTP2 patch. My computer is Pentium 4, 1.2 GHz, 512 RAM. The operating system is Windows XP home edition. has anyone else encountered such a problem? Is there a way to fix it? Any help is appreciated.

  • #2
    Well you could check out our playtest.exe from the source code forum and report whether it still crashes in the according playtest thread.

    -Martin
    Civ2 military advisor: "No complaints, Sir!"

    Comment


    • #3
      I have had the same problem for some time now. Prior to moving (up?) to the X/P home edition, I never had this problem. It usually crashes between turns 330 and 360, and always during the AI movement phase. I have watched the AI movement phase in detail, using the cheat mode, and except for the fact that it usually happens when a Calvary unit is moving, I have not noticed anything else that would give a clue as to the problem.

      Comment


      • #4
        I forgot to add that this crashing to the desktop does not occur when I play the orginal game (with the official patch). It occurs evertime I play once I add the Apolyton patch. This happens on both the huge and gigantic maps, which are the only two I have played on recently

        Comment


        • #5
          I have always heard that the huge and gigantic maps are buggy. You should try a game with a smaller map.
          "Democracy is the worst form of government there is, except for all the others that have been tried." Sir Winston Churchill

          Comment


          • #6
            Originally posted by Tamerlin
            I have always heard that the huge and gigantic maps are buggy. You should try a game with a smaller map.
            Or you can try out our playtest version from the source code forum and hope that we already fixed the bug, or just report it so that we can fix it at the root.

            -Martin
            Civ2 military advisor: "No complaints, Sir!"

            Comment


            • #7
              Thanks guys. I'll try both approaches and report back on my results. This way I can justify more playing time in the name of research! I thought only the Gigantic map had bugs, which was why I had switched to the Huge one.

              Comment


              • #8
                The only crashes to desktop i ever had(it too would only happen on the enemy turns) were to do with the 'enemy tile pillage bug' thing- i believe Martin fixed it a while ago though.
                This was while running the game on Win98, so not sure on the XP side of things.
                'The very basis of the liberal idea – the belief of individual freedom is what causes the chaos' - William Kristol, son of the founder of neo-conservitivism, talking about neo-con ideology and its agenda for you.info here. prove me wrong.

                Bush's Republican=Neo-con for all intent and purpose. be afraid.

                Comment


                • #9
                  Prior to getting X/P, my only crashes were also on the pillaging of vacated tiles. Martin's GoodMod does indeed fix that problem. I had no other problems with Windows 95, 98 or even the nasty ME

                  Comment


                  • #10
                    Well it's not the map size. I tried a game on the standard size map and it experienced the same type of crash, except that it game earlier in the game, at turn 236. The earliest crash I've had on the larger maps is at turn 330.

                    It is possible to get through the crash and continue the game. Since it always occurrs during the AI movement phase, I reload the previous turn via the automatic save, go to the cheat mode and reload slic, "turn on" the entire map, and then let the AI have it's turn, then turn off the cheat mode. Over 90% of the time this will get me to the next turn. I will then experience 2 - 4 additional crashes during the next 100 turns or so.

                    I'll now try the "play test" version.

                    Comment


                    • #11
                      I have been able to locate the cause of my desk top crashes. It stems from having too many slaves. When I conquer towns, I usually elect the "enslave" option. Once I reach a certain over all ratio of slaves to citizens (about 50% I think), a strange command is implemented at the end of the AI movement phase. In those cities with the highest number of slaves, a force of 12 barbarian archers magically appear and do battle with whatever forces are garrisoned there. This happens on every turn until the Emancipation Wonder is completed. Most of the time, this command doesn't work, causing the crash. If the command does work the first time it is implemented, it will continue to work until completion of the Emancipation Wonder. If it does not work the first time time, the majority of the turns will complete as usual, but random crashes will occur, again, until completion of the Emancipation Wonder.

                      I have verified this on 6 games now, using both the standard and huge maps, with the difficulty and Barbarian activity set at the hardest levels; and using either the Apolyton Pac or the Goodmod/Apolyton Pac.

                      I am now using a very simple fix. I set the Emancipation Wonder to enable at the Gunpowder Advance (which is unrealistic in real time, but it works), as it is very unlikely one can amass too many slaves that early in the game.

                      I do not understand why this only happens under Windows X/P

                      Comment


                      • #12
                        Having slaves revolt is a normal game feature, which depends on the ratio of slaves to military units in each individual city. The emancipation wonder turns slaves into citizens, thus preventing further revolts. The magically appearing barbarian units represent the revolting slaves. When the slaves win the battle, they may form a new civilisation, and this may trigger a known game bug. It could be just a coincidence that it happens under Windows XP.

                        Comment


                        • #13
                          However the slaves shouldn't be represented by Archers all the time, it would be bezzer to let them from an up to date army.

                          -Martin
                          Civ2 military advisor: "No complaints, Sir!"

                          Comment


                          • #14
                            The units created by a slave revolt will change if you have advanced far enough through the technology tree. I recall a game where the slaves revolted into Infantrymen instead of archers. I think that only happened because I was further into the technology tree than normal – the AIs were not interested in building the Emancipation Act for some reason.

                            I can vouch for the fact that I played many SAP games where I did not accumulate very many slaves and also experienced no crashes. But when I became more aggressive in capturing slaves I then experienced crashes on a more consistent basis. I think that is more than just coincidence!

                            Comment


                            • #15
                              ETB,

                              check out what Fromafar posted. That shall be really your problem. (also follow the link for further information )

                              Originally posted by Fromafar
                              Having slaves revolt is a normal game feature, which depends on the ratio of slaves to military units in each individual city. The emancipation wonder turns slaves into citizens, thus preventing further revolts. The magically appearing barbarian units represent the revolting slaves. When the slaves win the battle, they may form a new civilisation, and this may trigger a known game bug. It could be just a coincidence that it happens under Windows XP.

                              Comment

                              Working...
                              X