Summary of Events
We look at AMD Eyefinity against NVIDIA Surround with our Frame Rating technology. Results may surprise!
In January of 2013 I revealed a new testing methodology for graphics cards that I dubbed Frame Rating. At the time I was only able to talk about the process, using capture hardware to record the output directly from the DVI connections on graphics cards, but over the course of a few months started to release data and information using this technology. I followed up the story in January with a collection of videos that displayed some of the capture video and what kind of performance issues and anomalies we were able to easily find.
My first full test results were published in February to quite a bit of stir and then finally in late March released Frame Rating Dissected: Full Details on Capture-based Graphics Performance Testing which dramatically changed the way graphics cards and gaming performance was discussed and evaluated forever.
Our testing proved that AMD CrossFire was not improving gaming experiences in the same way that NVIDIA SLI was. Also, we showed that other testing tools like FRAPS were inadequate in showcasing this problem. If you are at all unfamiliar with this testing process or the results it showed, please check out the Frame Rating Dissected story above.
At the time, we tested 5760×1080 resolution using AMD Eyefinity and NVIDIA Surround but found there were too many issues and problems with our scripts and the results they were presenting to give reasonably assured performance metrics. Running AMD + Eyefinity was obviously causing some problems but I wasn’t quite able to pinpoint what they were and how severe it might have been. Instead I posted graphs like this:
We were able to show NVIDIA GTX 680 performance and scaling in SLI at 5760×1080 but we only were giving results for the Radeon HD 7970 GHz Edition in a single GPU configuration.
Since those stories were released, AMD has been very active. At first they were hesitant to believe our results and called into question our processes and the ability for gamers to really see the frame rate issues we were describing. However, after months of work and pressure from quite a few press outlets, AMD released a 13.8 beta driver that offered a Frame Pacing option in the 3D controls that enables the ability to evenly space out frames in multi-GPU configurations producing a smoother gaming experience.
The results were great! The new AMD driver produced very consistent frame times and put CrossFire on a similar playing field to NVIDIA’s SLI technology. There were limitation though: the driver only fixed DX10/11 games and only addressed resolutions of 2560×1440 and below.
But the story won’t end there. CrossFire and Eyefinity are still very important in a lot of gamers minds and with the constant price drops in 1920×1080 panels, more and more gamers are taking (or thinking of taking) the plunge to the world of Eyefinity and Surround. As it turns out though, there are some more problems and complications with Eyefinity and high-resolution gaming (multi-head 4K) that are cropping up and deserve discussion.
Keep the faith, Ryan and co.
Keep the faith, Ryan and co. Just continue to call it like you see it and let the chips fall where they may.
Hopefully AMD will get its stuff together otherwise they are going to lose a few folks.
I sincerely admire your
I sincerely admire your journalistic integrity Ryan… as well everyone else at the PCper team!
-Stewart Graham
what a difference in AMD
what a difference in AMD graft, they improved on there driver.
Is this so with an APU + Graphic card. Good job Ryan.
Well currently rolling with
Well currently rolling with 2×7970’s on a 1920×1200 triple display setup. Can’t say I ever really been personally bothered the various issues raised in the article in regards to the frame interlieaving and stepped tearing enough to stop playing, though I trust the guys over at PCPer to give it to me straight. I noticed the stuttering with crossfire more than anything else you guys brought up with your new testing methodology. I think most of us gamers at least gained a better understanding about the various issues involved. Sometimes my benchmarking applcation(be it FRAPS or Dxtory) would say I was getting a certain frame amount but the game just felt too jittery, whereas if I disabled crossfire the game felt more smooth even with a lower framerate.
That is not to say I haven’t thoroughly enjoyed my 7970’s/Eyefinity setup. When I’ve been been able to play at Eyefinity resolutions I’ve done so, when I haven’t I’ve just adjusted my quality or resolution settings until I could get a smooth enough playing experience.
Do I hope that AMD is able to smooth out those circumstances where I can’t play at a give resolution/quality due to micro-stuttering with crossfire, yeah that would be awesome. I think a lot of us out here still don’t have a full appreciation for the phenomena due to not having been able to test multi-GPU solutions side by side, so it just comes down to “the game doesn’t feel fluid enough at my current settings so I’ll dial them down until it does”, which I’m sure people have different sensitivities to. Keep up the good work PCPer crew.
what about this
what about this ryan?
http://www.brightsideofnews.com/news/2013/9/18/nvidia-launches-amd-has-issues-marketing-offensive-ahead-of-hawaii-launch.aspx#.Ujo-ScnFMsU.twitter
why use 2 hdmi cables when
why use 2 hdmi cables when you can use a single displayport cable and the problem does not exist with displayport ?
At first I thought this
At first I thought this article may have been over egging the problem with eyefinity + crossfire. Having now disconnected my second HD 7970 and played a few games in eyefinity I have seen that I is not. Radeon Pro may tell me that I’m getting half the FPS that I was but my eyes see the same low FPS experience.
Not impressed AMD, I feel like a chump for spending £300 on a card whose only additional effect to my system has been extra heat and noise.
Still at least I can go back and play Farcry 3 now with out the giant oversized HUD problem.
Thanks For the good article and thanks for bending AMD’s ear.
A damned good read thanks
A damned good read thanks Ryan. AMD owners should be pleased that these issues are highlighted and making sure AMD keep on their toes. Like the FCAT article, it was good to see AMD address the issue and get it fixed and again, it was PCper who made AMD aware of the issues (like they didn’t already know!)and forced them into sorting that out for their users.
I think a lot of hardware
I think a lot of hardware maker define CPU differently then Microsoft.you can ask I wrote a bug report to and today 13.10 beta.if I recall message signal interrupt and its extended variant were implemented in vista for consumer?ROFL we know how vista was received so this might be one overlooked good thing.my case?in regedit MSI was enabled (sad was not for some reason ,can’t enable it)but no amount of MSI set!(if it isn’t set isn’t it defaulting to one msi / socket?but I have 4 CPU in my i5 2500k(ya only physical CPU ms say)so imagine amd 8 core fx lol stuck with 1 MSI / msix.I think this is the cause.sadly on my system none were set . I normally tweak but from what I saw on ms it isn’t a case of 0 or 1.and ms recommend hex value.Rolf a bit too complex for my knowledge.but you guys know a lot of hardcore tweaker . if I’m right ? I would be like what the eck am I the only one that used vista ?
PS:what I wrote is for w8 64
PS:what I wrote is for w8 64 bit!But I suspect a lot of hardware maker default to 1 (probably easier to implement)since socket come fro 2 to 12) detecting might be entertaining.
2.1.4.1. Resolution,
2.1.4.1. Resolution, Granularity, and Accuracy of System Time
http://www.windowstimestamp.com/description
Bottom line?I hate compromise!