Most of you will probably sort your own problems soon enough, but for those who still find persistant problems, here are some simple fixes which may help;
DOWNLOADS
1. Nvidia drivers; Due to v81.85 not recognising the 5xxx series I was testing (unable to detect hardware), I belive they had a fault, I used v81.87 Beta instead. As of 14th Nov there is a new driver (v81.94), and although I still see little difference for anyone using a video card lower than a 6xxx series, I would recommend changing.
v81.85
v81.87
v81.94
2. DirectX 9c; I realise the CD came with dX9c updates, but I would HIGHLY recommend you scap those (July updates) and go for the Oct updates. The Oct updates seem to address a few issues which caused CTD (Crash to Desktop) in other games and could be just as effective with Civ4.
DirectX 9.0c Redistributable (October 2005) for Software Developers
filename: directx_9c_oct05sdk_redist.exe
dX9 Oct 2005
3. Codecs; There are two (2) I would recommend installing, Bink and WMP.
The Window Media Player 10 codecs can be found here...this link allows download without the "Windows Validation" process.
(filename: WM9Codecs.exe)
WMP Codecs
Bink and Smacker v7.0 should be installed for the files, you wont use the programs unless you are a developer. You can also download and install Miles sound from this site (I see no need as the files installed do not effect Civ4).
Bink
4. Chipsets; Update your chipset drivers!!! This is an absolute must for Nforce chipsets and extremley important for all others, especially in multi-player. Most motherboard companys support thier products with drivers but tend to stop updating these after 6 months or so. Most cases are that these drivers are just generic and can be found at there home sites.
ie. Your (Soltek) mainboard may use Nvidia Nforce 2 bridging chipset, onboard graphics, and Realtek Audio. So;
4in1 from
Nvidia
&
Audio from
Realtek
TWEAKS
We have seen most of these already, but I will outlay some others.
1. CivilizationIV.ini; These are some changes which can be made. They are the "safe" changes which should allow most people to play with few problems. The most important would seem to be Screenshots: Having AllowScreenShots = 1 seemed to cause CTD on few of the machines I tested on.
AllowScreenShots = 0
FullScreen = ask
AutoSaveInterval = 0
SyncInput = 0
LoggingEnabled = 1
OverwriteLogs = 1
While there are numerous other things which can improve the game and your chances of playing, most include changing or deleting files so I will not put these up. Logging is also important as the success and failure of loads will be recorded. If you can extract the info from a log, put it up so we can all help, other wise just describe the problem.
This is an awesome game which has been developed specifically for those who enjoy MOD's. It is frustrating to spend the money on anticipation of a great game only to find the hours wasted in screwing around without getting results, but hang in there, a patch will be out soon.