That's obvious. Instead, some make up their minds quickly and then point blame!
And it is really sad to observe.
"I don't know anything indepth about the topic, I won't won't read technical explanations about the topic...and your are WRONG!!!"
And for the umpth' time, the silence of AMD is speaking volumes.
It is almost like the know the issues is not malicous code...but a hardware/driver thing (most likely their fixed tessellation engine opposed to NVIDIA's shader based tessellation engine.)
So to sum up:
- There has been offered technical posts/links explaining why the ocean is tessellated, even when hidden out of sight.
- There has been posted technical posts/links explaning why this dosn't require the performance to tank due to reuse of calculations/results.
- There has been offered technical posts/links explaining the I.Q degradation by lowering the tessellation factor in AMD drivers.
So infact the article in the OP has been "debunked" and a lot of posts have brought light on the confusion.
But still some people posts like nothing of this sort ever happend.
This thread is dead, untill any REAL evidence confirms the tinfoilhat people *chough*