# DX11 Having support for DX9 , DX10 , DX11

This topic is 3125 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Hello. I want my game to support different software and hardware platforms automatically. Example of what I want to do: * User has Windows7 - DX11 Device will be created , if user has old hardware , the device will be created with the appropriate feature level. * User has Windows Vista - If user has a DX10 compatible hardware a DX10 device will be created , if the user has only DX9 compatible hardware than a DX9 device will be created. * User has Windows XP - Only a DX9 device will be created. My question is how I determine this? How do I determine using C++ the windows ( Or the Directx version installed ) the user is running and the hardware type so I can make this selection on the application start.

##### Share on other sites
Try to create the DX11 device, and if it doesn't work, jump down one level. DX11 is available on Vista too if you get the latest updates from Windows Update (SP2 and platform update).
The problem is that if you link to D3D11 in your app, it will fail to start if the D3D11 DLLs aren't available on the system. So to get the same app running on different systems like that, you need to dynamically load D3D11.dll etc. with the LoadLibrary Function.

##### Share on other sites
Quote:
 Original post by Erik RufeltTry to create the DX11 device, and if it doesn't work, jump down one level. DX11 is available on Vista too if you get the latest updates from Windows Update (SP2 and platform update).The problem is that if you link to D3D11 in your app, it will fail to start if the D3D11 DLLs aren't available on the system. So to get the same app running on different systems like that, you need to dynamically load D3D11.dll etc. with the LoadLibrary Function.

Ok that sounds simple enough. But what about people with Windows XP? Isn't XP missing a core component (WDDM) so even loading DX11 DLL's wont help , or would it?

Thank's for the fast reply :>

##### Share on other sites
What I mean is, D3D11.dll isn't available on XP, so LoadLibrary will return an error. Which is OK, you just handle that in your app. If you add D3D11.lib in your project link dependencies however, your app will fail to start with an error box. So you need to load it dynamically, and if it fails, you load D3D10.dll or D3D9.dll instead. (For D3D10/11 you might need to load DXGI.dll also, if you want to use those functions).
Once you have a library handle, you use the GetProcAddress Function, to get a function in that library. For example if you want the D3D11CreateDevice function, you use GetProcAddress(hD3D11Lib, "D3D11CreateDevice"). That will give you the function pointer, and you use that to create your D3D11 device. After that the usage of the ID3D11Device object is the same as before.
You also have to check the return code from the function of course, since someone could put the D3D11.dll DLL on their XP system, but the D3D11CreateDevice function would fail in that case.

##### Share on other sites
Quote:

This is not entirely true. Linking D3D11.lib technically has no bearing on what happens at runtime. It's statically linked to your program at compile time. If you also set a project setting to delay-load the appropriate DLLs (in this case, D3D11.dll and friends), the DLLs won't be loaded until they are called at runtime. You don't even need to use LoadLibrary.

In addition, D3D11 supports hardware all the way down to D3D9 level hardware, so as long as the appropriate drivers are installed you only have to write one version of your code that targets D3D11 and avoids using newer features if you're running on older hardware and you can avoid integrating at least D3D10.

D3D11 is still only supported on Vista and Win7 though, so you may still want a D3D9 renderer if XP support is crucial.

##### Share on other sites
There is no reason to support dx10. It is obsolete as of dx11 and dx11 feature levels since its supported by vista and 7. The real issue you will face is whether you will support the different features such as tesselation, geometry shaders, and compute shaders. None of these are supported in dx9 if you aren't using any of these features there is no reason to use anything other than dx9. If you are you will have a lot of issue with needing many different sets of shaders and software implementations of features not supported.

##### Share on other sites
Thank's everyone. Basically I figured out what to do. I found a function (http://msdn.microsoft.com/en-us/library/ms724451%28VS.85%29.aspx) to help me figure out what windows the machine is running. If it's XP , I initiate the DX9 Renderer , if it's Vista or 7 I initiate a DX11 Device with an appropriate feature level.

##### Share on other sites
Quote:
Original post by Mike.Popoloski
Quote:

This is not entirely true. Linking D3D11.lib technically has no bearing on what happens at runtime. It's statically linked to your program at compile time. If you also set a project setting to delay-load the appropriate DLLs (in this case, D3D11.dll and friends), the DLLs won't be loaded until they are called at runtime. You don't even need to use LoadLibrary.

