Originally Posted by RyanShrout
As the author of the Frame Rating stories at PC Perspective, I feel the need to comment here as I am more or less being directly attacked by BSN and AMD now. Many of you discussing this have the story and facts right here but there is still some confusion I want to clear up.
First, Alatar is right in that we use our Frame Rating / capture based testing pretty much exclusively now and have on GPU stories since March of this year. This is how we test as I fundamentally believe it is a better practice than the alternatives. We have not been "piling on" AMD in any fashion but have addressed each price segment ONE TIME with a story then have used Frame Rating for successive releases, etc. We had never fully investigated Eyefinity / Surround until my most recent article in question.
Second, there seems to the be implications that NVIDIA has "sponsored" this story or that their marketing was pushing me to write it. Obviously this accusation comes directly from AMD and the BSN story. It really couldn't be further from the truth. In fact, I have been trying to get information and answers from AMD about the Eyefinity specific problems since early August when I approached them about the story I had essentially nearly finished by then. They stalled a bit, and try to get me to not write the story, but in the end I decided it was in the best interest of the readers and the gamers to maintain our journalistic integrity. NVIDIA literally had ZERO say or impact on this story and to be honest they didn't even know how to capture Eyefinity/4K setups until after I had developed the process on the capture hardware. Yes NVIDIA has been approaching other media about these issues but as I understand it NVIDIA didn't do that until as recently as Sept 9/10th.
I actually sent a full report to AMD with my findings (screenshots, benchmarks, videos) in mid-August to show them what I was finding and to see if they had a response on WHAT the problem was specifically with EF and if they would discuss a fix timeline. They didn't get any of that for me until I told them on September 16th that I was publishing the next day.
My story was not an NVIDIA funded or promoted thing; I did this on my own in the process of continuing to test and investigate these frame pacing problems. Does it suck for AMD that it happens to be close to the announcement of their new GPUs? Yup, but as a tech journalist I think it would be improper to let that influence our editorial information and data gathering. Obviously as fixes or new products are announced we will continue to write articles and test hardware using these methods and if and when AMD fixes EF/4K, we'll be right there to report it as well.
Finally, this story on BSN is garbage and has no factual basis at all. In fact, after having heard some complaints from AMD myself over the past weeks about the decision to publish this story, I can tell you that most of the wording and accusations in it come directly from the mouth of AMD PR. If any company is attempting to use PR to sway opinions now, it is AMD. NVIDIA is no angel in these matters but in this case of the BSN story accusing me of bias, AMD is at fault. I also find it ironic that Theo "retired" from BSN over the summer, had not written anything on the site since July 29th, then suddenly re-emerged to publish that piece about me.
Thanks for reading this and sorry for butting in this thread; I usually try to keep out of talks about me and pcper.com directly.