ATI HD 5800 owners, do not install WHQL 11.10 Drivers or Rage will be Blue!!!

I’m sad to see this great game being destroyed by so many bad drivers from AMD!

AMD must really hate ID Software...

After so many hassles AMD finally got the driver amd_catalyst_11.10_preview3 to work great on Rage (at least on HD 5800)

Now this WHQL 11.10 Drivers makes rage blue on HD 5800!!!

I had to use Driver Sweeper to clean all 11.10 WHQL mess to get back my amd_catalyst_11.10_preview3…now I can play again

What are you doing AMD ? You want id Software to drop pc gamming?

PS: To ID Software, if you are reading this, will we have some DLC soon ? and the Hi –res Textures ?

My system:

Quad 6600@3200
4G ram DD2 8500
ATI HD 5870 MSI
2x Raid 0 Seagate 1T 7200

Yep. HD 5850 on Windows 7 x64 and this is yet another driver that rage won't work with. Full blue screen with the outtlines of a few characters on screen.

It's been a month and we have one patch. Every other game I've bought in the past 5 years has been playable at launch, and what issues there have been were solved with a patch or two.

Rage sold over a million copies to date, yet lots of people still can't play the game. Look at Rage's metacritic rating.I think ID solftware is pretty much done as a PC game developer now. I know I'll never buy another of their products.

Does that really make sense to you? A company releases a game written against a standard spec works on and off depending on another companies drivers?

Rage is not the issue here. OpenGL is an industry standard spec. AMD is on the OpenGL architecture review board. They create and support the standard, on paper at least. They are guilty of making drivers that are non-compliant (at best) and completely broken at worst. The fact it isn't noticed very much is due to the reason that OpenGL games are not very common. But I can assure you other large OpenGL programs have problems on AMD as well (Blender for example).

Considering that id has made no changes since the working Preview 2 driver, and now AMD made changes and released a driver that breaks the game, you would say id is at fault?

I think that given that a lot of people can find at least one driver that works for them (albeit unofficial and unsupported) that the major issues are driver related.

It's clearly open to interpretation as to where the fault lies. Personally I feel myself questioning just how much driver testing was done before release. After all, many other games release without widespread major driver related issues (DE:HR and BF3 to name a couple of recent releases).

There clearly needs to be greater collaboration between id and AMD, it's been noted from the tone of one of Carmack's posts that he is less than happy with AMD. If truth be known, neither of the parties is going to come out of this with much credit. People quite rightly expect a working product when they buy Rage. Just as they expect BF3 to work and to be able to play Skyrim as soon as it is installed.

We should also not forget that some gamers with modern Nvidia cards are also having problems. It's a pretty distasteful mess all round. As consumers we could do with all involved parties putting aside their bickerings and working together to repair the damage.

I use blender at least 3 days a week and have never had trouble with it.

The point is that EVEN IF AMD is at fault, ID should have tested Rage far enough in advance to see these problems coming and have worked with AMD to solve them in advance of launch. Rage has a lot of new technology incorporated in it's engine. AMD and NVIDIA can't plan for every possible use for their graphics cards, they can only optimize their drivers for the software that's out there. Since Rage is something new, it should have received more testing.

