• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Nvidia Launches "AMD Has Issues" Marketing Offensive ahead of Hawaii Launch

I see the Lt and humbug's got Ryan on the back foot elsewhere;), why would you go to all the bother of portraying your innocence-while deflecting/ignoring specific direct questions(in regards to non reporting of imo larger driver failings from Nvidia) if there is nothing to hide though.

That thread is giving me a good laugh there is so many people posting in it thinking they are being smart and not realising they are making themselves look silly.

EDIT: One thing I think people don't realise is that writing an article about nVidia failings is a much harder target to pin down - by the time its been researched, written, gone through editorial and been published often the information is out of date and in instances like 320.18 supposedly killing GPUs no one was ever able to reproduce it to actually write a factual article. Whereas stuff like frame metering its easier to gather hard data and there was little likelihood of a fix appearing before the article was pushed to the site.
 
Last edited:
That thread is giving me a good laugh there is so many people posting in it thinking they are being smart and not realising they are making themselves look silly.


To quote myself:

The individual will take from it what they will

Were probably on a different page but damage limitation springs to mind, professional reviewers are paid regardless what they review, they are usually all bought one way or another(with gifts, tech, early access, cash bungs, sometimes even employed by:eek:), otherwise all hardware reviews would hold the same outcome(which they never do), they aren't in it for free that's for sure.:)
 
PC Perspective were working for nearly a year with Nvidia on FCAT,and in their first reviews using frame metering never mentioned this relationship,which Nvidia first actually hinted at in their website(but never said they were collaborating,instead saying "the independent press" or something to that level). Funnily enough the GPU editor at Anandtech and one of the editors at HardOCP actually talked about them working with Nvidia(The Tech Report hinted at it strongly without naming names),and according to HardOCP,Nvidia had been fishing for collaborators from hardware sites for a while(they had approached HardOCP themselves).
 
PC Perspective were working for nearly a year with Nvidia on FCAT,and in their first reviews using frame metering never mentioned this relationship,which Nvidia first actually hinted at in their website(but never said they were collaborating,instead saying "the independent press" or something to that level). Funnily enough the GPU editor at Anandtech and one of the editors at HardOCP actually talked about them working with Nvidia(The Tech Report hinted at it strongly without naming names),and according to HardOCP,Nvidia had been fishing for collaborators from hardware sites for a while(they had approached HardOCP themselves).

The truth lies somewhere inbetween. I've been in contact with various people on this subject over the last couple of years so have a bit of an idea of whats been going on.
 
The truth lies somewhere inbetween. I've been in contact with various people on this subject over the last couple of years so have a bit of an idea of whats been going on.

Cause and effect-it's the timing, motive, not the findings(as it's been highly publicised since the first instance) that's beyond questionable.
 
Last edited:
I don't really know the specifics regarding the timing of this article in particular - but I do remember that back when the original article was published they mentioned investigating ultra high resolution i.e. 4k setups as something that should be done in the future (along with a number of other aspects that articles on have been slowly trickling out since) so I think that drawing a direct conclusion on the timing is potentially a fallacy without hard evidence. Due to the complexity of the material surrounding frame metering they couldn't fit it all into one or even 2 articles.

EDIT: What I mean is I think people are seeing something there because they want to see it there whether its actually true or not and theres plenty of information that potentially backs up either view on the matter which is being selectively ignored depending on what people want to see.

At the end of the day theres a lot better areas to cover for multi gpu let alone AMD v nVidia that people actually care about that would make far more sense to target if you wanted to write something bias against AMD than 4k gaming that most don't care about.
 
Last edited:
I don't really know the specifics regarding the timing of this article in particular - but I do remember that back when the original article was published they mentioned investigating ultra high resolution i.e. 4k setups as something that should be done in the future (along with a number of other aspects that articles on have been slowly trickling out since) so I think that drawing a direct conclusion on the timing is potentially a fallacy without hard evidence. Due to the complexity of the material surrounding frame metering they couldn't fit it all into one or even 2 articles.

EDIT: What I mean is I think people are seeing something there because they want to see it there whether its actually true or not and theres plenty of information that potentially backs up either view on the matter which is being selectively ignored depending on what people want to see.

The problem being, Ryan has already had access to the prototype driver which helps address the frame metering issue, but I don't see any mention/reference of it in this latest article.

Just one example of dodgy journalism:

When I went to AMD with these problems (a few weeks ago) they assured me that they are working on a fix and that it CAN be fixed.

If it does require hardware, did AMD’s upcoming Hawaii product have enough time to integrate the solution? A new architecture with the same problems with Eyefinity would be a big disappointment.

Ryan(Delboy) is misdirecting his audience-'If it does require hardware' despite first hand experience that AMD is working on a software fix, he knew that back in April:

Keeping mind that we are testing the Radeon HD 7990 with both the 13.5 beta and the prototype driver, we see very different behavior. The currently available driver sees a drop in perceived frame rate thanks to runt frame issues but that is lessened greatly with the driver build targeted for a June/July release. Without that driver the HD 7990 is much slower than both the NVIDIA GeForce GTX 690 and the GTX Titan...but with it the power of the Tahiti GPUs is much better positioned to be the top performer.

'Frame Rating: High End GPUs Benchmarked at 4K Resolutions'

http://www.pcper.com/reviews/Graphi...marked-4K-Resolutions/Battlefield-3-999-Level

Which yet again begs the question, why release a report that contradicts his earlier report so close to the 25th September as he has clearly lied to his target audience?
 
Last edited:
I am confused about something, I don't see any reference to a "AMD Has Issues" campaign on google. They don't do a very good job of explaining what exactly they are talking about re: the headline, but that's BS News for you.
 
How about naming the article "Both vendors have 4k problems?"

It's a technology that is not ready for the consumer market really, yeah it has cool screens and prototypes, but we don't really have any affordable 4k screens, or affordable GPU's to run it yet. Yes, you can buy 3x titans or 7970's or whatever but that is hardly mainstream.

I'm waiting for the time when you can run it at a single GPU, like you can with 1080p and higher now. Yeah, it's going to take a while.

And by that time, the driver problems will probably get fixed.
 
I'm waiting for the time when you can run it at a single GPU, like you can with 1080p and higher now. Yeah, it's going to take a while.

Reminds me of when I got Voodoo 2's in SLI and was able to run at a blistering 1024x768 resolution, was a while before a single card could handle it lol, and all my mates struggling with their pathetic 640x480 and 800x600 :P
 
The problem being, Ryan has already had access to the prototype driver which helps address the frame metering issue, but I don't see any mention/reference of it in this latest article.

Just one example of dodgy journalism:



Ryan(Delboy) is misdirecting his audience-'If it does require hardware' despite first hand experience that AMD is working on a software fix, he knew that back in April:



'Frame Rating: High End GPUs Benchmarked at 4K Resolutions'

http://www.pcper.com/reviews/Graphi...marked-4K-Resolutions/Battlefield-3-999-Level

Which yet again begs the question, why release a report that contradicts his earlier report so close to the 25th September as he has clearly lied to his target audience?

You are forgetting this prototype driver addresses the framepacing problem on resolutions of 2560x1440 and less.

It does nothing on the eyenfinity problems and multi-monitor problems mentioned in Ryan's article.

There is no dodgy journalism here. Read the article and you'll see.
 
You are forgetting this prototype driver addresses the framepacing problem on resolutions of 2560x1440 and less.

It does nothing on the eyenfinity problems and multi-monitor problems mentioned in Ryan's article.

There is no dodgy journalism here. Read the article and you'll see.

And this brings us to the most important part of the whole story. Why would someone write an article mentioning or criticizing 4K gaming experience a week ahead of AMD's launch of 4K optimized drivers and the Hawaii GPU architecture in (you've guessed it) - Hawaii?

Ryan admitted on oc.net he'd been holding on to the info for a couple of months. Timing stinks.
 
That wasn't in the article though.

I'd reckon he was constricted by NDA in regards to the drivers and the release date? If he'd give out the date for the drivers, people could have speculated the release date for the new architecture from that etc.

Timing for the article does suck, but still I think its better to release one now of the current situation, and do another one later when the situation is fixed. It's all pretty much for entertainment anyway, as very few people will have a 4k screen, or a Hawaii card with a 4k screen, or any nvidia card with a 4k screen atm.
 
That wasn't in the article though.

I'd reckon he was constricted by NDA in regards to the drivers and the release date? If he'd give out the date for the drivers, people could have speculated the release date for the new architecture from that etc.

Timing for the article does suck, but still I think its better to release one now of the current situation, and do another one later when the situation is fixed. It's all pretty much for entertainment anyway, as very few people will have a 4k screen, or a Hawaii card with a 4k screen, or any nvidia card with a 4k screen atm.

uninformed people still look at it and say "look amd is only trouble". Same with nVidia back when a lot of their gtx 570s was burning left and right due to bad vrm design, ohh wait no people still flocked like madmen.
 
You are forgetting this prototype driver addresses the framepacing problem on resolutions of 2560x1440 and less.

It does nothing on the eyenfinity problems and multi-monitor problems mentioned in Ryan's article.

There is no dodgy journalism here. Read the article and you'll see.


4k- is above 2560 and to display on 4K with AMD, the driver uses an eyefinity group, which he has tested with the prototype driver, again here is the link:


Drivers used@4K- 3840x2160

Graphics DriversAMD: 13.5 betaAMD: Frame Pacing Prototype 2 (HD 7990)

So yes, it is indeed dodgy journalism, you missed it even though I put up the link where he already used the prototype driver at over 2560 res, he managed to pull thee wool over your eyes didn't he?:p
 
Back
Top Bottom