-
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?
- Thread starter Gerard
- Start date
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.
As Rroff says tessellation is tessellation, AMD looks like they want to take short cuts in getting better performance on their new cards going by the slides doing the rounds, obviously this does not work well in Hawx 2.
As Rroff says tessellation is tessellation, AMD looks like they want to take short cuts in getting better performance on their new cards going by the slides doing the rounds, obviously this does not work well in Hawx 2.
Last edited:
Permabanned
- Joined
- 22 Feb 2010
- Posts
- 1,629
Its not all about tessellation raven...
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.
Indeed, ive yet to see it make much of a difference at all in any game its been implemented into. Just seems that some people get a stiffy over it depending on how they can run that Heaven benchmark.
Ubisoft are a massive company and IMO not so stupid to implement dodgy code so the game runs 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.
I wonder what Ubisoft did 'wrong' in performing tesselation for HAWK2.. I'd be interested to find out if what they implemented was an easier way to code tesselation, or just a different flavour of tesselation suited to nvidia.
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.
Thing is for tessellation to work... you need a standard implementation that takes the data your providing it with and spits out the same reliable output each time... otherwise your game can very easily break... so I can't imagine whats going on... my gut instinct looking at the graph of AMD performance over different levels of tessellation is that they are trying to take some kinda shortcut to artificially inflate their tessellation performance but thats not something I can substantiate.
My instinct is that AMD is optimising the data in some way before handing it off to the tessellation processing so that the output is consistantly within the range their hardware works best at, which would probably give reasonable gains on nVidia cards as well but not show the raw hardware performance difference so vividly. I'm in 2 minds on that as it does potentially increase performance without much if any visual hit but does maybe hide future performance issues.
My instinct is that AMD is optimising the data in some way before handing it off to the tessellation processing so that the output is consistantly within the range their hardware works best at, which would probably give reasonable gains on nVidia cards as well but not show the raw hardware performance difference so vividly. I'm in 2 minds on that as it does potentially increase performance without much if any visual hit but does maybe hide future performance issues.
Last edited:
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.
Last edited:
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.
Do you actually know AMD's 'new' way of doing tessellation?
What's the problem anyway? It's an unreleased card, and say it will be improved by released day (not fixed I noted just improved).
Perhaps Ubisoft wanted to do Heavy tessellation and AMD's card's unfortunately don't offer this? Who knows?
I'm sure it will all come out in the wash.
What's the problem anyway? It's an unreleased card, and say it will be improved by released day (not fixed I noted just improved).
Perhaps Ubisoft wanted to do Heavy tessellation and AMD's card's unfortunately don't offer this? Who knows?
I'm sure it will all come out in the wash.