• 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 Shenanigans again?

lol because AMD sucks in performance in Hawx 2 they cry, hey if their cards can't handle tessellation done right that runs great on Nvidia cards then that's their problem and not the developers or Nvidia's

You seem to be jumping the gun somewhat considering its an unreleased benchmark with suspicious timing for when reviewers got their hands on it.
 
The fact this poor tessellation performance is only associated with the 6*** cards just shows that AMD's shortcuts to implement better tessellation performance with their new cards has backfired.

And what if the final games performance is different from the benchmarks? Which is almost certain since its been proven plenty in the past that synthetic benchmarks are mainly pointless when it comes to comparing them to actual gameplay.

I think you're also ignoring the fact that some review sites "just happen" to have got this early benchmark 2 days away from an AMD launch. Convenient timing? I doubt it.
 
Ubisoft are a massive company and IMO not so stupid to implement dodgy code so the game run like crap on AMD cards, it's not in their interest considering AMD have the majority of the DX11 market currently. I think it's down to AMD to sort their drivers out.

Well then the question is why did they reject the amd fix and instead stick to a version that apparently will suit nvidia cards?

Should be interesting to see what happens with the reviews coming on friday anyway.
 
Who knows, ask ubisoft, maybe they had a problem with AMD's way of doing things, apparently it runs fine on Nvidia. AMD says they can sort it in the drivers so I see no problem, yet again AMD needs to sort their drivers out as they stated. I agree with Rroff, I think AMD's new way of doing doing tessellation with the 6*** is causing them problems.

Actually if you look at the article it states amd had a fix for it, and they are working on a driver based fix for the final release. Which would suggest that drivers may not be the issue.
 
Well AMD found a solution that would benefit all GPU's, so it sounds like some money has changed hands.

This is starting to remind me of the dx10.1 patch that improved performance on ati cards in assassins creed. Did ubi ever offer a reason why it was withdrawn that didn't stink of BS?
 
All this "intentional hobbling" just seems to be a fabrication by a load of AMD fans to explain the issue and shift the blame to Ubi and Nvidia.

Considering what they done with the assassins creed patch its not exactly a wild assumption. Yet the NV fans clearly can't accept that....
 
Just like the AMD fans can't accept it's AMD's problem and not Nvidia's or UBI's, are we to believe all AMD say?

Why should people believe what nvidia and ubi have said when they were clearly in cahoots behind getting the assasins creed patch removed as it increased amd performance? All ubi could do was churn out excuses that reeked of so much BS the average bumpkin was getting high off the smell.
 
Back
Top Bottom