A quick comparison of the performance data in H.A.W.X. 2, with tessellation on, and that of other games/benchmarks will demonstrate how unrepresentative H.A.W.X. 2 performance is of real world performance.

I don’t know why for a tessellation benchmark, but H.A.W.X. 2 DX11 benchmark doesn’t enable the tessellation by default. What’s more you can’ enabble it with the GUI. The only way I found is to edit the following ini file:

13 thoughts on “Tom Clancy’s H.A.W.X. 2 DX11 Benchmark”

Well, AMD indeed DOES have a point when they are complaining about silly amount of polygons on screen. What good is a polygon that is as small as a pixel or less? That’s just ridiculous. We want games to advance in a good way. Not to crawl to a halt.

[quote]
What good is a polygon that is as small as a pixel or less?
[/quote]
FSAA Antialiasing is done averaging SUBpixels…
Ati is wrong. They just know their tessellator sux and they’re trying to hide it.

The AMD card is running in a system with a newer i7 core @ 3,2ghz vs. the nvidia setup with the older core 2 duo @ 3,0ghz.
Not really a valid comparison…
But still, the mid-end 460 768mb is kicking serious but vs. the slightly higher scoring high end ati card…