No you didn't. You used benches from 2 years AFTER Crysis 2
Oops, sorry about that. You are correct.
AKA long after any AMD performance issues were solved.
In other words it wasn't tessellation, but rather AMD's shitty drivers. It was GPU write back latency if I recall correctly. COD: Ghosts also did that for occlusion culling. I don't think AMD PR got the memo from their driver people.
AMD is still saying it was tessellation and still saying they were rendering and tessellating water under the ground. They are turning people away from their cards, and polarizing the gaming market. They don't seem to know that they have been improving their tessellation.
You then used Tombraider launch benchmarks to prove how bad the performance was.
Nvidia didn't get the game until around launch. They didn't launch a PR campaign against AMD and Square Enix, or have a public meltdown. They apologized to their customers for the poor performance and got to work on drivers. Two weeks and no source code needed.
I would say it is quite possible he got mixed up.
90% percent of what he said was wrong. That's quite mixed up.
He probably mixed up DDR3 and GDDR3 like the console people do though. His only personal connection to gaming is getting his son an Xbox.
I'm sure Nvidia PR has NEVER made any mistakes right?
You got me there. I recall quite a few and a rather large one.. Not so many in a single interview.
He said it improves single core performance not that you are necessarily using a single core.
Quote: "In situations where a single core is a bottleneck in DX or OpenGL, um then we try to resolve that problem."
"As far as draw calls, they are supposedly working on it. DX12 will definitely alleviate much of the issue."
This should stop draw calls from causing AMD's FPS to hit the floor. It will probably help a lot with physics too. That is as there will be more CPU and less issues with latency on rendering tripping things up.
You can see it hitting AMD more here Even though it's non-deterministic it still seems close enough between cards to make some determinations about drivers.
There are way more examples I've seen showing driver overhead on AMD.. Batman for example ran way better on AMD. Well unless it was CPU physX vs CPU physx.. Project cars seems to be having some issues on AMD(only 10% of physics calculations is physx).