If Rage had been running correctly since launch, and these new drivers messed Rage up, no big deal. Just roll back to the older ones. But Rage was an absolute MESS at launch. No graphics options. No HDD texture cache. Horrilbe pop in in about 50% of systems. Tons of graphical anomalies. Broken animation system. Crashes on area transitions. And other issues. It took WEEKS for people to figure out how to configure a config file for their system, that Rage should have done automatically for them. All of these issues were very common and could have been solved before launch. Since then we've gotten one patch that still hasn't solved nearly all of the issues, and none of the things promised leading up to launch. No ID editor. No HD texture pack (though 85% of systems actually can't come close to running it because of the stupid compression system taking up absurd CPU cycles). No DEV COMMUNICATION. No PATCH ETA.

It's been over a MONTH since I paid $60 for Rage, and it still isn't playable. I learned my lesson, and have moved on. I won't make the same mistake again.

It didn't take weeks for the community fixes to come out, I was playing Rage before one week after buying it. Also, if Rage is finished and the problem is on AMD's end, why should id extend the release date? You want them to hold AMD's hand and whisper sweet nothings into their ears while they make blue drivers?

Sure the game didn't have the best release; however, from the looks of it, it doesn't appear to be id's fault (constant improvement of game quality by driver release). Still we don't know what is happening behind the scenes.

The Problem is AMD (ATI) not ID Software !!!

Rage uses OpenGL not DirectX like BF3, Deusix, Hard Reset...etc

If the OpenGL drivers from amd_catalyst_11.10_preview3 work great on Rage ( Q6600 HD5870) the problem is not ID software!

OpenGL from AMD svckS !!!, Run some PC demos from the scene in OpenGL (pouet.net) to see the same "artefact’s” from AMD

ID Software should have dropped OpenGL,

Sadly they paid a really high price for this this risk, other developers will think twice before releasing an AAA game only in OpenGL

Rage should have been in DirectX9-11 in PC, we all know that AMD is really bad in OpenGL…

Umm, but they did test and they did work with AMD... all the evidence is there. Quotes like "We were quite happy with the performance improvements that we had made on AMD hardware in the months before launch,: he said. We had made significant internal changes to cater to what AMD engineers said would allow the highest performance with their driver and hardware architectures, and we went back and forth with custom extensions and driver versions." and "We knew that all older AMD drivers, and some Nvidia drivers would have problems with the game".

They tested, they worked closely with AMD, they took on the best advice from AMD to ensure that it was going to work, they knew that older drivers would have problems, they arranged for a special AMD driver release to support the game --- and AMD released the wrong driver, and haven't seemed to be able to get their act together since.

That's the point of working to a specification like OpenGL. If you code to a specification, and if the driver manufacturer follows the same specification, then you've got reasonably high assurance that it is going to work. It doesn't matter if you use the code in new or different ways; the point of a specification is to provide a common ground between what programmers do and what driver manufacturers provide. You don't reactively optimize a driver for specific software, you build your driver to the specification and any software that follows the same specification will work. This should be common sense. AMD's (and ATI's before them) track record in this is well known to be notoriously bad, whereas ID's is well known to be quite good. AMD even contribute to the OpenGL specification - they can't even follow a specification that they helped write themselves.

Frankly the apparent eagerness some people have to blame id (and exonerate AMD) for this state of affairs is shocking. Some people are just behaving like a pack of monkeys, jumping up and down in their cages, screeching, and flinging their sh-t about. No matter how many times the same thing is stated, over and over again, with all the evidence tallied up and presented, those people seem to just want to point the finger at id. The above quotes were publicly released by id; AMD have not released anything to deny and/or contradict them, therefore they must be taken as an accurate description of what happened.

It really has nothing to do with AMD's drivers, it is the game itself that is broken on PC, which in turn is breaking the drivers. And, of course id doesn't seem to want to address the situation.

You're entitled to your opinion. Kindly show the same consideration to others. Otherwise you make yourself seem like just another rabid internet troll.

Please explain:

• The game works fine on NVIDIA
  
• The game works fine with some AMD driver versions
  
• The game doesn't work with other AMD driver versions

Surely a game that was broken on the PC would fail in all 3?

Surely, with all other things being identical, if going from AMD driver version A to AMD driver version B causes the game to break, then the only thing that changed must be what broke the game?

Surely?

I suspect that you've hit the nail on the head here, and that we'll see a D3D port of Rage at some point in time. Unfortunately, texture upload speeds on AMD under D3D utterly svck too (even Intel integrateds are faster!), and with that likely to be the primary bottleneck in the game, people won't see great performance as a result. But it will work.

