My $0.02:
I’m trying to decide just how much I can say about how… how amusing it was to work with ATI’s driver manufacturers.
Suffice it to say that I have the feeling this is not entirely Firaxis’s fault. Keep in mind that developers, quality assurance, and publishers often have to work at cross purposes. The developers want the game to do everything imaginable, including make your coffee, and they want it to be pretty. The QA department wants it to work, and sometimes that just takes TIME. The publishers want the game to come out on a handy date, rather like releasing movies. One super nice release time is a couple weeks before E3, for example. Not only are there going to be thousands of people congratulating the devs and publishers at their booth, but it’s just before summer starts. Just before Christmas is obviously also a good time.
Now, in a perfect world, the developers and the QA department and the publishers are all in one building. The world is rarely perfect enough for the QA lead to go bang on the head developer’s door and ask why, pray tell, they haven’t fixed a showstopping bug and what they’re doing working on all that high level content. You can’t hang up on an irate techie. 
But in no world conceived can everyone including the developers for the video card and sound card drivers be in the same building with the game developers. It’s been known to happen that, during a game’s development and testing, the brand-newest driver from (to pick a company COMPLETELY at random. Really.) ATI suddenly makes the computer explode into so much rainbow confetti. It’s not that QA and the developers suddenly changed something or that they didn’t know that people used ATI cards.
I have the feeling – just the feeling, mind you; I don’t work for Firaxis and am not currently in the gaming industry – that the exchange went something like this:
QA Lead: frantically runs up to developer Sir! The new ATI driver is causing our game to launch computers into orbit!
Dev: Crap. We launch in a MONTH. We’re done with the game, bar testing, and they’re throwing new stuff at us? They have our specs, they have our game, why did they release a driver that doesn’t work with it?
QA Lead: Possibly because they hate us. But good news! I called them and they promised to have the new driver out by game launch.
Dev: Can we rely on that?
QA Lead: Well, do we have a choice? It’ll probably take them a month and a half to come out with a new driver; it’s not like they can just put a line of code in there that says WorkWithCiv4=TRUE.
Dev: Maybe we can delay launch for a –
Publisher: Don’t make me come down there and hit you with my stick with nails in. We are NOT pushing back the launch date any further.
QA Lead: Well, if we’re really lucky, maybe they’ll have it fixed when they say they will. Considering we’re two weeks from stamping this sucker on CDs and I already have this long list of bugs to find, I just can’t add this to the list. I put my faith in your hands, o ATI!
exeunt omnes, curtain