How does this work if the appropriate DLLs aren't available, and the program should still run?
I have very limited experience with this so perhaps I just don't understand the process, but how would I write the following for example without LoadLibrary:
#include <DXGI.h>#include <cstdio>typedef HRESULT (WINAPI * LPCREATEDXGIFACTORY1)(REFIID, void**);int main() {	HMODULE hDXGI = LoadLibrary(TEXT("dxgi.dll"));	if(hDXGI == NULL) {		DWORD dwErr = GetLastError();		printf("Failed to load dxgi.dll: %u\n", dwErr);	}	else {		LPCREATEDXGIFACTORY1 pCreateDXGIFactory1 = (LPCREATEDXGIFACTORY1)GetProcAddress(hDXGI, "CreateDXGIFactory1");		if(pCreateDXGIFactory1 == NULL) {			DWORD dwErr = GetLastError();			printf("Failed to get the CreateDXGIFactory1 function: %u\n", dwErr);		}		else {			IDXGIFactory1 *pFactory;						HRESULT hResult = pCreateDXGIFactory1(__uuidof(IDXGIFactory1), (void**)&pFactory);			if(FAILED(hResult)) {				printf("CreateDXGIFactory1 failed: 0x%08x\n", hResult);			}			else {				// Use pFactory				printf("IDXGIFactory1 created!\n");								pFactory->Release();			}		}				FreeLibrary(hDXGI);	}		return 0;}

##### Share on other sites
You use a function like the one referenced above to determine which version of Windows you are running, and if you're on a non-supported system simply be sure to not call any D3D11 functions. As long as you never call a function from the DLL, it won't try to be loaded by the OS.

##### Share on other sites
I see. It doesn't work if the system could potentially have support though, as with D3D11. DXGI.dll in this case may or may not also be version 1.1.

• 10
• 17
• 9
• 14
• 41
• ### Similar Content

• By cozzie
Hi all,
It's been a while since I've been working on my HLSL shaders, and found out I'm not 100% sure if I'm applying gamma correctness correctly. So here's what I do:
- create backbuffer in this format: DXGI_FORMAT_R8G8B8A8_UNORM_SRGB
- source textures (DDS) are always in SRGB format
- this way the textures should be gamma correct, because DX11 helps me out here
Now my question is about material and light colors. I'm not sure if I need to convert those to linear space. The colors are handpicked on screen, so I guess gamma correct. Below are 2 screenshots, the darker is including converting those colors (return float4(linearColor.rgb * linearColor.rgb, linearColor.a);), in the lighter shot I didn't do this conversion.
These are the properties of the brick material and the light source (there are no other lightsources in the scene, also no global ambient):
Material:
CR_VECTOR4(0.51f, 0.26f, 0.22f, 1.0f), // ambient CR_VECTOR4(0.51f, 0.26f, 0.22f, 1.0f), // diffuse RGB + alpha CR_VECTOR4(0.51f, 0.26f, 0.22f, 4.0f)); // specular RGB + power Directional light:
mDirLights[0].Ambient = CR_VECTOR4(0.1f, 0.1f, 0.1f, 1.0f); mDirLights[0].Diffuse = CR_VECTOR4(0.75f, 0.75f, 0.75f, 1.0f); mDirLights[0].Specular = CR_VECTOR4(1.0f, 1.0f, 1.0f, 16.0f); mDirLights[0].Direction = CR_VECTOR3(0.0f, 1.0f, 0.0f);
So in short, should I or should I not do this conversion in the lighting calculation in the shader? (and/or what else are you seeing :))
Note that I don't do anything with the texture color, after it's fetched in the shader (no conversions), which I believe is correct.

