Why does this game not work for AMDATI yet?

Post » Wed May 16, 2012 4:52 am

All i really want is to play this god forsaken game, that i spent my hard-earned money on.
And when looking for fixes all this company is doing is blaming the graphics card drivers and doing nothing but break it worse with terrible patches.
Please Bethesda/ID, stop being worthless and actually contribute to fixing the issues at hand. I have tried an almost stupid amount of different fixes with drivers,
config files and settings for RAGE and all this game does is be a terrible piece of crap that does not work as intended.

I'm tired. This game really should never have been released to the PC community without some kind of ACTUAL testing. This is a stupid problem to have.

CPU Specs:
Windows 7 32-bit
Intel Core 2 Quad CPU Q6600 @2.4GHz
AMD Radeon HD 6800 Series
4GB RAM
User avatar
Lindsay Dunn
 
Posts: 3247
Joined: Sun Sep 10, 2006 9:34 am

Post » Tue May 15, 2012 7:11 pm

I have to say, it's working great for me. It hasn't crashed once, no blue textures, nothing that ruins the game play. The final 11.10 drivers are working well for me also.

Win7 x64
Core2 Duo @2.8
4 gigs ram
HD 6870 1 gig
X-FI Titanium PCI-e audio
User avatar
Carlos Vazquez
 
Posts: 3407
Joined: Sat Aug 25, 2007 10:19 am

Post » Tue May 15, 2012 5:56 pm

I have to say, it's working great for me. It hasn't crashed once, no blue textures, nothing that ruins the game play. The final 11.10 drivers are working well for me also.

Win7 x64
Core2 Duo @2.8
4 gigs ram
HD 6870 1 gig
X-FI Titanium PCI-e audio
I have the same GPU as you x2 but the vsync makes it kinda choppy.
User avatar
Danny Blight
 
Posts: 3400
Joined: Wed Jun 27, 2007 11:30 am

Post » Tue May 15, 2012 11:30 pm

Cool Beans, i downloaded the new AMD 11.10 Preview 3 Drivers to see if they made a difference. Now my entire game is all blue, all the time....
I even tried rolling back my drivers and re-installing old drivers, as well as tweaking the config to try and make it stop being blue.... Now its just some super broken piece of crap game.

I also tried starting RAGE in safe mode, as that is meant to reset all the games settings.... It changed nothing.
User avatar
Samantha Pattison
 
Posts: 3407
Joined: Sat Oct 28, 2006 8:19 pm

Post » Tue May 15, 2012 7:54 pm

I think what this all boils down to is don't release a game until there are working drivers in place on day one with a 99% success rate. The other odd 1% can wait for a patch. But this was more like a 15-20% success rate on launch and has only slowly risen. I would estimate that still 25% or more players aren't able to play the game properly nearly a month later. This is just not right. I can only hope this experience will somehow strengthen the relationship between game developer and driver engineers. I really hope I see an in depth article about this at some time in the future. I want to know the root of the issue. Why did this occur? Was there a lack of communication between ID's departments? Was there a lack of communication between ID and the folks responsible for the drivers? How long was ID aware that the necessary drivers to play their game didn't exist as the release date crept closer and closer? And near the end of development, when they finished testing the game and said "Yeah this is great, it works. Let's make that gold disc and send it off to the manufacturing plant." what the hell drivers were they using? Why didn't we have those drivers?
User avatar
Cesar Gomez
 
Posts: 3344
Joined: Thu Aug 02, 2007 11:06 am

Post » Wed May 16, 2012 5:19 am

I hope PC users dont buy Skyrim now. This engine is so PC unfriendly its ridiculous and i doubt that (due to the lack of productivity going on by ID/Bethesda) that the issues with the engine will be fixed when Skyrim comes out.
User avatar
meg knight
 
Posts: 3463
Joined: Wed Nov 29, 2006 4:20 am

Post » Wed May 16, 2012 5:38 am

People really need to stop blaming AMD, because it's not only their fault, it's id's fault as well for sending out a broken game.
User avatar
Maddy Paul
 
Posts: 3430
Joined: Wed Feb 14, 2007 4:20 pm

Post » Tue May 15, 2012 5:20 pm

People really need to stop blaming AMD, because it's not only their fault, it's id's fault as well for sending out a broken game.

I'm not blaming AMD in even the slightest. I'm blaming ID 100% for releasing a game that was clearly testing on machines made out of some fancy new technology that is not for sale. Since it didn't run on any PC that exists on release day -.-
User avatar
Matt Terry
 
Posts: 3453
Joined: Sun May 13, 2007 10:58 am

Post » Wed May 16, 2012 7:10 am

