Possible Fixes for "Failed to Initialize Renderer" Startup Error

[ghostkiller2.0]

Originally posted by JFJohnny5

My system is an Athlon 64 3000+ with 1Gb RAM and ATI X800XL AGP. Did NOT work on this one.

My brother has a Dual Xeon (yes, Xeons...he works IT and got them cheap), not sure of clock speed, with 2 Gb RAM and an ATI X700 PCI-X. It DID work here.

Obviously this is not a good lab test, as there are so many variables. But notice they're both ATI cards, mine was AGP, his was PCI-X. Can anyone confirm evidence along those lines??

mine is a ATI x 700 (256Mg on Board) AGP and does not work with an AMD Athlon 2.2 and 768 Mb RAM

[Solver]

Forgive me, I believe I know better than you whether Firaxians are working on a solution or not.

Also, if you look around, you will notice that a couple of solutions have been proposed, and that several people have reported these solutions working for them. Given that Firaxis only found out about these problems when you guys started posting here, I would say that this isn't a bad result.

Yes, the problem itself is a mess. But the job being done to fix it is good.

Also,

there is no reason why when you own a rig capabale of running any graphically intense game presently on the market that this game should not run.

Exactly. Any rig that runs any graphically intense game supports T&L, and thus is able to run Civ4. ATI cards can run Civ4, there's just this temporary problem. So unless you're saying that some people were running Doom3 on Intel Extreme Graphics Chipset 2, you're quite right.

[codechino]

Originally posted by ghostkiller2.0


I agree that this needed to be said. However, I do understand that it could be done a bit more tactfully. Sure we are having problems. BUT it was pointed out that the non-retail versions were not having the same problems. The fact that the websites have not updated I do not think is a problem with Firaxis or 2k.

The people that were working on a response (dev Team) were posting here WHERE WE WERE TALKING ABOUT THE PROBLEM. Also, having worked with corporate websites and the like, things take time. (also they were done with their work day when the bulk of the problems arose) They need to mind their P's and Q's with press releases and the like so take it easy. Sure we are upset, we can not play the game we love.

So give them a little time. I for one am not going to rush and return the game cause of a few bugs. That is a risk we take by buying the game on the day it comes out. Patience is a virtue, and unfortunately becoming less and less common

unfortunately, getting a working game on release day is also less and less common. buyers should not have to take a risk when purchasing a game, these things shouldve been ironed out.

that said, nothing to do about it now except try and be helpful.

[BleckLord]

People, try to be more patient, wait about that returning. Getting a 100% working fix, or a 98% working for that matter, isn't quite easy, and can't be done in two hours. Firaxians are now working around the clock on it, we already have instructions that let some people fix the error, I'm sure that within a couple of days the situation will improve more.

Solver, I understand that you want to quell the rising anger of dissapointed fans, but you have a working copy (and you didn't pay $54.11 for a retail version that doesn't work).

