Ah, Gramphos you poor dude. LoL, reading through this you seem to be dealing with people with an impressive amount of patience on your part.
I'm one of those people who got civ working by making a new user acount, so I tried your recommendation about deleting the cache and sure enough the game worked after that.
I should have thought of that, being a programmer myself, but it was 1 am and I was tired and the brain wasn't working real great.
So thanks, now I can delete my extra user account... gota see if I can get that kick ass game I played earlier today copied over first though...
So in conclusion, it does seem to be some wierdness with ATI and their newest cards. However, we can't entirely take the blame off Firaxis, as they probably should have had someone somewhere run the game on an x800 AGP / x800XL (both of which appeared to have this problem). As a programmer at a game company I can understand how this can happen; pressure to get the game out on time is, well, undescribeable (how many all nighters did you guys pull just before it shipped? My company did 48 hours straight before we shipped First To Fight ), I also understand how it feels to be a gamer getting the box and being pissed that I can't just play it right away. Its a tough industry we work in, and the blame really should rest on the way the publishers work it.
By the way Firaxis, if any of you read this, "2k games" was the label we published First to Fight under and let me just say, we didn't exactly enjoy our publishing arrangement with them.... I was a little depressed to see their logo on the Civ4 box...
I'm one of those people who got civ working by making a new user acount, so I tried your recommendation about deleting the cache and sure enough the game worked after that.
I should have thought of that, being a programmer myself, but it was 1 am and I was tired and the brain wasn't working real great.
So thanks, now I can delete my extra user account... gota see if I can get that kick ass game I played earlier today copied over first though...
So in conclusion, it does seem to be some wierdness with ATI and their newest cards. However, we can't entirely take the blame off Firaxis, as they probably should have had someone somewhere run the game on an x800 AGP / x800XL (both of which appeared to have this problem). As a programmer at a game company I can understand how this can happen; pressure to get the game out on time is, well, undescribeable (how many all nighters did you guys pull just before it shipped? My company did 48 hours straight before we shipped First To Fight ), I also understand how it feels to be a gamer getting the box and being pissed that I can't just play it right away. Its a tough industry we work in, and the blame really should rest on the way the publishers work it.
By the way Firaxis, if any of you read this, "2k games" was the label we published First to Fight under and let me just say, we didn't exactly enjoy our publishing arrangement with them.... I was a little depressed to see their logo on the Civ4 box...
Comment