I havn't so much a had 30 seconds of game play since day 1, and that was in the world of squares. I'm not going throug anymore drivers or any of that crap until it's FIXED. I was talkin to the dude at EB games 2 days ago, and he said almost every PC copy sold at his store has either been returned, or people have said to him that it just doesnt work. I will admit, I'll give skyrim a chance, but I'm letting the folks at the shop know, it may come back the next day, so ID, you crack computer programmers you, this is the last chance I give you ever, if skyrim is screwed, never again will I buy your products, and never will I suggest your products again. I'm a mod on another kind of site, and theres thousands on it, and many love to play games, trust me when I say, thats gonna be a lot of money out of your tight little pockets that couldn't spend enough to do something right. Anyway thats my once every 2 week rant as that how often I check to see if anything is fixed, I don't even really want to play this anymore I don't think. Oh, and off topic, don't buy War In the North either, not on topic I know, but hey, safety first right.
User avatar
Isabell Hoffmann
 
Posts: 3463
Joined: Wed Apr 18, 2007 11:34 pm

Post » Tue May 15, 2012 8:53 pm

Id has nothing to do with Skyrim, only RAGE. Skyrim was done by Bethesda's own developers, and was in production long before ZeniMax bought id Software.
User avatar
Tamika Jett
 
Posts: 3301
Joined: Wed Jun 06, 2007 3:44 am

Post » Tue May 15, 2012 9:07 pm

Id has nothing to do with Skyrim, only RAGE. Skyrim was done by Bethesda's own developers, and was in production long before ZeniMax bought id Software.

Just before I read this I went and looked at that actually, I thought this all along too, so I don't know why I started listening to others instead of just checking to be sure. So you are right, no ID for Skyrim, my appologies. That being said, ID is still in my very bad books, thats for damn sure!
User avatar
Aaron Clark
 
Posts: 3439
Joined: Fri Oct 26, 2007 2:23 pm

Post » Tue May 15, 2012 6:00 pm

My apologies to Bethesda in my original post. I'm just so angry about Rage not working i'm lashing out at affiliated companies for poor technical support, very poor customer service and no response on there own forums.
Rage has been out for a month, and is still a broken piece of crap. Hopefully Skyrim will be much better, but i'm not going to buy it before i read the forums and search the internet for issues with the software.

Anyways, Rage is still broken.
I've finally managed to get it to run smoothly for roughly 5-10 minutes (at most) and during this time, its pretty and works fine. But at a certain point the game just starts slowing right down and stuttering all over the place.
I've found closing the entire game and re-opening it fixes this, but only for another 5-10 minutes. SO, if you're extremely patient and want to play 5-10 minutes of the game at a time i'll post my config and launch options
as well as the drivers i used in the hopes that it helps someone having similar problems.

RageConfig.cfg
seta com_allowconsole "1"seta com_videoRam "1024" //This should be set to the amount of RAM your graphics card has (512, 1024 etc.)vt_pageimagesizeuniquediffuseonly2 8192 //This is set for 8k textures, if your PC has lower end hardware set it for 4k textures.vt_pageimagesizeuniquediffuseonly 8192 //This is set for 8k textures, if your PC has lower end hardware set it for 4k textures.vt_pageimagesizeunique 8192 //This is set for 8k textures, if your PC has lower end hardware set it for 4k textures.vt_pageimagesizevmtr 8192 //This is set for 8k textures, if your PC has lower end hardware set it for 4k textures.vt_restartvt_maxPPF 16 //This is set to 16 for my Quad Core. If you have less than Quad (Dual/single) its reccomended you set it to 8.

Launch Options:
+cvaradd jobs_numThreads 4 +com_skipIntroVideo 1 +seta com_allowconsole 1 +vt_maxPPF 16
//+vt_maxPPF is set to 16 because i have a quad core, once again, set it to 8 if you have Dual/Single core.

Edit:* I forgot to mention i'm using the Rage Performance Drivers. The new Preview 3 drivers make my entire game blue....... All of it.

I'm also accepting any suggestions that anyone might have towards fixing my game slowly degrading into unplayable territory after 5-10minutes of gameplay.

Also, before anyone goes mentioning there are already topics about this issue, i have searched alot of them and found nothing yet to fix the issue.
User avatar
Marina Leigh
 
Posts: 3339
Joined: Wed Jun 21, 2006 7:59 pm

Post » Wed May 16, 2012 5:50 am

Try this as a good fix.
http://www.gamesas.com/index.php?/topic/1250637-updated-to-1110-officialgame-crashes-immediately/

Putting the file as suggested in the same directory of Rage.exe has improved the performance of my game drastically but not fixed all the issues I have been having.

