NVIDIA does not support DX11.1

[w0mbat]

Source (in German): http://www.heise.de/newsticker/meldu...l-1754119.html


NVIDIA has confirmed that their Kepler CPUs (GTX 600) do not support DX11.1. The feature level is stuck with DX11_0.

Not supported DX11_1 features:

- Target-Independent Rasterization (2D-Rendering)
- 16xMSAA Rasterization (2D-Rendering)
- Orthogonal Line Rendering Mode
- UAV in non-pixel-shader stages

[PedantOne]

who cares?

[w0mbat]

Everyone who thinks it's not OK to advertise wrongfully. And I couldn't imagine what would happen if it was AMD and not NVIDIA. Everyone would be raging hard. I'm sure you too...

[PedantOne]

Nvidia: So basically, we do support 11.1 features with 11_0 feature level through the DirectX 11.1 API. We do not support feature level 11_1. This is a bit confusing, due to Microsoft naming. So we do support 11.1 from a feature level for gaming related features."

http://www.brightsideofnews.com/news...bute280a6.aspx

[Ket]

Ahaa.. well thats got to be a spanner in the M$ wheels as they are trying to "force" people into upgrading to W8 for DX11.1. Not that anybody should care about DX11.1 anyway, even if I had a GTX670 (which I almost got over my 7950) I still wouldn't care, but didn't nV advertise Keplar as supporting DX11.1 when Keplar first came out?

[w0mbat]

Nvidia: So basically, we do support 11.1 features with 11_0 feature level through the DirectX 11.1 API. We do not support feature level 11_1. This is a bit confusing, due to Microsoft naming. So we do support 11.1 from a feature level for gaming related features."

http://www.brightsideofnews.com/news...bute280a6.aspx

There you have it. No DX11.1 but they used it to advertise. That's not right.

[NEOAethyr]

I thought dx11.1 was only to add stereo 3d support api into d3d it's self.
I guess not though.
But it's not a huge deal to me.
Dx11.1 isn't out of beta yet anyways I think, at least it wasn't a week or 2 ago.

[Rollo]

So they support the gaming related features of DX11.1, and not four non gaming related features of DX11.1, on gaming cards and you're angry they advertised as being DX11.1 compliant?

Ummm, vive la revolucion, I guess....

[Jamesrt2004]

So they support the gaming related features of DX11.1, and not four non gaming related features of DX11.1, on gaming cards and you're angry they advertised as being DX11.1 compliant?

Ummm, vive la revolucion, I guess....

Some people may use those features and prefer using the 'gaming cards' though.

And really it's not for us anyway..
It's more for noobs that don't really understand hardware that 'could' have chose nvid over and cause' of the extra features

[w0mbat]

So they support the gaming related features of DX11.1, and not four non gaming related features of DX11.1, on gaming cards and you're angry they advertised as being DX11.1 compliant?

Ummm, vive la revolucion, I guess....

No, they don't support anything at all, at least in real world applications. Either you have tech level 11_1 or you don't. If you don't support all of it, it's not going to work.

Source: http://www.forum-3dcenter.org/vbulle...1&postcount=57

This guy is a game dev for AAA titles. He says it's either all or nothing.

[Lanek]

Some people may use those features and prefer using the 'gaming cards' though.

And really it's not for us anyway..
It's more for noobs that don't really understand hardware that 'could' have chose nvid over and cause' of the extra features

UAV is related to gaming ( tesselation etc).. just kepler cant do it outside compute shader type. it is gaming relevant, but i dont see anything to to jump around. the only thing is all 11.1 features supported by Kepler was allready "optional1 " in DX11.1 hardware feature ( supported by API ), the one who was not supported by API and need hardware are not supported by Kepler Nvidia. ( Look on MSDN table and look the "optional1 " in the column DX11.0. )

So basically it seems, kepler support DX11.1 features only when this is possible by API ( software ) and will have been supported by any DX11.0 hardware whatever they have DX11.1 hardware or not, when thoses features need hardware and cant use API for it they dont.

Nothing to jump around, and i will not even debate if this right or wrong to call it DX11.1 or not. ( because i dont care, we will not see thoses features used yet ).

[zanzabar]

is NV screwing up dx11 like did 10 again.

[zalbard]

Hmm, that's shady... Why not support it?
Their cards came out way later than 79x0.

[Rollo]

When my 7970 arrives, I'll be well positioned to play all those great DX11.1 games!

[zanzabar]

When my 7970 arrives, I'll be well positioned to play all those great DX11.1 games!