Regardless of who's supposed to do QA or testing, the developer is the one with access to the code. I'd like to hear from someone what the log file output means (even if all I get is 'the renderer bailed cause it couldn't get a dx9 device handle'). And 2k's support is a joke, so I'm not hopeful for any help from them.

If this wasn't discovered until release, then the person responsible for writing the verification plan should be let go. If Firaxis or 2k knew about the problem, then they deserve whatever wrath we decide to dish out. It IS there job to release a product that works and work 24/7 to fix problems this big on launch day.

[trip52]

Originally posted by Solver
Exactly. Any rig that runs any graphically intense game supports T&L, and thus is able to run Civ4. ATI cards can run Civ4, there's just this temporary problem. So unless you're saying that some people were running Doom3 on Intel Extreme Graphics Chipset 2, you're quite right.

apparently not- my x700 256mb ATI supports hardware t&l and cant run it.

you did get me on the second half about doom 3 though; nicely done - touche.

while they may be working on a solution (ill buy you lunch at sizzlers if they get one to work successfully) none of it excuses the problems with this product. sid meiers should be ashamed to have his name on this at the moment.

just kidding about the lunch - ill be dead from trying to figure out how to get this damn thing to run.

[ghostkiller2.0]

Originally posted by BleckLord

If this wasn't discovered until release, then the person responsible for writing the verification plan should be let go. If Firaxis or 2k knew about the problem, then they deserve whatever wrath we decide to dish out. It IS there job to release a product that works and work 24/7 to fix problems this big on launch day.

WHOA TAKE IT EASY!! Don't call for people's jobs. Think about the variety of systems we are running. Intel, AMD Athlon, various RAM settings video cards... the list goes on. Sure you can point fingers but that is not going to do any good. Instead of complaining put out your TECH specs and HELP the dev team fix it.

[jadelith]

yes. the head of the testing team -should- be fired. I don't care if he has a family to feed, I didn't pay $54 for nothing. If the release date is on 25th, the game should be ready at 25th. for all systems. The last time I've heard of such a wide bug was HL2 (it worked fine on this comp tho :/).

[Salatir]

Originally posted by BleckLord


Solver, I understand that you want to quell the rising anger of dissapointed fans, but you have a working copy (and you didn't pay $54.11 for a retail version that doesn't work).

QFT.

[=M@ddog=]

Sure does seem odd that this basically happens to almost all ATI card users. Did Nvidia supply them with a bunch of cards so they would not let ATI cards work? That is a whole bunch of testers listed...no one has ATI?

[ghostkiller2.0]

I am off to class but continue posting replies to my posts I will be back around 1:30 CDT (GMT - 6)

[timekillr]

Originally posted by jadelith
yes. the head of the testing team -should- be fired. I don't care if he has a family to feed, I didn't pay $54 for nothing. If the release date is on 25th, the game should be ready at 25th. for all systems. The last time I've heard of such a wide bug was HL2 (it worked fine on this comp tho :/).

Note that it might not be his fault.

A boatload of people are involved in software development, and more often then not the QA leads are only responsible for what they approve; if the build is one that has not been sent to QA, then it's not their fault.

[jadelith]

If it worked on my computer, then i wouldn't be hanging around in civ4-help forum

I don't think its almost all ati users, it should be around 5-10% of them. But still, this is absolutely unacceptable. this computer ran bw2 / hl2 / pirates .... no reason to blame my computer or me on this

[PBN]

has anyone with the issue tried loading the DirectX 9.0c from MS (posted more on the other stickied thread)?

[Salatir]

Ah well, just returned the game. To those that preach patience, I understand what you're saying. But of equal weight is the opinion of those that bought a product with the expectation that it would work, out of the box, and are completely unaccepting of the flawed product. And right now, those two opinions are diametrically opposed.

I voted with my wallet. And as much as it pains me, I won't be buying this game for a few months, nor will I look upon any future Firaxis product without suspicion.

[jadelith]

my point was, the person who is in charge of the team that tested on graphics cards should be removed.

no reason to blame sid

[BleckLord]

WHOA TAKE IT EASY!! Don't call for people's jobs. Think about the variety of systems we are running. Intel, AMD Athlon, various RAM settings video cards... the list goes on. Sure you can point fingers but that is not going to do any good. Instead of complaining put out your TECH specs and HELP the dev team fix it.

I agree, there are too many combinations to test, the catch is that the problem follows the graphis card (specifically ATI brand), not the system internals. This does not seem to be an uncomon problem, which means it should be easily duplicated in a controlled/test environment.

Would you be asking for a public statement and jobs if AMD or Intel had 30% bad processors escape testing?

[jdchambe]

Originally posted by TrashcanMan
Not sure if it would have worked with the x800XL but I know it did with the x800 Pro.

So far the only people who've posted to any of these threads who owned an x800 Pro have said that the game works fine for them. fwiw.

[bionicjames]

Originally posted by PBN
has anyone with the issue tried loading the DirectX 9.0c from MS (posted more on the other stickied thread)?

No dice, I tried it (sapphire radeon 9600 256mb)

[=M@ddog=]

Originally posted by jdchambe


So far the only people who've posted to any of these threads who owned an x800 Pro have said that the game works fine for them. fwiw.

Nope. my x800 pro wont run it

[BleckLord]

Note that it might not be his fault.

A boatload of people are involved in software development, and more often then not the QA leads are only responsible for what they approve; if the build is one that has not been sent to QA, then it's not their fault.

Ok, so I work for a ISO 9001 certified company. If 2k has a standards protocol, then there is a document describing the exact process for the release. In that document will reside the name of the person I would fire. If 2k doesn't have a quality certification, then Firaxis should be scolded for having them as a publisher.

My company has to release software that works 99.999% of the time, and you know what, it does work. If you have a well writen test and verification plan, then you can ensure software works.

[jdchambe]

Originally posted by BleckLord


I agree, there are too many combinations to test, the catch is that the problem follows the graphis card (specifically ATI brand), not the system internals. This does not seem to be an uncomon problem, which means it should be easily duplicated in a controlled/test environment.

Let's hope. For all we know 10% of the people who own ATI cards have a problematic AGP aperture setting on their mother board bios that causes a timing problem with DirectX 9.0c, that only gets exposed when you you initialize the display with the exact sequency that Civ4 happens to be initializing it. And that this 10% is all of us. *shrug*

I'm not saying that is the problem or that it is even likely, but sometimes problems with 3D games that get missed during testing can end up resolving to things like that...

[Solver]

Solver, I understand that you want to quell the rising anger of dissapointed fans, but you have a working copy (and you didn't pay $54.11 for a retail version that doesn't work).

Regardless of who's supposed to do QA or testing, the developer is the one with access to the code. I'd like to hear from someone what the log file output means (even if all I get is 'the renderer bailed cause it couldn't get a dx9 device handle'). And 2k's support is a joke, so I'm not hopeful for any help from them.

I have a working beta version right now and no retail version at all . While the developer does the coding, the publisher is responsible for how the game is released, published, etc. Likewise, the publisher sets the deadlines which means that it depends on the publisher how much testing and QA the gold build gets. t's pretty obvious that 2K didn't give the time to test the gold build on a significant number of computers, or else the issue would have been noticed.

apparently not- my x700 256mb ATI supports hardware t&l and cant run it.

you did get me on the second half about doom 3 though; nicely done - touche.

while they may be working on a solution (ill buy you lunch at sizzlers if they get one to work successfully) none of it excuses the problems with this product. sid meiers should be ashamed to have his name on this at the moment.

just kidding about the lunch - ill be dead from trying to figure out how to get this damn thing to run.

There is a difference between "can't run" and "should run, but can't". Your ATI card falls in the second category. It definitely should run Civ4, but can't at the moment - not because Firaxis designed it so, but because there's a problem that will be fixed.

And please don't mix them all together, what Sid Meier, Firaxis and 2K do are really different things.

[jdchambe]

Originally posted by =M@ddog=



Nope. my x800 pro wont run it

*sigh* Well there are some with problems with the pro then. My point is the same though, there have been reports that the x800 pro is working ok for some people. But I guess not all.

[Traelin]

Originally posted by Salatir
On a forum, not owned by Firaxis or 2k. No offense to the denizens here, but that hardly qualifies as publically owning up, in my book. Their proprietary sites need to alert those concerned with their game that there's a problem - and to give those with these particular cards that have NOT as yet bought the game fair notice.

A tech is not the public voice of his or her company. And until that public voice does something more than says "Hey, we have new wallpapers, guys!" they're not admitting anything.

I understand your frustration, really I do. Just give them a chance to get a hotfix going, or do whatever it takes to get this thing up and running. Sometimes "it" just happens, as Forrest Gump would say. IMO the fact that they're even on here trying to troubleshoot the issue, shows that they're "owning up". Most companies wouldn't even bother. Take that piece of crap UbiSoft and the worst game of all time (in terms of bugs), Pool of Radiance: ROMD. You couldn't even get them to patch most of the problems.

[timekillr]

Originally posted by BleckLord


Ok, so I work for a ISO 9001 certified company. If 2k has a standards protocol, then there is a document describing the exact process for the release. In that document will reside the name of the person I would fire. If 2k doesn't have a quality certification, then Firaxis should be scolded for having them as a publisher.

My company has to release software that works 99.999% of the time, and you know what, it does work. If you have a well writen test and verification plan, then you can ensure software works.

2K probably doesn't have what you call a "standards protocol". What they do have, most likely, is an internal QA team; that QA team tests the game, and if they don't find problems they release it.

Hardware QA testing is incredibly hard to do; 90% of the time, publishers outsource their hardware QA needs.

What I'm also saying is that it's quite possible that changes were made AFTER the QA approval process was performed and someone in the production pipeline decided to release the game.

The best way to test this issue would be to use their latest QA approved release and try it on a problematic system (I can personally vouch for a genuine ATI X800XL AGP card). If they can reproduce the problem in-house, then they can more than likely fix it.

So far, from what I've seen, the problem only happens on the following cards:

X800XL AGP
9600XT
9500
9550

Now the problem is the 9600XT is a VERY popular card, and I'm certain that the X800XL card is used in the hardware QA process.

So who knows who's at fault? All we know is we're pissed.

[Traelin]

Originally posted by trip52

i completely agree - this not acceptable...
whatever- i give em 24 hours, then everyone should just return the POS till they fix it proper.

Dude if they thought it was acceptable, they wouldn't be on here trying to fix it. I was frustrated last night, too. But I decided to wait 48-72 hours for a reasonable hotfix. Give it at least that much time.

[Traelin]

Originally posted by Solver
...the problem is that there's a compatbility issue with otherwise good Radeon cards.

Hehe that's subjective. After this and other more minor issues, I'll never buy an ATI again. I've never had problems with nVidia.

[jdchambe]

man. you people who are pointing fingers and calling for heads act like you've not spent much time on the forums for many other 3D games. It is unfortunate, but in the 3D game world, this kind of stuff happens frequently.

At least firaxis is on top of it and willing to publicly put some of their developer's heads on the chopping block by posting to the forums. Many gaming companies wouldn't do that.

Let's not bite their heads off now, or they'll stop posting helpful suggestions.

[ERLoft]

FWIW, for me, having read this thread prior to getting home and installing the game, I:

1) Went to the MS site and did the Direct X update.
2) Rebooted machine.
3) Ran the ATI Driver removal tool.
4) Rebooted machine.
5) Installed the newest Catalyst 5.10 package, including drivers.
6) Rebooted machine.
7) Installed Civ IV.
8) Rebooted machine.
9) Verified that I had d3dx9_26.dll in my Windows\System32 directory.
10) Tried to run Civ IV.
11) Got the same error message as everyone else.

My specs are posted a couple of pages back...

[crimsonmage]

At work i have the Radeon X850 AT and it works great - cant really play it here - but it looks interesting!