[1.20] Game Stuck After Pressing End Turn

My game (1.2) got stuck for the second time after I pressed End Turn today (it also happened yesterday). The hourglass is on, End Turn button is in pressed state, I can move around, zoom/in out, open Govern screen etc. so it's not a hard freeze but the game is stuck in the sense that it is not moving to the next turn.

 

It's an 8-player large map game, turn 168.

 

Anyone seen this?

 

16,670 views 19 replies
Reply #1 Top

I've seen this as well.  Twice today actually.

Reply #3 Top

The thing is though, it must be some sort of a random behaviour that's causing it, because when I load the autosave it doesn't immediately hang a few turns later.

Reply #4 Top

Well at least I am not alone. This has happened like 4-5 times in my game now. Also like MarvinKosh says, it's not repeatable on the same save. When I reload the autosave, I am able to continue but some turns after it happens again. Maybe it's some timing thing.

Reply #5 Top


If it hangs like this, hit escape and save your game.  Exit the game, relaunch, and carry on as normal.

Reply #6 Top

 

My current 1.20 game, getting close to Turn 300, has just started to get stuck. However, for me it is happening in the middle of a turn. Everything works except I can't move or attack. So, yes, I save and reload, but let's hope they can snuff this bug out.

 

UPDATE: After I exited the game completely, relaunched, and reloaded, I had no further problems.

Reply #7 Top

Hit the Enter key and your turn will end normally

Reply #8 Top

Actually I do get an application hang which means hitting Enter or Esc doesn't do anything except vent my frustration.  Looking at my last debug.err it seems to happen right after a successful autosave.  Or I could be reading too much into that.

Reply #9 Top

Quoting ManiiNames, reply 6

If it hangs like this, hit escape and save your game.  Exit the game, relaunch, and carry on as normal.

This. Whenever this happens to me I do this and it's fixed.

Reply #10 Top

For me (on 1.2) when I press [enter] the game crashes. This has occured just as I passed the 100 turn mark.  I even received a note from Microsoft asking for the details! 

Unless someone knows a work-around for the 100-move crash, I will apparently have to stop playing until the 1.2 upgrade antidote is relesed. 

Reply #11 Top

Well, I've been playing today with no repeat of the issue.

What I did was take out the Ecomental mod files and transfer the settings and stuff to a fresh copy of those files from FE 1.20.

Unfortunately as I've now discovered, this is not the cause.  It must be something else. :P

Reply #12 Top

MY game hangs completely as well when it happens, no saving possible.

debug.err ERRORS are usually about stuff that wasn't found, but that doesn't coincide with the crashes. Generally theres a lot of warnings about "leaked" stuff in there lately, whatever that means.

Reply #13 Top

It probably doesn't happen every time because the random seed is not saved in your save game, and therefore if some random decision the computer makes is crashing the program, it might not make that same decision after you've loaded.  If you reload the save game a few times, you might see it happen again.  If you do, upload that save.  Just make sure you've got it set to autosave every turn.

Reply #14 Top

I think (though I can't confirm it yet) that there's a bug with the autosave.  Think about it - autosave happens when you hit end turn, not when your turn starts, right?  And the problems start when turn processing begins, starting with the save if it's needed.

I disabled autosave, mashed the turn button and didn't get a hang.  It's not much of a test.  Still have to see how things work when the game's been running a few hours and I've actually been playing instead of mashing 'Turn.'

I remember that there was a similar autosave problem with GalCiv II if there wasn't enough memory available, so it's worth looking at even if it's just to eliminate that possibility.

Reply #15 Top

I've reloaded my game numerous times (after move 100) and I am sorry to say that it crashes 100% of the time - no matter how many times I reload the game, and all previous saved games (which previously worked) will no longer work either.

Reply #16 Top

I've seen this 3 times now and each time I found a unit running on autopath from one place to another farther away on a map but gets stuck running against a 'friendly' structure or town that the unit should have pathed around.  If you select the unit and get it to stay still (animated running action but not moving anywhere when you find it) then end the turn the game continued for me each time.

Reply #17 Top

Quoting cparkin01, reply 17
I've seen this 3 times now and each time I found a unit running on autopath from one place to another farther away on a map but gets stuck running against a 'friendly' structure or town that the unit should have pathed around.  If you select the unit and get it to stay still (animated running action but not moving anywhere when you find it) then end the turn the game continued for me each time.

Not so for me.  I only have 1 unit outside of the city and it is not moving.  By now all of my save game files seem to be corrupted and I have no choice but to start a new game - but I'm not going to play again until the bug is fixed.  There would be no point.

Reply #18 Top

Quoting Ambermonk, reply 11
For me (on 1.2) when I press [enter] the game crashes. This has occured just as I passed the 100 turn mark. I even received a note from Microsoft asking for the details!
Unless someone knows a work-around for the 100-move crash, I will apparently have to stop playing until the 1.2 upgrade antidote is relesed.

Exactly the same for me.  If I take Autosave off, I maybe get a few more turns.  But then when I go to Save Game it freezes and crashes, so it's the same deal.  Unplayable.  Is there a fix for this yet?  Or do we just wait for 1.3 -- my top priority for that patch would be to fix these major crashes; all else is window-dressing.  I upgraded to 1.2 from 1.02; now I wish I hadn't.  The fact that it's a great game when it works makes it even more frustrating.

Reply #19 Top

Quoting Diarch, reply 19
Unplayable.  Is there a fix for this yet?  Or do we just wait for 1.3 ... The fact that it's a great game when it works makes it even more frustrating.

The good news is that this problem has largely been fixed.  Look for patch 1.29.  It was designed by Brad (Frogboy) expressly for people like us that have had these problems.

I posted 2 thank-you's to Brad on 2 different threads but I guess I missed this one.  This patch fixed my CTDs and also made my saved games usable again.  Thanks again Brad.

PS: He did this at home on his own time just to help those of us with this problem.  A great effort.