NVIDIA Kepler not fully compliant with DirectX 11.1

Sh1t son I got dx 11.2 ya all wanna see it?

These unsupported features seem to only concern some future professional applications - I'm pretty much sure they'll want to use that to differentiate cards between gamer GeForce and workstation Quadro / Tesla.

......Kepler supports UAVs in pixel and compute shaders. But not in tessellation related (hull and domain shader) or any other shader type before the rasterizers. And in my opinion, that is gaming relevant. Use of UAVs in vertex, geometry, hull and domain shaders have no potential use for anything outside of gaming. Where else does one use this shader types? So nV's claim they support all gaming relevant DX11.1 features is plain wrong in my opinion.
If I'm not mistaken, they don't support a single feature of level 11_1 which is not optional for level 11_0.......

..... It might just be that Microsoft didn't want UAV acces by all shader types to be a new option for level 11_0. If Kepler doesn't support 64 UAV or TIR or anything else from level 11_1, there is no way for Nvidia to expose UAV access by all shader types......

.... UAV is a random access (read | write) view on a buffer. You can do scattered writes to an UAV fe. You can already render out into UAVs if you want in 11.0
I think you can not go without RT _and_ DS (+UAV) in 11.0, because then the whole pipeline goes to sleep basically. I'd say the "feature" it's really only a guarantee that nothing just turns off, you should be able to do the feature itself without problems if your hardware isn't a bit inflexible.
nVidias problem is likely the 64 UAVs, not that you can't turn off RT & DS together.....

..... You also loose the resolution-information when you don't have a RT&DS bound, there it goes hand in hand with the "Target-Independent Rasterization" feature of DirectX 11.1.....

AMD is running out of money. Most of us consider that "dying"....