Sign in to follow this  

DX11 Updating engine from dx9 to dx11

Recommended Posts

LevyDee    377
I have been building a home grown engine for a few years now just as a hobby using dx9, so not working on it full time. So my question is, eventually I will need to update to directx11, and was just curious if someone with experience could enlighten me how difficult this could be. Really just changing how you use the d3ddevice right? I am already using a programmable pipeline, so that wont be an issue, but are there any other big challenges involved? Thanks.

Share this post

Link to post
Share on other sites
Narf the Mouse    322
Make sure all your effect files designate row_major - Matrices (float4x4) are row major by default in DX9, and column major (matrix) in DX10 and DX11.

More generally speaking, my own game engine seems to be working fine just wrapping DX9, D10 and DX11 in genericized classes. Ideally, only the smallest possible part of the foundation of your engine should even know it's using DirectX, or which version.

If you've built it along good "separation of concerns" lines, you should be able to swap out that small subset. You could even put it in a DLL - DX9API.dll, DX10API.dll, DX11API.dll. Then, when/if you get your hands on DX12, or OpenGL, or whatever, you can swap in a DX12API.dll, OpenGLAPI.dll (not familiar with OpenGL version numbers) or, I dunno, AsYetUninventedConsoleAPI.dll.

In short, there's no reason even so much as your Mesh class/struct should have a clue what you're using - Leave that to your VertexBuffer and IndexBuffer classes.

Share this post

Link to post
Share on other sites
Hodgman    51345
Two of the biggest differences to me are -
* DX9 vertex declarations are forgiving in that they can be slightly incorrect and still work. DX11 input layouts on the other hand need to exactly match your vertex shader input structure. This means that if the same mesh is drawn using 2 shaders, you may need 2 input layouts.
* DX11 render states are immutable objects. E.g. You can't just set "depth test = less" at any time, instead you've got to create a complete depth-stencil-state object ahead of time. If porting a DX9 engine, you might need to create a bunch of large tables/maps of state objects in advance.
[quote name='Narf the Mouse' timestamp='1348979191' post='4985261']Make sure all your effect files designate row_major - Matrices (float4x4) are row major by default in DX9, and column major (matrix) in DX10 and DX11.[/quote]I don't know about D3DX math, but the HLSL compiler hasn't changed in that column_major is the default float4x4 layout in DX9 too.

Share this post

Link to post
Share on other sites
mhagain    13430
A third major difference I'd highlight is use of constant buffers instead of free-standing constants in HLSL code. Depending how you've currently got things set up that may result in a good deal of re-thinking, re-organizing and re-writing.

There are also many smaller, more subtle differences throughout the two versions, such as the differences between Lock and Map, and these can sometimes trip you up.

Around the release of D3D10 the major GPU vendors published sets of slides outlining advice and trouble-spots to look out for, and these are still quite relevant to D3D11 and worth reading. Here's a good overview:

Share this post

Link to post
Share on other sites
MJP    19791
The initial port probably won't be too hard for you. It's not too hard to spend a week or two and get a DX9 renderer working on DX11. What's harder is actually making it run fast (or faster), and integrating the new functionality that DX11 offers you. Constant buffers are usually the biggest performance problem for a quick and dirty port, since using them to emulate DX9 constant registers can actually be slower than doing the same thing in DX9. Past that you may need a lot of re-writing for things like handling structured buffers instead of just textures everywhere, having texturs/buffers bound to all shader stages, changing shaders to use integer ops or more robust branching/indexing, and so on. Edited by MJP

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Partner Spotlight

  • Similar Content

    • By RubenRS
      How do i open an image to use it as Texture2D information without D3DX11CreateShaderResourceViewFromFile? And how it works for different formats like (JPG, PNG, BMP, DDS,  etc.)?
      I have an (512 x 512) image with font letters, also i have the position and texcoord of every letter. The main idea is that i want to obtain the image pixel info, use the position and texcoords to create a new texture with one letter and render it. Or am I wrong in something?
    • By thmfrnk
      I found a very interesting blog post here:
      However, I didn't really got how to use his "TestConeVsSphere" test in 3D (last piece of code on his post). I have the frustumCorners of a 2D Tile cell in ViewSpace and my 3D Cone Origin and Direction, so where to place the "testSphere"? I thought about to also move the Cone into viewspace and put the sphere to the Center of the Cell with the radius of half-cellsize, however what about depth? A sphere does not have inf depth?
      I am missing anything? Any Ideas?
      Thx, Thomas
    • By Modymek
      hi all
      I want to enable and disable shader in MPCH Media player Classic
      the MPCH have shader option using HLSL shaders
      I want the shader to read each file extension before it plays the file
      so if the video file name is video.GR.Mp4 it will play it in Grayscale shader 
      if it is not and standard file name Video.Mp4 without GR. unique extension so it plays standard without shader or end the shader
      here is the shader I have for grayscale
      // $MinimumShaderProfile: ps_2_0
      sampler s0 : register(s0);
      float4 main(float2 tex : TEXCOORD0) : COLOR {
          float c0 = dot(tex2D(s0, tex), float4(0.299, 0.587, 0.114, 0));
          return c0;
      I want to add if or block stantement or bloean to detect file name before it call the shader in order to go to the procedure or disable it or goto end direct without it
      any thoughts or help
    • By noodleBowl
      I've gotten to part in my DirectX 11 project where I need to pass the MVP matrices to my vertex shader. And I'm a little lost when it comes to the use of the constant buffer with the vertex shader
      I understand I need to set up the constant buffer just like any other buffer:
      1. Create a buffer description with the D3D11_BIND_CONSTANT_BUFFER flag 2. Map my matrix data into the constant buffer 3. Use VSSetConstantBuffers to actually use the buffer But I get lost at the VertexShader part, how does my vertex shader know to use this constant buffer when we get to the shader side of things
      In the example I'm following I see they have this as their vertex shader, but I don't understand how the shader knows to use the MatrixBuffer cbuffer. They just use the members directly. What if there was multiple cbuffer declarations like the Microsoft documentation says you could have?
      //Inside vertex shader cbuffer MatrixBuffer { matrix worldMatrix; matrix viewMatrix; matrix projectionMatrix; }; struct VertexInputType { float4 position : POSITION; float4 color : COLOR; }; struct PixelInputType { float4 position : SV_POSITION; float4 color : COLOR; }; PixelInputType ColorVertexShader(VertexInputType input) { PixelInputType output; // Change the position vector to be 4 units for proper matrix calculations. input.position.w = 1.0f; // Calculate the position of the vertex against the world, view, and projection matrices. output.position = mul(input.position, worldMatrix); output.position = mul(output.position, viewMatrix); output.position = mul(output.position, projectionMatrix); // Store the input color for the pixel shader to use. output.color = input.color; return output; }  
    • By gomidas
      I am trying to add normal map to my project I have an example of a cube: 
      I have normal in my shader I think. Then I set shader resource view for texture (NOT BUMP)
                  device.ImmediateContext.PixelShader.SetShaderResource(0, textureView);             device.ImmediateContext.Draw(VerticesCount,0); What should I do to set my normal map or how it is done in dx11 generally example c++?
  • Popular Now