I just started a 1.21 beta game in OS X (I'd been holding out waiting for the final patch, but I was going into withdrawal) and I ran into a nasty bug. A worker (always the same one) will move half a space and stop. The game freezes. When I try to force quit, the game quietly closes after I hold down the keys for a couple of seconds. It happened three times in about 4 turns. Didn't matter whether I moved with the mouse or the keyboard. Guess I'll have to wait after all. :(

BTW, I've got the autosave if anybody wants it.

Originally posted by gfeier
BTW, I've got the autosave if anybody wants it.

Send it to the MacSoft beta e-mail address.

Brad

Originally posted by Brad Oliver


Send it to the MacSoft beta e-mail address.

Brad

Done.

Still having trouble with this bug. Anybody else?

I've not experienced it, but I'm playing in OS 9.2; I'll play around in OS X later to see what happens.

Originally posted by gfeier
Still having trouble with this bug. Anybody else?

I didn't see the save file come through yet, so e-mail it directly to me (bradman@pobox.com) and I'll take a look. Sometimes if the problem happens on the PC version with the same saved-game, it's classified as a "feature", and thus could be potentially fixed in the PC 1.29f patch.

How long have you waited on the worker before giving up? And if you load the game under 9, does it exhibit the same pause? You indicated that it happened 3 times in 4 tries, so I take it it's not guaranteed to occur?

Brad

I sent it off with more info.

Originally posted by Brad Oliver


...and thus could be potentially fixed in the PC 1.29f patch.


Hmmm... looking at the 1.29f patch, are we? :goodjob:

Originally posted by gfeier
Hmmm... looking at the 1.29f patch, are we?

Actually, no - I haven't seen the 1.29f code yet. I mentioned that mainly because bugs that also occur in the PC code are easier for Firaxis to fix for obvious reasons.

Originally posted by Brad Oliver


Actually, no - I haven't seen the 1.29f code yet. I mentioned that mainly because bugs that also occur in the PC code are easier for Firaxis to fix for obvious reasons.

Can't blame a guy for hoping. :(

Thanks for the chuckle, gfeier.

There is an upside to all this waiting for me, I'm doing some postgrad work at the moment and actually getting stuff done. If the patches and Editor were out--and God forbid, PTW--work, and getting to know my new girlfriend, would be impossible.

My fiance and I have taken to calling Civ3 "my stupid game"... at least she knows what she's got ahead of her. :crazyeye:

Turned out that the bug is a temporary freeze. I was just too damned impatient. I had a little more time tonight and decided to wait and see if the freeze unfroze. It did. In just about exactly one minute. Every time. I was just waiting about 10 seconds too little. Sorry about that. It's still EXTREMELY annoying since it seems to happen to one unit just about every turn, and sometimes two. I can just imagine what 1850 AD will be like. :mad:

Freezing…

We don't get any of that in the middle of winter in sunny Queensland, Australia.

I started my first Civ game in ages today, so -- if I make it to 1850 on Regent -- I am expecting the same slow-downs as I get more 'advanced'. Interesting allegory: as our civilisations achieve more 'progress', everything slows down. Is this realistic?

Is somebody in this thread trying to make a connection between "significant others" and "bugs?" Lets see, something like this, "She 'bugs' the _____ out of me over Civ3."

Sorry for the SPAM, notice the post time. Good night!

Hmmmmm.. I'm wondering if this was the problem I was having with my 1.21 game that kept freezing at the year 400 AD... was starting to drive me nuts, so I just installed a second copy of Civ III and brought it up to the 1.17 patch and left it there.

Looks like the 1.21g patch fixed the problem. End of thread! [dance] :beer: [dance]