I would advise trying various settings of the AMD catalyst driver to/from application controlled. It seems for me that different boards, systems and configurations of systems require tuning separately. What suits me I am sure will not suit you and the same for everyone else.

I would move from the 11.10 P3 to the 11.10 full release before applying the fix too.

I found a major flaw in using the previews in that the game would sometimes just stop loading the textures properly. Occasionally not in obvious areas either and pretty much soon after that the game would just crash entirely. I have not experienced it yet on the 11.10 final release.
If you see textures not loading then it's not an issue for where you but I would save before you move areas because that is when the crash happens and at least you can save yourself sometime.

I also believe this issue can be more fundamental to those complaining about it crashing after the intro sequences as well.

I think the issue is a fundamental problem between the way Rage was made to make it console friendly and the lack of those limitations on a PC where the driver tries to handle the performance and clashes with the game or vice versa.
User avatar
Samantha Jane Adams
 
Posts: 3433
Joined: Mon Dec 04, 2006 4:00 pm

Post » Tue May 15, 2012 6:30 pm

There is no issue on NVIDIA hardware; the game works. These issues only occur on AMD hardware. AMD have now twice messed up a driver release over a 1 month period. AMD's (and ATI's before them) support for OpenGL is notoriously bad and has been for at least 10 years. The hardware performs poorly with dynamic texture updates, which are what Rage absolutely requires to work well; even an integrated Intel is faster.

The game was tested on AMD hardware, id knew that a driver update would be needed, they took on advice in the best of faith from AMD and AMD let them down. Here's that quote from Carmack again (and note that AMD have not denied any of this):
We were quite happy with the performance improvements that we had made on AMD hardware in the months before launch. 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.
The evidence is that id have bent over backwards to ensure that this would work on AMD hardware. They took advice direct from AMD engineers. They did everything in their capabilities to get a working game. The screwup firmly belongs in the AMD camp.
User avatar
Scared humanity
 
Posts: 3470
Joined: Tue Oct 16, 2007 3:41 am

Post » Wed May 16, 2012 7:25 am

There is no issue on NVIDIA hardware; the game works. These issues only occur on AMD hardware. AMD have now twice messed up a driver release over a 1 month period. AMD's (and ATI's before them) support for OpenGL is notoriously bad and has been for at least 10 years. The hardware performs poorly with dynamic texture updates, which are what Rage absolutely requires to work well; even an integrated Intel is faster.

The game was tested on AMD hardware, id knew that a driver update would be needed, they took on advice in the best of faith from AMD and AMD let them down. Here's that quote from Carmack again (and note that AMD have not denied any of this):
The evidence is that id have bent over backwards to ensure that this would work on AMD hardware. They took advice direct from AMD engineers. They did everything in their capabilities to get a working game. The screwup firmly belongs in the AMD camp.

That isn't true at all. I would say that as it stands more people are able to play on Nvidia hardware than AMD, but when the game came out it was like 50/50 and there are STILL Nvidia owners having issues as well. The game has run 100% flawlessly for me since preview 2 on AMD hardware. So I know that at least in that driver the opengl works fine. Logic says to me that there must be other underlying causes. It could be that older AMD hardware simply doesn't have what's necessary for this modern type of opengl but newer revisions of the hardware do.
User avatar
glot
 
Posts: 3297
Joined: Mon Jul 17, 2006 1:41 pm

Post » Tue May 15, 2012 8:57 pm

Considering that at it's core, megatexture is nothing more that a bunch of glTexSubImage2D calls, and considering that glTexSubImage2D has been in OpenGL since some time in the early 90s, I think we can rule out (or, at worst, significantly reduce) the possibility of there being any underlying causes in the engine itself.

AMD are members of the OpenGL ARB, which is the board that decides the OpenGL specification. AMD have no excuse whatsoever if they cannot conform to that specification.
User avatar
Taylrea Teodor
 
Posts: 3378
Joined: Sat Nov 18, 2006 12:20 am

Post » Wed May 16, 2012 5:14 am

Considering that at it's core, megatexture is nothing more that a bunch of glTexSubImage2D calls, and considering that glTexSubImage2D has been in OpenGL since some time in the early 90s, I think we can rule out (or, at worst, significantly reduce) the possibility of there being any underlying causes in the engine itself.

AMD are members of the OpenGL ARB, which is the board that decides the OpenGL specification. AMD have no excuse whatsoever if they cannot conform to that specification.

I don't think its as simple as you're making it out to be.
User avatar
BaNK.RoLL
 
Posts: 3451
Joined: Sun Nov 18, 2007 3:55 pm

