Ray Marden wrote on Oct 8, 2011, 23:34:
If you can wait, you will get more bang for your buck by waiting for the end of year update - you can either go into a whole new line or buy one of the "old" cards at a discounted rate.

The 6950 is a good step up (20%?) from the 5850, but I upgraded because my wife needed a new system - she took my system at the time and I build a new system. At the time, the 6950 was the best sub-$300 (single) card available.
Just like how I'll probably be giving her the 6950 when the new ones ship.
Waiting for Skyrim to wash out the bitterness of Rage,
Ray

Ray Marden wrote on Oct 8, 2011, 22:34:
Yes, with v-sync disabled, the screen refreshes as much as it can whether it'a a full or partial (tearing) update.

But enabling v-sync does not cut your framerate in half - the game simply refreshes the entire screen as often as it can.

If you have a slower computer, v-sync probably does make the overall experience more smooth, albeit with a sh*t ton of tearing. However, I would gladly take a v-sync experience equivalent to 40hz, 50hz or 58hz instead of capping the game's framerate to 30 FPS.

Creston wrote on Oct 8, 2011, 21:34:
Aaaaaand the patch has made the game absolutely unfuckingplayable. I get probably a frame every 5 seconds now.

Fantastic. Thanks, John. You're a goddamn fucking champion.

Steam forums rife with people for whom the patch made things a fuckton worse. A few who say it fixed stuff. Large majority it either completely broke the textures, or can't even run anymore.

I can't even play. I can't get out of the bar. It takes a minute for the screen to update a single fucking frame.

I reckon this patch got tested on their in-house testing equipment again. Well done, id. Truly, job well done.

FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUCCCKKKK

Edit : Somehow got it working again. Deleted all cfgs and startup options, still wouldn't work. Turned off Vsync in driver. Still wouldn't work. Turned off CCC AI. Still wouldn't work. In a fit of aptly named rage, fiddled with every fucking option in existence, and now it runs...

Patch still broke Vsync, though. You can try to switch it On or Smart in the video panel, it doesn't do anything.

Christ what an incredible clusterfuck of a launch.

Creston

Krovven wrote on Oct 8, 2011, 22:43:

Creston wrote on Oct 8, 2011, 22:37:
Patch allows for ultra-spectacular new visuals! :p

Haggar's place never looked better!

Check out the details on those sunglasses!

LOL. Yep, just like Dmirti said, ignoring major technical problems and dealing with it in post-release patches sure is acceptable.

Creston wrote on Oct 7, 2011, 22:44:
Yes. And since then, AMD has released two MORE wrong drivers to the public, right? Because they just can't figure it out. Okay, Todd Hollenshead.

Edit : In fairness, after installing the latest AMD driver AND restoring the 8192 tweaks, it seems as if the texture flickering is finally gone. Hurrah.

Creston

gilly775 wrote on Oct 7, 2011, 23:50:
I still find it funny that fingers are being pointed at AMD/NVidia for poor driver support by id, yet id/Bethesda let the game ship before VERIFYING that whatever drivers that had to code the game were good enough and available to the masses. But I guess that's what some people do when you decide to choose the console as the lead development platform....

Creston wrote on Oct 8, 2011, 22:37:
Patch allows for ultra-spectacular new visuals! :p

Haggar's place never looked better!

Check out the details on those sunglasses!

Krovven wrote on Oct 8, 2011, 22:26:
Why shouldnt anyone be bitter if they spend $60 on a game and can't play it? Nevermind being bitter after having problems with Deus Ex, Dead Island and now Rage during launch weeks?

If you don't show some respect towards the people that have spent money on these games, have legitimate problems and make comments brushing off those problems...then don't be surprised when you get an earful. Now go cry in the corner.

Ray Marden wrote on Oct 8, 2011, 22:15:
So...patch notes that contain a blatant lie?

A game that mandates a 60hz refersh rate - tearing, texture resolution, graphical quality be damned?

And, if you don't give it 60hz, the game is going to limit PC gamers to 30hz?

siapnar wrote on Oct 8, 2011, 21:10:
Christ you're bitter.

Really didn't see any comments made by him that would warrant the one you just made... I just saw valid points of discussion

Ray Marden wrote on Oct 8, 2011, 22:15:
All this aside, I gave the new patch a quick whirl and it seems to work, at least on my system (6950 2GB & Win 7 64-bit)

theyarecomingforyou wrote on Oct 8, 2011, 21:48:

Creston wrote on Oct 8, 2011, 21:11:

When VSync is turned ON you should not see screen tearing. However, any time your frame rate drops below 60 frames per second you will get a sudden more severe drop to 30 frames per second. This is how VSync inherently works.

Errr, wot? If this is how Vsync inherently works, then why do I never have that problem in every other game except Just Cause 2? For that matter, why do I not have this problem in RAGE itself when I force Vsync through the CCC?

It is actually how it works. That's why many gamers are opposed to it and are willing to put up with a bit of screen tearing. The advantage of V-Sync is that it stops graphics cards over working themselves. If I disable V-Sync in some games, especially games like Crysis 2, then my graphics card heats up quite dramatically.

Creston wrote on Oct 8, 2011, 21:11:

When VSync is turned ON you should not see screen tearing. However, any time your frame rate drops below 60 frames per second you will get a sudden more severe drop to 30 frames per second. This is how VSync inherently works.

Errr, wot? If this is how Vsync inherently works, then why do I never have that problem in every other game except Just Cause 2? For that matter, why do I not have this problem in RAGE itself when I force Vsync through the CCC?