i cannot tell if the world is really ending next month, or if there is just a hint of sarcasm there.

[Final8ty]

DirectX 11.1 is equal to feature_level_11_1.
If they saying that they support directx 11.1 API, but with feature_level_11_0, than I'll say any DirectX 9 card supports DirectX 11.1, but with feature_level_9_1. It's the same thing. I hope you understand why this statement is stupid.


If you pass a compiled vertex, hull, domain or geometry shader that use a non-supported instruction to a create-shader function (vertex, hull, domain or geometry) on a hardware that don?t support UAVs at these stages, than the create-shader function will fails. It will also fails if the shader tries to use an UAV slot beyond the set of UAV slots that the hardware supports.

Yes. I'm already done some testing: stream output data directly from the domain shader stage. My GCN-based card can do it, but Kepler not.


Only Windows 8 support DirectX 11.1. The Windows 7 just got the runtime to speed up some functions in IE10.


It's a very well documented API, and very useful. I'm really like the shader tracing.

http://forums.anandtech.com/showthre...2#post34277712

[DilTech]

I can honestly say that nowhere on my GTX 660 Ti box does it even mention DX11.1. Then again, neither does my 7950 either.

[SKYMTL]

I just looked through every single marketing and tech slide NVIDIA sent my way since Kepler was introduced. That includes the Tech Day presentation. I see zero mention of DX11.1.

However, I distinctly remember a conversation about it. I'm going to listen through my audio recordings.

[Lanek]

I just looked through every single marketing and tech slide NVIDIA sent my way since Kepler was introduced. That includes the Tech Day presentation. I see zero mention of DX11.1.

However, I distinctly remember a conversation about it. I'm going to listen through my audio recordings.

its even in there page presentation of Kepler, and specially about the interview when Kepler was launched when they was asked about the bug in driver/card id who was showing DX11.0 only

http://pressroom.nvidia.com/easyir/c...ue&prid=865433
( its the first time i read this page from Nvidia, but really, i think they have need really change their pants, slip and hire someone for change the carpet after write it lol )

Manufactured on TSMC's new 28-nm process, with support for PCI-E Gen 3 and DX11.1

( ofc they dont say if it is by the API ( who is compatible with DX11 anyway for some features, but not all ) or hardware based DX11.1 .. so we turn in round about it.. you remember now the " we had no time for get the MS qualification ? )

Murrokapetii http://muropaketti.com/artikkelit/na...-gtx-680-gk104

we also had to ask specifically whether the GK104 GPU with DirectX 11.1 support. The answer is yes, but NVIDIA's Drew Henry (General Manager for NVIDIA GPU's PC Business Unit), the "Who cares?"

( again, this is not really important for me what features are supported on hardware or software and marketing is marketing, at first, i was not even wanted to put my words in this threads about it .. threre's no drama to make about this )..

[zalbard]

I can honestly say that nowhere on my GTX 660 Ti box does it even mention DX11.1. Then again, neither does my 7950 either.

Doesn't make it much better... The cards are recent enough to support the tech.

[Chrono Detector]

Not much of a big deal really, but I sure hope they won't pull something stupid like Assassin's Creed removal of DX 10.1, that was just plain dirty and a stupid move on their part. And at this point there are no games that even support DX 11.1, let alone a whole bunch of games still support DX9 and we won't be seeing a whole bunch of DX11 supported games coming soon anyway.

[kromosto]

isn't this a fraud? dx11.1 support means you can run dx11_1 features not using dx11.1 with dx11_0 features.

[Ket]

I can sort of see why some people would be pissed, but they shouldn't be. We won't see any games utilising DX10/11 properly until the new gen of consoles turn up... which isn't for what? Another 18 months? Ho-hum...

[kromosto]

i don't care about dx11.1 thing a little bit.

it is not important to have a dx11.1 game in short or long time ,even if there may be no dx11.1 in the future but this will not make false advertising legit. And yes everybody should get pissed even AMD gpu owners like me too.

[Ket]

Uhh.. not really. Can you see any difference between DX10 and DX10.1? No? Me neither. Its going to be exactly the same with DX11 vs DX11.1. Then theres as I say, a good 18 months before next gen consoles start to hit, only then will we seen the true potential of DX10/11, none of the advanced features such as tessellation have been properly utilised to date in PC games (just look at Heaven 3.0 with extreme tessellation and compare with games like Metro and Call of Pripyat) and not at all in console games because the consoles are extremely limited by todays standards.