The Worst Patch

[Jawa Jocky]

Originally posted by vondrack
I am running Civ3 under WinXP Pro and have no problems with crashing... with one notable exception. The game will crash relatively often, if I use the F3 key... should I use, say, F1 and then click the Military Advisor, it's okay... but F3 causes the game to crash "relatively" often (like once or twice throughout a 20-hour game).

F3 is my crash key too. It happened a lot on my old 98 machine, but its only happened once on my new XP pro. I just save before pressing F3 (I don't autosave).

The other thing I've noticed. Going from a PII-450MH w/ 256ram to a P4 - 2G w/ 512ram makes a huges difference. I'm actually considering trying a big map. On my old computer I would usually play small maps or increase the ocean coverage on regular maps.

The 1st patch was the only bad one, IMO.

[Thrawn05]

Originally posted by Jawa Jocky
The 1st patch was the only bad one, IMO.

I agree with that. I was better off with the out of the box version.

[Moonsinger]

I don't have any problem with patch 1.29f yet. In fact, I enjoy playing it more than any previous patch.

[Flight]

Mine used to crash in an earlier version but i posted the porblem on the bug thread above and it got fixed in the next patch and as far as i know i was the only person to report it. I was happy

It hasn't crashed since

[TheStinger]

Mine crashed after i buggered about with my drivers, once i had set it all back to the original settings it stopped crashing.

I had to reinstall though.

[Gen.Dragolen]

You can add my voice to the chorus of F3 induced crashes:
W2k Pro SP2+,
550MHZ PIII
512 MB RAM
6 GB HDD with 1.6 GB free space
1280x1024 on 8 MB AGP card

It usually happens when I go to the F3 screen after looking at a city screen or one of the other advisor screens. If I do something else, like finish the turn, no problem next turn if I start at the Military Advisor screen, and then go elsewere.

It has been doing this since the game was installed, and the game is patched to 1.29f

It's annoying, but predictible.


D.

[Moonsinger]

Out of the box, the screen went blank right after the introduction screen, but they fixed it in the first patch. Also, it used to crash all the time in WinME. After I upgraded my system to WinXP, the game hasn't crashed since.

[Grumbold]

I've had a few crashes but not often enough to get upset about it. Then again, I suppose any crash during a multiplayer game is going to be a significant irritation so PtW needs to be rock solid.

[N. Machiavelli]

I had my first crash yesterday. It's nothing that I can replicate so I chalk it up to 'one of those things'. It was a graphics/processing hang/loop that wouldn't end. I closed the game, restarted and everything was hunkey-dory.

[Ethelred]

I have had the game glitch or even crash in the Military Advisor screen as well. It started AFTER I planted a spy. Now that I wiped out the civ I had the spy working on it stoped hanging.

I think its an issue with seeing other civs units in the Military advisor.

[vondrack]

Originally posted by Ethelred
I have had the game glitch or even crash in the Military Advisor screen as well. It started AFTER I planted a spy. Now that I wiped out the civ I had the spy working on it stoped hanging.

I think its an issue with seeing other civs units in the Military advisor.

Interesting idea, Ethelred!

I will try collecting some evidence in my future games... could be a fine error report for Firaxis, if we can confirm it depends on the spy.

EDIT: Ethelred, I guess you meant to post the error report in a different thread. The bug report thread is Topped, while the PATCH README thread will soon be forgotten... I think Firaxians have less time to watch the forums lately (can't remember seeing them posting in a long time), so putting it into the bug thread should make it easier for them to notice.

[Ethelred]

I posted it here because someone allready mentioned a problem with the MA on this thread.

I then posted it to the 1.29f bug thread. After I did a search which showed a MA screen bug but there was no mention of a spy being involved in the problem. I only discovered the bug two days ago. I wasn't sure of the cause at the time since I was using the NO CD executable. I switch back to original version and still had the bug. When I wiped out France, where I had the spy, the bug went away. So now I am pretty sure about it.

[Catt]

I just had my fourth or fifth crash in the eight months I've had the game. Near as I can remember, every one of those crashes occurs when a fighter on air superioity engages an enemy bomber, often near the "edge" of the map. These incidents have occured under 1.21, 1.17, maybe earlier patches as well.

(It doesn't crash on all AS missions - these work well the vast majority of the time - just trying to say that all of my limited crashes seem to occur in the context of air battles).

Catt

[Thrawn05]

Originally posted by Catt
I just had my fourth or fifth crash in the eight months I've had the game. Near as I can remember, every one of those crashes occurs when a fighter on air superioity engages an enemy bomber, often near the "edge" of the map. These incidents have occured under 1.21, 1.17, maybe earlier patches as well.

(It doesn't crash on all AS missions - these work well the vast majority of the time - just trying to say that all of my limited crashes seem to occur in the context of air battles).

Catt

THis is a known problem. Most people who have made WW2 mods know of this. There is no work around at this time other then avoid air battles at the poles for the time being.

[Galvatron]

Well yes as many problems Civ III creates crashing is one which didn't occur to me but hey you never know which bugs Civ III has in store you see something new every day. Surprises. Surprises.