Sign in to follow this  

DX11 Can i program DirectX11 on a GeForce 8800GTX?

Recommended Posts

Iam going through some DX11 tutorials and as soon as i am going to draw with Shaders the program crashes.
When i declarate these functions with D3DX10CreateEffectFromFile it works, but when using D3DX11CompileFromFile there is a crash on the dev->Draw Method.

Is this because my Card is not DirectX 11 compatible?

Sigh... Mr Murphy don´t want me to make games...
I was happy with my engine untill i saw soft shadowmapping shadows... i want them in my engine!!! =)

If this is the case, which DX11 card is best (not ATI, i want nVidia) for around 200$?

Share this post

Link to post
Share on other sites
GeForce 8x doesn't support shader model 5 but however you can D3D11 by specifying D3D_FEATURE_LEVEL_10_0 when calling D3D11CreateDeviceAndSwapChain and user shader model 4

Share this post

Link to post
Share on other sites
Hm ok, but this means i have to change all my shaders to and stuff like this:

[source lang="cpp"]D3DX11CompileFromFile(L"shaders.hlsl", 0, 0, "VShader", "fx_4_0", 0, 0, 0, &VS, 0, 0);
D3DX11CompileFromFile(L"shaders.hlsl", 0, 0, "PShader", "fx_4_0", 0, 0, 0, &PS, 0, 0);
// encapsulate both shaders into shader objects
dev->CreateVertexShader(VS->GetBufferPointer(), VS->GetBufferSize(), NULL, &pVS);
dev->CreatePixelShader(PS->GetBufferPointer(), PS->GetBufferSize(), NULL, &pPS);

wont work i guess?

Share this post

Link to post
Share on other sites
Hello KurtO, just so you know (because it is actually a little counter-intuitive) your 8-series card [i]may[/i] support compute shaders, even though with some limitations. So you may want to give them a try, they could be useful to achieve some smoothing effects. You can refer to this thread for more info on this topic.


Basically as Asesh said the DirectX 11 API can be used to program DirectX 10 and even DirectX 9 hardware, but all the features you use must be available on that hardware, so DirectX 11 adds nohing in terms of functionality to these cards [i]except[/i] compute shaders, which actually work (I used to program them on my G210, DirectX 10 card).

Share this post

Link to post
Share on other sites
Thank you damix911, i was wrong, i didnt think you could use the DirectX11 API at all, but this is not the case. Luckily i didnt buy a new card and i will continue develop DirectX11 on my 8800GTX card.
The limitation is not in my hardware at this moment, it is in my brain trying to understand all the math and physics! =) hehe

I have trouble today with Soft shadow mapping and i have seen some examples in DX11 so that is why i am jumping the ship from DX9.
I also like the whole new API with shaders for rendering and i think it is convinient to have the shaders do lot of the "SetRendering" Flags that you had to do in DX9.

So onve again, thanks for your help and if anyone find a nice "simple" soft shadow mapping sample, please let me know! =)

Share this post

Link to post
Share on other sites
Tessellation and "full" compute shaders are cool, though [img][/img]

Take a look at the DX SDK June 2010 samples (not sure if Windows SDK still has them as they were). There are several shadow samples; though the most advanced ones require SM5 to run efficiently, and require more GPU work if implemented in earlier models. Edited by Nik02

Share this post

Link to post
Share on other sites
Nik02, ihave tried with lmost all of the SDK samples, but i hate when they work with DXUtil.
I want full understanding and it takes so much time to understand all the Util-Functions that are used. And also there is always proppet with all kinds of features, lots of option and different techniques.

I would like basic sample that is easy to follow with just a plane and some simple meshes / primitives.

I think the basic problem is that i have to poor understanding of shaders and DX11 but i am doing lots of DX11 tutorials, and shaders are COOOOOOL and i cant imagine to program now without them.

But like you i also think tessellation and "full" shaders are cool! =) But i am not there yet in my knowledge. heheh

Share this post

Link to post
Share on other sites
The utility stuff in samples is usually used so as to reduce the amount of so-called "boilerplate" code - functionality that a general DX sample app needs to do anyway. The actual techniques demonstrated in the SDK samples are largely independent from the utility classes. Most of the "meat" is in the shader and effect files.

Soft shadowing is a relatively advanced concept, but if you have a good understanding on how to do shadow maps and blurring as independent techniques, it is not extremely difficult to combine them. Both general shadow mapping and blurring have lots of examples floating around the 'net.

Be sure to check the NVidia, AMD and Intel developer sites for more GPU samples as well.

Share this post

Link to post
Share on other sites
I think i understand the concept, but there are so many steps, and everything has to be 100% precise for this to work (syntax, shaders and pixelshader and states), But i will definetly try one of those demos and then try to implement shadows to my engine.

Share this post

Link to post
Share on other sites
Yea, you need some highly abstract thinking to truly understand shadow mapping; in particular, the relation to the "camera" and "light" spaces. Once you do understand it, the code itself is not too difficult. Same applies to blurring. Soft shadows are generally implemented as shadow maps with variable blur width based on distance or occlusion criteria (though this is not the only way).

You can use PIX to inspect the intermediate render targets (such as the shadow depth map), if you find that your technique doesn't work in an expected way. Once you see the device state visually, it is much easier to determine what's wrong (if anything). Edited by Nik02

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