Sign in to follow this  

DX11 Is Xna Still Required If I Migrate From Dx9 To Dx11 Using C#?

Recommended Posts

I notice there is a package called XNA that used to be required to run games on windows 7 platform with DX11....

I think it's a SDK package, but sometimes, when running certain games, the game fails to start if

I didn't install the XNA even though I am not writing any code.


Despite of the new Windows 10 OS, if I still use windows 7 and targeted at 7, should I install the XNA SDK?


I am asking this because the default SDK which comes from VS2013 already has a fairly good coverage.




Edited by lucky6969b

Share this post

Link to post
Share on other sites
Despite of the new Windows 10 OS, if I still use windows 7 and targeted at 7, should I install the XNA SDK?


I would have to say whether or not you decide to install it really depends on how comfortable you are with using DirectX11 because you do not require XNA to use DirectX11. But you can still use Windows 10 and XNA there is a fix for that now if you plan on using XNA instead.

Edited by dvds414

Share this post

Link to post
Share on other sites

XNA helping you for DX11 is coincidence. XNA was built on top of DX9 and possibly it's installation installed something else you needed like the DX9 SDK or something.


Microsoft stopped supporting XNA and the MonoGame team took it over. They ported it to DX11 and it now is based off DX11 with the advantage of Shader Model 5.


XNA/MonoGame is a C#.Net "wrapper" for DirectX. If you want a little bit easier way to work up to DirectX, XNA and MonoGame are a superb way to do it largely because of the great XNA 3 books that were published. Once you really have a solid understanding of things in MonoGame/XNA it's a lot easier to start doing DirectX.


DirectX in no shape form or fashion needs MonoGame or XNA to be installed. Quite the reverse in that they run on top of DirectX.


DirectX is more meant for C++ programming although some have managed to make it work using other programming languages such as SharpDX which uses C# but is not that well documented.


One thing you may be getting confused on is that in order to do DX11 in Windows 7 you have to have two copies of DirectX installed. DirectX is now part of the Windows SDK which is basically pre-installed. And if you're in Win10 that's great. But in Windows 7 it doesn't work for a lot of stuff. You actually have to have a second copy of DirectX installed, from what I've experienced. So, you install the old DirectX SDK in addition to the Windows SDK that's already installed. It's kind of confusing, and I think Microsoft wanted it to be that way because they want to do anything in their power to force you to stop using anything before Windows 8. But if you get both installed you can do DX11 in Windows 7.


So, the bottom line is that you should never have to install XNA in order to program DX11. It may be installing the DirectX SDK and that may be what you are experiencing. And in order to do DX11 in Win7 you have to install the DX SDK in addition to the Windows SDK even though DX is built into the Windows SDK.

