Caporegime
- Joined
- 18 Oct 2002
- Posts
- 33,188
AMD did exactly the same thing with shogun 2 and the Dirt series so both are as bad as each other.
AMD did what exactly with either games? They helped them code it and add DX11 features? Were these locked out to Nvidia, no, did they cripple Nvidia speed, no Nvidia was faster in Dirt 2 using the code AMD helped implement.
Ready what is being talked about Assassins Creed HAD dx10.1 in it, AMD was 15-20% faster with DX10.1 than plain DX10, Nvidia then asked Ubisoft to REMOVE DX10.1 as their hardware couldn't do it, thus Nvidia and AMD both had to use DX10 and AMD lose 15-20% of its speed.
Ah yes, the good old, "I don't understand X and my favourite card manufacturer is losing out cos of X so it must be NVIDIA's fault" argument.
Direct3D 11 deferred context command lists are a multi-threading feature in DirectX 11 defined by microsoft that NVIDIA added driver support for in CUDA 4.0 (iirc). If AMD is limping along on this front without driver support for a multithreading DX11 feature (and they claim to be all up in DX11!) it's their own damn fault. Sheesh! The level of fanboism here is ridiculous.
No, the level of your fanboyism is ridiculous, its absolutely and without question known that Nvidia did this, you're talking about DX11 while quoting and responding to a post about a DX10.1 game that had it removed in a patch after launch despite DX10.1 working perfectly on the only hardware to support it, AMD's.
As always you use one completely irrelevant example to have a go at another.
Sometimes Nvidia will be faster in a game, to pretend Nvidia don't actively try and kill AMD performance is to be utterly utterly blind. Or are you one of the Nvidia fans who thinks the tessellation in Crysis 2, which is done WAY beyond a point Nvidia cards can make any IQ benefit, was entirely for the end user, despite the performance drop on Nvidia's own cards while pushing super high tessellation its own users couldn't see?