• By chiffre
Introduction:
In general my questions pertain to the differences between floating- and fixed-point data. Additionally I would like to understand when it can be advantageous to prefer fixed-point representation over floating-point representation in the context of vertex data and how the hardware deals with the different data-types. I believe I should be able to reduce the amount of data (bytes) necessary per vertex by choosing the most opportune representations for my vertex attributes. Thanks ahead of time if you, the reader, are considering the effort of reading this and helping me.
I found an old topic that shows this is possible in principal, but I am not sure I understand what the pitfalls are when using fixed-point representation and whether there are any hardware-based performance advantages/disadvantages.
(TLDR at bottom)
The Actual Post:
To my understanding HLSL/D3D11 offers not just the traditional floating point model in half-,single-, and double-precision, but also the fixed-point model in form of signed/unsigned normalized integers in 8-,10-,16-,24-, and 32-bit variants. Both models offer a finite sequence of "grid-points". The obvious difference between the two models is that the fixed-point model offers a constant spacing between values in the normalized range of [0,1] or [-1,1], while the floating point model allows for smaller "deltas" as you get closer to 0, and larger "deltas" the further you are away from 0.
To add some context, let me define a struct as an example:
struct VertexData { float[3] position; //3x32-bits float[2] texCoord; //2x32-bits float[3] normals; //3x32-bits } //Total of 32 bytes Every vertex gets a position, a coordinate on my texture, and a normal to do some light calculations. In this case we have 8x32=256bits per vertex. Since the texture coordinates lie in the interval [0,1] and the normal vector components are in the interval [-1,1] it would seem useful to use normalized representation as suggested in the topic linked at the top of the post. The texture coordinates might as well be represented in a fixed-point model, because it seems most useful to be able to sample the texture in a uniform manner, as the pixels don't get any "denser" as we get closer to 0. In other words the "delta" does not need to become any smaller as the texture coordinates approach (0,0). A similar argument can be made for the normal-vector, as a normal vector should be normalized anyway, and we want as many points as possible on the sphere around (0,0,0) with a radius of 1, and we don't care about precision around the origin. Even if we have large textures such as 4k by 4k (or the maximum allowed by D3D11, 16k by 16k) we only need as many grid-points on one axis, as there are pixels on one axis. An unsigned normalized 14 bit integer would be ideal, but because it is both unsupported and impractical, we will stick to an unsigned normalized 16 bit integer. The same type should take care of the normal vector coordinates, and might even be a bit overkill.
struct VertexData { float[3] position; //3x32-bits uint16_t[2] texCoord; //2x16bits uint16_t[3] normals; //3x16bits } //Total of 22 bytes Seems like a good start, and we might even be able to take it further, but before we pursue that path, here is my first question: can the GPU even work with the data in this format, or is all I have accomplished minimizing CPU-side RAM usage? Does the GPU have to convert the texture coordinates back to a floating-point model when I hand them over to the sampler in my pixel shader? I have looked up the data types for HLSL and I am not sure I even comprehend how to declare the vertex input type in HLSL. Would the following work?
struct VertexInputType { float3 pos; //this one is obvious unorm half2 tex; //half corresponds to a 16-bit float, so I assume this is wrong, but this the only 16-bit type I found on the linked MSDN site snorm half3 normal; //same as above } I assume this is possible somehow, as I have found input element formats such as: DXGI_FORMAT_R16G16B16A16_SNORM and DXGI_FORMAT_R16G16B16A16_UNORM (also available with a different number of components, as well as different component lengths). I might have to avoid 3-component vectors because there is no 3-component 16-bit input element format, but that is the least of my worries. The next question would be: what happens with my normals if I try to do lighting calculations with them in such a normalized-fixed-point format? Is there no issue as long as I take care not to mix floating- and fixed-point data? Or would that work as well? In general this gives rise to the question: how does the GPU handle fixed-point arithmetic? Is it the same as integer-arithmetic, and/or is it faster/slower than floating-point arithmetic?
Assuming that we still have a valid and useful VertexData format, how far could I take this while remaining on the sensible side of what could be called optimization? Theoretically I could use the an input element format such as DXGI_FORMAT_R10G10B10A2_UNORM to pack my normal coordinates into a 10-bit fixed-point format, and my verticies (in object space) might even be representable in a 16-bit unsigned normalized fixed-point format. That way I could end up with something like the following struct:
struct VertexData { uint16_t[3] pos; //3x16bits uint16_t[2] texCoord; //2x16bits uint32_t packedNormals; //10+10+10+2bits } //Total of 14 bytes Could I use a vertex structure like this without too much performance-loss on the GPU-side? If the GPU has to execute some sort of unpacking algorithm in the background I might as well let it be. In the end I have a functioning deferred renderer, but I would like to reduce the memory footprint of the huge amount of vertecies involved in rendering my landscape.
TLDR: I have a lot of vertices that I need to render and I want to reduce the RAM-usage without introducing crazy compression/decompression algorithms to the CPU or GPU. I am hoping to find a solution by involving fixed-point data-types, but I am not exactly sure how how that would work.
• By cozzie
Hi all,
I was wondering it it matters in which order you draw 2D and 3D items, looking at the BeginDraw/EndDraw calls on a D2D rendertarget.
The order in which you do the actual draw calls is clear, 3D first then 2D, means the 2D (DrawText in this case) is in front of the 3D scene.
The question is mainly about when to call the BeginDraw and EndDraw.
Note that I'm drawing D2D stuff through a DXGI surface linked to the 3D RT.
Option 1:
A - Begin frame, clear D3D RT
B - Draw 3D
C - BeginDraw D2D RT
D - Draw 2D
E - EndDraw D2D RT
F - Present
Option 2:
A - Begin frame, clear D3D RT + BeginDraw D2D RT
B - Draw 3D
C - Draw 2D
D - EndDraw D2D RT
E- Present
Would there be a difference (performance/issue?) in using option 2? (versus 1)
Any input is appreciated.

• Do you know any papers that cover custom data structures like lists or binary trees implemented in hlsl without CUDA that work perfectly fine no matter how many threads try to use them at any given time?
• By cozzie
Hi all,
Last week I noticed that when I run my test application(s) in Renderdoc, it crashes when it enable my code that uses D2D/DirectWrite. In Visual Studio no issues occur (debug or release), but when I run the same executable in Renderdoc, it crashes somehow (assert of D2D rendertarget or without any information). Before I spend hours on debugging/ figuring it out, does someone have experience with this symptom and/or know if Renderdoc has known issues with D2D? (if so, that would be bad news for debugging my application in the future );
I can also post some more information on what happens, code and which code commented out, eliminates the problems (when running in RenderDoc).
Any input is appreciated.