To firaxis - 1.21 - HUGE PROBLEM

simwiz2

Warlord
Joined
Dec 3, 2001
Messages
261
Location
New Jersey
In 1.17 there were a few times where the game would get stuck on a unit with 0 moves left for a few seconds. It was rare, so i just ignored it. But in 1.21 it is happening EVERY TURN with almost EVERY unit. My turns are taking almost a half an hour, and this is on a TINY MAP! I send a bomber out to bomb a city, and it returns to base, and i wait sometimes up to 20+ seconds while it sits there with 0/1 moves, and the terrain that it bombed has similar delays updating (taking off RR, irrigation, etc). Ok, so my computer isnt very good, and it has a celeron instead of the recommended pentium 2, but despite this i was able to play the game fine pre-1.21. This problem now makes civ3 almost unplayable on a tiny test map, so i cant imagine what it will do to my usual standard map games. The delay happens with all units, not just bombers. And it is a constant occurence. So is it a bug? Can it be fixed? Has anyone with a faster computer had this problem?
 
All I can say is try turning auto save off. It really speeds up my game. No longer have to wait much more than two seconds in between turns on huge maps.
 
Originally posted by simwiz2
In 1.17 there were a few times where the game would get stuck on a unit with 0 moves left for a few seconds. It was rare, so i just ignored it. But in 1.21 it is happening EVERY TURN with almost EVERY unit. My turns are taking almost a half an hour, and this is on a TINY MAP! I send a bomber out to bomb a city, and it returns to base, and i wait sometimes up to 20+ seconds while it sits there with 0/1 moves, and the terrain that it bombed has similar delays updating (taking off RR, irrigation, etc). Ok, so my computer isnt very good, and it has a celeron instead of the recommended pentium 2, but despite this i was able to play the game fine pre-1.21. This problem now makes civ3 almost unplayable on a tiny test map, so i cant imagine what it will do to my usual standard map games. The delay happens with all units, not just bombers. And it is a constant occurence. So is it a bug? Can it be fixed? Has anyone with a faster computer had this problem?

maybe is a bug, i recommend u reinstall civ3 and then add the 1,21f patch and the problem will sove i guess. I solved many bugs that way.
 
I don't think that what he's talking about is the time in-between game turns. I experience similar problems (at least I believe them to be similar) with my games, and it doesn't seem to be specific to this patch (I've had it with 1.16 and 1.17 also, and didn't buy the game till after 1.16). Here is what happens:

1. You move a unit. It could be any unit. Move this unit or attack with it or bombard with it until it runs out of movement points.

2. Every once in a while (no really good way to predict when it will happen, it has happened to me in countless different circumstances in every era, but it's not something that happens on every turn), when you're done moving the unit, the game will fail to auto-select the next unit and the terrain that has been affected by that unit's turn will also fail to update properly. The game itself remains responsive, and I've been able to unstick myself from this situation by saving the game while the problem is happening and reloading. Doesn't fix it every time, but it often does the trick. You can also manually select and move any other unit you could otherwise while it happens, but the game will still fail to auto-select the next unit, and it will just sit there for minutes with a unit selected showing 0 moves left if you let it. It eventually does snap back and start working normally if you wait long enough, fortunately, or I would have stopped playing this game altogether at 1.16.
 
Originally posted by simwiz2
In 1.17 there were a few times where the game would get stuck on a unit with 0 moves left for a few seconds. It was rare, so i just ignored it. But in 1.21 it is happening EVERY TURN with almost EVERY unit. My turns are taking almost a half an hour, and this is on a TINY MAP!


The Stuck Unit problem with 1.17 happened to me fairly regulary, especially at the Industrial and Modern Era. It was very annoying, and required me to save and reload.

I have not yet reached those eras with 1.21 - but I have just had a game crash after I did some Editing on units. What use is an Editor if using it causes crashing??

We shall see about this in the next few days. . .
 
I'm still using 1.17 and have had the stuck unit problem many times especially with bombard units. I stumbled on a way out though. When stuck I select a unit that hasn't moved yet and use the 'j' command. (Really just press the j key.) The computer then goes on to another unit - other than the one I selected and the one that was 'stuck'. This seems to get the autoselect process back on track. Don't know if this little trick will work on 1.21.
 
Back
Top Bottom