Screenshots or Images?


Screenshots or Images?


Sad but true If something @ OpenGL fails is due to a faulty OpenGL driver from AMD and certainly not the OpenGL standard

And OpenGL as API itself has been ahead of time for many years on DirectX. DirectX onyl eveolved to the level of OpenGl at the release of DirectX 10.1

If an OpenGL game fails to run AMD should be blamed for not supporting the needed extentions or they so called "driver optimization" that are made outside the normal API calls that break the sh*t. And ontop of that AMD has always been lacking @ OpenGL support unlike nVidia's mature evolved OpenGL driver.

Not quite true. D3D had vertex buffers and programmable shaders first. The dreaded gl_arb_draw_elements_base_vertex? Only approved as an OpenGL extension in 2009, part of D3D since 2003 (http://www.opengl.org/registry/specs/ARB/draw_elements_base_vertex.txt even namechecks D3D). The geometry shader was entirely Microsoft's invention. True, there are some parts of OpenGL that were ahead, but it's been more like a 75/25 split in favour of D3D for quite some time.

All academic of course...

Got a 5700 and my game is now f'd and blue. I actually had very little to no problems until this last driver update. ALL my other games run fine with no problem at all. I point my finger at carmack and his drones.

Do you now?

What about this: http://www.gamesas.com/index.php?/topic/1249144-ati-1110-final-drivers-fix/ ?
And this: http://www.gamesas.com/index.php?/topic/1238786-new-rage-pc-update/#entry19013075 ?
Oh, and look at the havoc they're causing elsewhere too: http://forums.amd.com/game/categories.cfm?catid=279 and http://forums.amd.com/game/categories.cfm?catid=260&entercat=y
"Crossfire causing lockup", "Major problems with 6970 crossfire in BF3", "11.10 Drivers and WEI Score went from 7.8 to 6.3", "Bad Company 2 - Frame Skipping", "HD 4890 + BF3 + AMD Overdrive = BSOD. Help please.", "Stuttering in BF3", "BF3 problem with artifacts", "Green rectangle and letter ? on pc startup, intermittent", etc etc etc yadda yadda yadda.

Pretty damning, eh? Better point your finger at AMD here, methinks.

It's the drivers.

you're not the only one the MSI ATI HD 6850 is not any better, my ATI HD 5750 runs better.

It's the Carmack.

Maybe it`s because Terry Makedon aka Catalystmaker left the driver division? http://twitter.com/#!/catalystmaker

I really don`t get it. The chaos at AMD must be immense if they release broken WHQL drivers.

Rage is ultra smooth and plays at 60FPS in my system with 11.10 Preview 3 and CAP4

My only grip is the need of better textures definitions up close (is the 150G Patch coming soon ? )

I never had any crash whatsoever, my config is : 1680*1050, 4XAA, Large Textures and Vsync On .

The Game is NOT Broken! The problem is this Awful drivers updates from AMD and the really bad OpenGL updates that broke Rage!!!.
( Rage uses Open GL and not DirectX)

My advice? Stick with 11.10 Preview 3 if you want to play rage with not troubles.

PS: use Driver Sweep 3 to clean all ATI registries

My rig: Windows 7x64, Intel Q6600@3200 , MSI 5870 1G, 4G8500, Asus PQ5 Turbo

Sorry, but even the 11.10 release notes contain an admission that it's the drivers. Even AMD themselves are saying it's the drivers. No amount of wanting to blame id for this is going to wash, not any more. For the rest of us it just finally and definitively confirms what we already knew anyway. It's the drivers.

IMHO id Software/Bethesda should sue AMD and demand a compensation for the financial loss caused by them releasing wrong drivers all the time and thus damaging the image of id Software/Bethesda.

AMD should finance the development of the upcoming DLC (I hope) with the a new patch with Hi-Definition textures for us PC owners !!!