Post » Tue May 15, 2012 11:02 pm

Tried updating to 11.10 final drivers again. It made my game blue... again. I'm gonna rollback my drivers to the Rage Performance Drivers and wait for the next patch for this game to be released.
Guess i'll go nap while ID continues to ignore there forums.... Which is sad, cause i saw a moderator post on the forum before, but only to let people know they're closing the thread. Y'know... Not for anything useful.

Heres a beautiful screenshot of what happened to my game with the new drivers. http://cloud.steampowered.com/ugc/649870345854515052/93C0C6DB53CB9359532F1227065BC59BB085336C/
Well, this is a terrible console port and i'm gonna wait until some kind of patch is released in the hopes it fixes the issue. Cool beans.
User avatar
Dragonz Dancer
 
Posts: 3441
Joined: Sat Jun 24, 2006 11:01 am

Post » Tue May 15, 2012 4:20 pm

I can sympathise, I really want to play this game and while it doesnt look like http://cloud.steampowered.com/ugc/595826512488586185/BDFF7F0BB1282FDE12430F90E0E775C71E2CAE01/ anymore the constant crashes send me back to the beginning of the game so I cant even get past the first mission :(
User avatar
Ladymorphine
 
Posts: 3441
Joined: Wed Nov 08, 2006 2:22 pm

Post » Tue May 15, 2012 4:16 pm

Oh man, finally got the game to run for a solid 30 minutes or so with the new 11.10 Final Drivers and the 6.14.10.11298 OpenGL Driver (pasting the OpenGL driver in my System32 and next to Rage.exe)
Its still not perfect but, running for 30 minutes is a big step up on previous attempts.
I've kept all the previously mentioned Launch options and Config file and so far, its still far from perfect, but i can play for over 3 times what i could before.

So hey, Thanks ID Software for suggesting nothing towards fixing up my game.
And to all the members of the community working hard on fixes for everyone, Thank You. The community are basically carrying this game and honestly, this game is worth far less than the pricetag.

The game has crashed after my solid 30 minute of gameplay on a loading screen, but other than that so far its gone fine. I'll post an update as soon as i find any more stupid problems with this fix. (There'll probably be more)

Also, this game was hyped up so much i'm not really impressed with what they've done with it. They've just gone and ripped off Borderlands, thrown away the RPG elements and made it more like a cartoon (Cartoonistic? Cartooney? Hmm, words are hard)

Anyways, hopefully this helps anyone else with a similar PC setup to mine....
User avatar
Eliza Potter
 
Posts: 3481
Joined: Mon Mar 05, 2007 3:20 am

Post » Wed May 16, 2012 7:03 am

You might try rolling back your drivers way back...11.6; 11.7; 11.8, etc. 11.8 worked for me. Then went to preview drivers and now 11.10 and works perfectly!
User avatar
lolli
 
Posts: 3485
Joined: Mon Jan 01, 2007 10:42 am

Post » Tue May 15, 2012 3:16 pm

I actually tried this with .2 thru.9 still no luck.
And get this game stop just informed me via email they arent doing anymore refunds on this game.... What does that even mean? If it's a known software issue doesnt the seller HAVE to refund it?
User avatar
GLOW...
 
Posts: 3472
Joined: Thu Aug 03, 2006 10:40 am

Post » Tue May 15, 2012 9:38 pm

Well, everyone could build an exact duplicate of my system THEN you'll know for sure RAGE (and everything else) will work for you!
User avatar
Nichola Haynes
 
Posts: 3457
Joined: Tue Aug 01, 2006 4:54 pm

Post » Tue May 15, 2012 8:42 pm

People really need to stop blaming AMD, because it's not only their fault, it's id's fault as well for sending out a broken game.

Wrong rage works perfect on ps3 360 and nvidia cards. Rage even works perfect on Linux with wine. Ati has had problems with open gl drivers for years. Ati drivers kept breaking quake wars. Every time I called ati they said just down grade the drivers. The problem is that every other driver update broke the game. Nvidia worked perfect.
User avatar
courtnay
 
Posts: 3412
Joined: Sun Nov 05, 2006 8:49 pm

Post » Tue May 15, 2012 10:48 pm

I'm not blaming AMD in even the slightest. I'm blaming ID 100% for releasing a game that was clearly testing on machines made out of some fancy new technology that is not for sale. Since it didn't run on any PC that exists on release day -.-

Maybe, but what could id have done. Ati open gl drivers have svcked for years now. They still have not fixed them.
User avatar
My blood
 
Posts: 3455
Joined: Fri Jun 16, 2006 8:09 am

Next

Return to Othor Games