Indecisive Worker Infinite Loop

Beam

Beat 'm up Scotty!
Retired Moderator
Joined
Sep 30, 2001
Messages
1,571
Location
At 51º35'N 4º46'E
Description of problem:
While playing the Medieval Ages scenario I found that the screen was stuck at a city, i.e. no map scrolling. An automated worker appeared to be in the city. Activating and re-automating solved the problem after reloading (ahum).

Couple of turns later the screen starts jumping between two workers. Only way out is to go to F4 then to F3, find the workers and activate or disband them. Fortify does not work. Once both workers are disbanded the problem was gone.

Steps to reproduce:
Load .sav.
Fortify Knight in Basel.
Screen starts jumping.
Press F4 until the FA screen appears, then F3 for the MA screen.
Activate the 10th worker in the Worker queue (the one near Venice) and exit the MA screen.
Order the activated worker near Venice to build road.
The screen is now stuck on the worker near Pisa (probably enjoying the wine :).
F4, F3 again. Activate the second worker in the Captured workers queue and exit the MA screen.
Everything OK now.

So there is a workaround but it took me some time to sort it out and it is very annoying if you have to do this every turn.

http://www.civfanatics.net/uploads5/workerbug.zip It is 500k!

Observed result:
See problem description.

Expected result:
See problem description.
 
Had a similiar problem last night in an epic game, about 300 or so turns in, several workers that were automated got stuck in a loop, I don't really know what triggered it, but taking control of them manualy and putting them too different tasks somewhere else then auto'n them stopped it. Only seen it that one time.

Lionel
 
@Beammeuppy: Great work catching this, and coming up with a workaround. There's definitely something fishing going on here.

@Pounder: The AI's turn takes an excessive amount of time (there are a lot of units) but I got to the next turn without any problems. It never locked up :confused: Of course this was in 1.15, so something may have been fixed since 1.02 which I assume you save was created with.
 
Back
Top Bottom