Edited by BBeck

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

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By evelyn4you
      i have read very much about the binding of a constantbuffer to a shader but something is still unclear to me.
      e.g. when performing :   vertexshader.setConstantbuffer ( buffer,  slot )
       is the buffer bound
      a.  to the VertexShaderStage
      b. to the VertexShader that is currently set as the active VertexShader
      Is it possible to bind a constantBuffer to a VertexShader e.g. VS_A and keep this binding even after the active VertexShader has changed ?
      I mean i want to bind constantbuffer_A  to VS_A, an Constantbuffer_B to VS_B  and  only use updateSubresource without using setConstantBuffer command every time.

      Look at this example:
      SetVertexShader ( VS_A )
      vertexshader.setConstantbuffer ( buffer_A,  slot_A )
      perform drawcall       ( buffer_A is used )

      SetVertexShader ( VS_B )
      vertexshader.setConstantbuffer ( buffer_B,  slot_A )
      perform drawcall   ( buffer_B is used )
      SetVertexShader ( VS_A )
      perform drawcall   (now which buffer is used ??? )
      I ask this question because i have made a custom render engine an want to optimize to
      the minimum  updateSubresource, and setConstantbuffer  calls
    • By noodleBowl
      I got a quick question about buffers when it comes to DirectX 11. If I bind a buffer using a command like:
      IASetVertexBuffers IASetIndexBuffer VSSetConstantBuffers PSSetConstantBuffers  and then later on I update that bound buffer's data using commands like Map/Unmap or any of the other update commands.
      Do I need to rebind the buffer again in order for my update to take effect? If I dont rebind is that really bad as in I get a performance hit? My thought process behind this is that if the buffer is already bound why do I need to rebind it? I'm using that same buffer it is just different data
    • By Rockmover
      I am really stuck with something that should be very simple in DirectX 11. 
      1. I can draw lines using a PC (position, colored) vertices and a simple shader just fine.
      2. I can draw 3D triangles using PCN (position, colored, normal) vertices just fine (even transparency and SpecularBlinnPhong shaders).
      However, if I'm using my 3D shader, and I want to draw my PC lines in the same scene how can I do that?
      If I change my lines to PCN and pass them to the 3D shader with my triangles, then the lighting screws them all up.  I only want the lighting for the 3D triangles, but no SpecularBlinnPhong/Lighting for the lines (just PC). 
      I am sure this is because if I change the lines to PNC there is not really a correct "normal" for the lines.  
      I assume I somehow need to draw the 3D triangles using one shader, and then "switch" to another shader and draw the lines?  But I have no clue how to use two different shaders in the same scene.  And then are the lines just drawn on top of the triangles, or vice versa (maybe draw order dependent)?  
      I must be missing something really basic, so if anyone can just point me in the right direction (or link to an example showing the implementation of multiple shaders) that would be REALLY appreciated.
      I'm also more than happy to post my simple test code if that helps as well!
    • By Reitano
      I am writing a linear allocator of per-frame constants using the DirectX 11.1 API. My plan is to replace the traditional constant allocation strategy, where most of the work is done by the driver behind my back, with a manual one inspired by the DirectX 12 and Vulkan APIs.
      In brief, the allocator maintains a list of 64K pages, each page owns a constant buffer managed as a ring buffer. Each page has a history of the N previous frames. At the beginning of a new frame, the allocator retires the frames that have been processed by the GPU and frees up the corresponding space in each page. I use DirectX 11 queries for detecting when a frame is complete and the ID3D11DeviceContext1::VS/PSSetConstantBuffers1 methods for binding constant buffers with an offset.
      The new allocator appears to be working but I am not 100% confident it is actually correct. In particular:
      1) it relies on queries which I am not too familiar with. Are they 100% reliable ?
      2) it maps/unmaps the constant buffer of each page at the beginning of a new frame and then writes the mapped memory as the frame is built. In pseudo code:
 = device.Map(page.buffer)
          Alloc(size, initData)
              memcpy( + page.start, initData, size)
          Alloc(size, initData)
              memcpy( + page.start, initData, size)
      (Note: calling Unmap at the end of a frame prevents binding the mapped constant buffers and triggers an error in the debug layer)
      Is this valid ? 
      3) I don't fully understand how many frames I should keep in the history. My intuition says it should be equal to the maximum latency reported by IDXGIDevice1::GetMaximumFrameLatency, which is 3 on my machine. But, this value works fine in an unit test while on a more complex demo I need to manually set it to 5, otherwise the allocator starts overwriting previous frames that have not completed yet. Shouldn't the swap chain Present method block the CPU in this case ?
      4) Should I expect this approach to be more efficient than the one managed by the driver ? I don't have meaningful profile data yet.
      Is anybody familiar with the approach described above and can answer my questions and discuss the pros and cons of this technique based on his experience ? 
      For reference, I've uploaded the (WIP) allocator code at  Feel free to adapt it in your engine and please let me know if you spot any mistakes
      Stefano Lanza
    • By Matt Barr
      Hey all. I've been working with compute shaders lately, and was hoping to build out some libraries to reuse code. As a prerequisite for my current project, I needed to sort a big array of data in my compute shader, so I was going to implement quicksort as a library function. My implementation was going to use an inout array to apply the changes to the referenced array.

      I spent half the day yesterday debugging in visual studio before I realized that the solution, while it worked INSIDE the function, reverted to the original state after returning from the function.

      My hack fix was just to inline the code, but this is not a great solution for the future.  Any ideas? I've considered just returning an array of ints that represents the sorted indices.
  • Popular Now