AMD Still Trying to Fix Rage Issues, Rolls Out Catalyst 12.1a Preview Driver

9

Comments

Comments are closed on this article

avatar

RUSENSITIVESWEETNESS

For all their me-too criticism of late, this magazine will slobber all over Carmack next time his majesty grants another interview wherein he waxes ad nauseam about his latest and greatest contribution to humanity.

avatar

Maktaka

Constant texture pop-in whenever the camera is rotated is all on id's head.

Saving taking forever and the total lack of any useful autosave system is also entirely id's fault.

So is the godawful, always-on, cannot-be-disabled mouse smoothing that makes menus almost unnavigable.

And then there's the fugly as sin textures used for close-in views of the world. If it's not a weapon model, character model, or *distant* object, it looks terrible.

Plus the fact that half of the already-short game is spent just screwing around in town or driving yet again across the same pointless stretch of desert that you've been through a dozen times before.

Then they went and used every single "dungeon" twice to really stretch the remaining content thin. How so little content requires a 20 GB download I'll never know.

So it's a repetitive, empty, nigh-unusable, pile of crap. Nothing nVidia or AMD does can turn id's pile of excretion into a good game. And given the noises coming from John Carmack after the game's release, nothing can ever restore id to a developer capable to doing any better.

avatar

blkpanthr

ummm...aprently for you...i had no issues with a oc'd 6950..

It was a fantastic game, with great graphics...

close up tecxtures were ugly..

just super short...

 

avatar

stradric

"fantastic game"?  Ha!  There were fantastic aspects of that game, but let's not pretend that one or 2 good things in a pile of garbage makes the entire pile good.  Only if you compare RAGE to decade-old titles does it seem like a good game.

Also "great graphics" is debatable.

avatar

blkpanthr

meh...sounds like your opinion

i stand by my previous statement.

avatar

blkpanthr

its a bit of both

The new idtech5 engine uses some new tequniques that werent mature enough at launch so AMD has had to muck about to patch things.

Those same tequniques have casued issue in the game code as well so Id has had to patch things.

avatar

bling581

I would say it's mostly the driver dev's that are to blame. You can't expect software devs to write programs that are only compatible with current drivers, because then it would be up to AMD and Nvidia to keep everything rolling along. They could choose to sit on their hands and release updates when they feel like it. The only thing I think ID could've done better is communicate any new features or changes to the driver devs to try and get things worked out before it was released. Obviously not all bugs can be caught during testing but there's a cutoff to what's acceptable and what's not.

avatar

bling581

So are the issues truly AMD's problem or did the devs do a crap job creating the graphics? I would think if it was the devs problem AMD wouldn't be churning out so many updates to try and fix these issues.

avatar

don2041

I have wondered about this too. seems that every time there is a driver issue with a new game, amd or nvidia get blamed, and are somehow required to fix the problem. seems to me the drivers are already there but the developers don,t bother to write compatible code but just slap some shit together and blame the graghics companies, then have them fix their fuckups.

Log in to MaximumPC directly or log in using Facebook

Forgot your username or password?
Click here for help.

Login with Facebook
Log in using Facebook to share comments and articles easily with your Facebook feed.