AMD Frame Pacing Explored: Catalyst 13.8 Brings Consistency to Crossfire
by Ryan Smith on August 1, 2013 2:00 PM ESTCrysis 3
Our final benchmark in our suite needs no introduction. With Crysis 3, Crytek has gone back to trying to kill computers, taking back the “most punishing game” title in our benchmark suite. Only in a handful of setups can we even run Crysis 3 at its highest (Very High) settings, and that’s still without AA. Crysis 1 was an excellent template for the kind of performance required to driver games for the next few years, and Crysis 3 looks to be much the same for 2013.
Our last game and our last flip. AMD and NVIDIA exchange places one final time, with the GTX 690 and 7990 swapping out so that the GTX 690 takes the lead.
Crysis 3 is another game where AMD’s initial position wasn’t quite as bad, and consequently the improvements aren’t as great. 19% gets them to the acceptable range on the 7990, while at the same time with only 4 percentage points separating the 7990 and GTX 690 means that this is the closest the two cards have ever come to matching each other in frame time consistency.
Graphically we can see that both AMD and NVIDIA still struggle with consistency to some extent. GTX 690 in particular has a short run of very high variability about 10 seconds in that AMD doesn’t experience, likely due to their hard cap on minimum frame times.
Finally on the matter of 95th percentile times, our data here mirrors what we’ve seen earlier. AMD shows a smaller gain, with their final value of 20.7ms still leaving them a couple of milliseconds behind the faster GTX 690.
Facebook
Twitter
RSS
102 Comments
View All Comments
chizow - Saturday, August 3, 2013 - link
Written on the walls at AMD Driver HQ I'm sure, quickly referenced when questioned about microstutter being worst on CF.krutou - Friday, August 2, 2013 - link
BUT, BUT, BUT, RADEON PRO?!?LordOfTheBoired - Saturday, August 3, 2013 - link
Took them by the hand? Looks more to me like "waited until people cared, then released a benchmark to prove they didn't have the problem, while offering no constructive commentary."And the hell of it is... AMD's stance makes sense. This IS a market that hates VSync because ZOMG LAG. "The market" has made it ABUNDANTLY clear that they have no interest whatsoever in technologies that improve the visual experience at the (real or imagined) cost of responsiveness.
But apparently that's only true when there's the visual equivalent of a record skip on your screen and not when it's a subtle frame rate fluctuation. The former is a good thing because it means you "aren't lagged", the latter is a horrible thing because it means you "aren't lagged".
chizow - Wednesday, August 7, 2013 - link
@LordOfTheBoired - this is the type of indignant attitude that got AMD and their fans in this predicament to begin with.mikato - Wednesday, August 7, 2013 - link
Well one result of Nvidia releasing the software was to allow tech journalists to shine a bright spotlight on a problem of their competitor's products. Your "holding AMD by the hand" idea is pretty amusing.novastar78 - Wednesday, August 7, 2013 - link
What's sad is that AMD has ripped ATi to shreds to the point where they are spread pretty thin. Just getting a working product out the door is a task. You are being waaay too hard on them.They were using traditional methods to test and frankly it's not so unimaginable that they were caught by this. Granted, maybe it should have been caught sooner, but to demonize them or put them down for it seems a bit harsh.
They know now that it's a big problem are definitely committed to fixing it. You can clearly see that they are trying to stabilize the company and there is lots of turmoil. The moves they are making and the people being brought on board are a good sign. There is definitely a process change that needs to happen but when the tree is being shaken so many times too many apples can fall.
Give it some time, I think we will see great things form them over the next few years.
Wreckage - Thursday, August 1, 2013 - link
It did not help that certain people were claiming that AMD does not have a stutter problem.DanNeely - Thursday, August 1, 2013 - link
The problem is that AMD didn't think they had a stutter problem; or more precisely, until 3rd parties shoved the reality in their face they assumed (without testing) that they and nVidia had equal amounts of the problem.I suspect at one point in the past they were right; and that the genesis of nVidia's "years in the making" tool to measure the problem dates back to when they discovered it was a problem internally and began working on fixes so that they could announce the same tool at the same time that their drivers had a negligible impact from it. It'd be interesting to see what would happen if someone tested SLI card/driver configurations from a few years ago to see how well nVidia did at the time.
BrightCandle - Friday, August 2, 2013 - link
NVidia has had this fixed for a lot longer than that. The 680's were noticeably smoother on their release day compared to the 7970 crossfire. NVidia has claimed they have been fixing this since the 8800 and there is no reason not to believe them as HardOCP and other review sites have been noting the difference for years.HisDivineOrder - Friday, August 2, 2013 - link
Exactly. This has been a problem for as long as there has been Crossfire. I think a lot of people are so shocked by this fact (because some of them owned Crossfire and just dealt with it and didn't realize they were getting shafted) they can't accept it.Yes, you got reamed. Yes, for years, you were using Crossfire and suffering from microstutter when you needn't have to. Yes, AMD took you for a ride. It's so infuriating it drives people not to want to believe it because to believe it would be so horrible as to suddenly be intolerable.
Do what most people do. Just stick with nVidia since you know they do proper testing. Boycott AMD for a five year period and come back once you're sure AMD's got their act together.