next turn button just stopped working

on turn 1034 "next turn" button just stopped working.  I tried everything...loaded... reloaded..gave it time to update.  everything else works fine but it just wont go to next turn.  I backed up the game a few turns and played it through and it sticks at the same point more or less.  If I start a new game it works fine....afraid it may stick agian...Anyone else experience this?

2,182 views 4 replies
Reply #1 Top

Have you checked all your units?  Some times you have to find a unit and make it "guard" or something to end the turn. 

 

EDIT: to clarify, a unit that is not already stationed in a city.  Or any bugged double wifes.  Check them and make them gaurd.  Or they might be in combat, sometimes if they get in combat and its an auto one that doesn't go into the auto-battle or battle screen, the game can pause if you move the camera away.

Reply #2 Top

Autoexplore is known to cause this as well.

Just cycle through all your units with 'next unit', and make sure everyone moved.

Reply #3 Top

on turn 1034 "next turn" button just stopped working.  I tried everything...loaded... reloaded..gave it time to update.  everything else works fine but it just wont go to next turn.  I backed up the game a few turns and played it through and it sticks at the same point more or less.  If I start a new game it works fine....afraid it may stick agian...Anyone else experience this?
End of quote

 

You have a memory leak problem at that point. Go back, load the autosave, then immediately save it again in one of your own files (file x say), then exit the game and reload file x, it should work now .. for awhile anyway until the memory leak overloads the memory again.

Reply #4 Top

Autoexplore is known to cause this as well.
End of quote

This is usually the case. Boats seem particularly prone, so check them first. Stuck units will generally remain outlined in yellow in the unit tree on the left side of the screen when you try to run the turn.

You have a memory leak problem at that point.
End of quote

AFAIK stuck turns are not known to have any connection with memory issues. The bulk are due to autoexplore/pathing.