These screenshots are not 1440p, each image is one quarter of a 1440p, however I can clearly see difference between them in those small images so I can imagine difference is much more noticeable in a 4k display and in motion.That's the thing, its not really cheating (well kinda by not being equal) its more of what is expected in driver updates. For instance in TW3 AMD users had instant relief by having the ability in driver to adjust tessellation, Nvidia users, aptly the Kepler crowd did not, so the only alleviation available to them would be from drivers from Nvidia.
As far as discernable looks there was an Nvidia setup manual thing for it and it showed the difference (looks like it was removed or I was drunk when I thought I saw it there, and I don't drink). I do know that 64X is far smaller than a pixel therefore unnecessary as many have stated thus far.
I am not a reddit fan, never go there of my own volition but searching gave me this: Force tessellation level control? • /r/nvidia
Well I guess I wasn't drunk (obviously):
View attachment 2608
Well I guess you can see that on 1440p 16x is quite sufficient.
Could have sworn it showed thru 64X.
There was also a new image that AMD released that showed the tessellation factor against a pixel size referencing Ungines Heaven Benchmark where 64X was far smaller than a pixel.
Fortunately I saved the Q&A from AMDs Robert Hallock mostly for this one point he made:
Do you know in the Witcher 3 tessellation level is adjustable in Graphics options menu? I think the only reason for limiting tessellation in the driver is to get a free performance boost in benchmarks.
Last edited: