Which version of DirectX 11 does my rig support?

[futurefields]

Hey guys, sorry for the noob question but I am really confused as to what the max version of DirectX 11 I can support is?

Windows 7 x64
7950 Boost 3GB

???

 

[desprado]

Dx 11.2

 

[tollingalong]

To check which version of DirectX is on your computer

Open DirectX Diagnostic Tool by clicking the Start button Picture of the Start button, typing dxdiag in the search box, and then pressing Enter.

Click the System tab, and then, under System Information, check the DirectX version number.

http://windows.microsoft.com/en-us/windows/which-version-directx#which-version-directx=windows-7

 

[futurefields]

it says I have DirectX 11

 

[f1sherman]

And you do.
What's your main concern over this? There should be none.

You GPU is fully DX11.2 hw compliant,
with 1 or 2 sw thingies missing due to AMD not implementing it in their driver.

Your GPU has identical DX feature list as AMD newest GPU R9 290/X/285

They said it will have DX12 support, unlike HD6000

 

[bystander36]

To get 11.1 or 11.2, you need Windows 8.x (not sure on specific versions).

 

[ViRGE]

Direct3D 11. Feature level 11_0.

 

[ShintaiDK]

Direct3D 11. Feature level 11_0.

^^ This.

The max archiveable on a 7950 is Feature level 11.1 with windows 8/9.

 

[BrentJ]

You can install DX 11.1 for Windows 7.

http://support.microsoft.com/kb/179113

DirectX 11.1 for Windows 7 SP1 and Windows Server 2008 R2 SP1:
Platform Update for Windows 7 and Windows Server 2008 (KB2670838)

Windows 8.0 includes DX 11.1. To get DX 11.2 you need Windows 8.1.

 

[ShintaiDK]

The platform update is not fully DX11.1. Its only partial.

Portions of the “DirectX 11.1 Runtime” are being made available on Windows 7 Service Pack 1 via the Platform Update for Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1 (KB 2670838)

 

[ViRGE]

The platform update is not fully DX11.1. Its only partial.

Which brings up a great opportunity for a story regarding that from Max McMullen, the current development lead for D3D.

If the goal is to describe which API methods function fully I could further throw another complicating factor by considering OS version and WDDM version. A classic example of this is the Direct3D 11.1 API Platform Update for Windows 7, where my team brought the 11.1 API from Windows 8 back to Windows 7. There was a lot of negative press about the 11.1 hardware features not being supported on Windows 7 in that platform update, along with a significant amount of speculation in the press that the hardware features were turned off to create a need to upgrade to Windows 8. The actual truth is my team engineered the platform update to have full support for the hardware features in feature level 11.1. Exposing those hardware features requires the runtime query a new WDDM version and function table from the user mode drivers. When my team went into testing for the platform update, a significant number of hybrid laptop drivers and unsupported wrapper drivers for things like USB displays behaved erratically when a new driver version was queried. After months of ordering more laptops and devices to test, I eventually pulled the plug on querying a new WDDM version to resolve the remaining driver compatibility issues. The cost was too great for the features being added. Even if my team managed to keep the driver query intact, some APIs like EnqueueSetEvent on DXGI wouldn't work without an update to the kernel or a change in design for Windows 7. Such APIs were left disabled in the platform update based on "bang for buck" of dev effort.

 

[BFG10K]

That's a good insider snippet from Microsoft. One can certainly bash them about Metro, but not about DirectX being locked to "force" Windows upgrades.

The tight coupling to WDDM (by design) means back-porting to older Windows platforms is non-trivial given kernel and/or platform changes are often required.

 

[Spjut]

That's a good insider snippet from Microsoft. One can certainly bash them about Metro, but not about DirectX being locked to "force" Windows upgrades.

The tight coupling to WDDM (by design) means back-porting to older Windows platforms is non-trivial given kernel and/or platform changes are often required.

My understanding of this is very limited, but I don't get why Microsoft does it like that.
Both OpenGL 4.4 and Mantle work on older versions of Windows, and can expose more than DX11.x does.

I get that DX11.x already is tied to WDDM, but Microsoft could make DX12 work in the same way as OpenGL and Mantle.

 

[BFG10K]

My understanding of this is very limited, but I don't get why Microsoft does it like that.

One reason is for the Windows GUI rendering. DWM is essentially a full-screen hardware accelerated Direct3D application.

There are probably other reasons too, like performance and stability.

Both OpenGL 4.4 and Mantle work on older versions of Windows, and can expose more than DX11.x does.

These APIs do not perform underlying OS functions or integrate into the kernel.

I get that DX11.x already is tied to WDDM, but Microsoft could make DX12 work in the same way as OpenGL and Mantle.

So far it's looking like DX12 will be coupled to WDDM 2.0.

 

[futurefields]

And you do.
What's your main concern over this? There should be none.

You GPU is fully DX11.2 hw compliant,
with 1 or 2 sw thingies missing due to AMD not implementing it in their driver.

Your GPU has identical DX feature list as AMD newest GPU R9 290/X/285

They said it will have DX12 support, unlike HD6000

see Bystanders post for the answer to your first question

 

[loccothan]

Yep in Win8.1 Will be Full Hardware DX11.x (DX11.1 11.2 and 11.3)
Then Will Be Full DX12 (Win9?)
All for GCN Cards

 

[futurefields]

So the highest version my rig supports currently is 11.0 since you need 8.1 for 11.1+

thanks guys!

 

[Dylanharvey999]

Direct3D 11. Feature level 11_0.

:awe:

This

 

[futurefields]

is there a list of games running 11.1? tried to find one but all I could confirm is that Battlefield 4 uses it.