• Advertisement
Sign in to follow this  

DX11 DX Nov SDK is out (with D3D11 Preview)

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

If you intended to correct an error in the post then please contact us.

Recommended Posts

The new November DX SDK is out, available here: http://www.microsoft.com/downloads/details.aspx?FamilyID=5493f76a-6d37-478d-ba17-28b1cca4865a&DisplayLang=en. This includes a new DX11 Technical Preview. Here are the release notes (shortened): What's New in the November 2008 DirectX SDK This version of the DirectX SDK contains the following new features, tools, and documentation. PIX for Windows PIX for Windows supports basic stream capture and single frame capture for Direct3D 11, however the new Direct3D 11 hardware features like tessellation, compute shader, dynamic shader linkage, and new resource formats, are not supported. In addition, advanced features like shader debugging and mesh viewing are not supported. These will be added in a future release. XACT3 Now Supports the Same xWMA Bitrates Supported by XAudio2 XACT3 now supports the same xWMA bit rates that are supported by XAudio2. The exposed lower bit rates allow titles to take advantage of more aggressive compression. Updated Audio Sample The XAudio2 Sound3D sample has been updated to better demonstrate the capabilities of XAudio2 and X3DAudio as well as highlighting best practices. Direct3D 11 Technical Preview Included in the November 2008 DirectX SDK is a technical preview of Direct3D 11 and associated components and tools. Direct3D 11 is an update to Direct3D 10.1 enabling new hardware features as well as improving the breadth of configurations supported by Direct3D. As such, Direct3D 11 enables developers to create applications and games that work on Direct3D 10, Direct3D 10.1, and Direct3D 11 hardware when it becomes available. With the addition of WARP and Direct3D 10 Level 9, Direct3D 10.1 and Direct3D 11 have the ability to target fast software rasterization and Direct3D 9 hardware. This version of the Direct3D 11 technical preview includes support for the following: Tessellation Compute Shaders Multithreaded Rendering Dynamic Shader Linkage Windows Advanced Rasterizer (WARP) Direct3D 10 and Direct3D 11 on Direct3D 9 Hardware (D3D10 Level 9) Runtime Binaries D3DX11 Completely Updated HLSL and Direct3D Compiler D3D11 Reference Rasterizer D3D11 SDK Layers In addition, there are four new samples that highlight tessellation, computer shaders, mulithreaded rendering, and dynamic shader linkage.

Share this post


Link to post
Share on other sites
Advertisement
Downloading right now. I've been waiting for days to give WARP10 and 10-on-9 a shot after seeing it in a Microsoft PDC presentation. That should finally allow me to use Direct3D 10 in my projects (no, I don't own a D3D10-capable graphics card).

I hope there's documentation, too, about how to program one's very own software device. I used to spend a lot of my time working on a software rasterizer named Muli3D and have been thinking about reviving it lately.

Share this post


Link to post
Share on other sites
Quote:
Original post by Stereo
Downloading right now. I've been waiting for days to give WARP10 and 10-on-9 a shot after seeing it in a Microsoft PDC presentation. That should finally allow me to use Direct3D 10 in my projects (no, I don't own a D3D10-capable graphics card).

I hope there's documentation, too, about how to program one's very own software device. I used to spend a lot of my time working on a software rasterizer named Muli3D and have been thinking about reviving it lately.


Both 10Level9 and WARP only work with the D3D11 runtime for now, just FYI.

Share this post


Link to post
Share on other sites
ooh, I didn't know they were releasing WARP and 10L9 just yet - thought that was still a bit hush hush! Very cool though - I quite like the way things are going with the various hardware support/combination (I'm lucky enough to not care for XP-compat personally) [grin]

Jack

Share this post


Link to post
Share on other sites
Quote:
Original post by jollyjeffers
ooh, I didn't know they were releasing WARP and 10L9 just yet - thought that was still a bit hush hush! Very cool though - I quite like the way things are going with the various hardware support/combination (I'm lucky enough to not care for XP-compat personally) [grin]

Jack


Technical Warp10 runs at XP. I read in a blog post that Microsoft have a somewhat modified runtime to make this possible. But as 10 Level 9 talks to WDDM drivers only it will not work on XP.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By evelyn4you
      hi,
      until now i use typical vertexshader approach for skinning with a Constantbuffer containing the transform matrix for the bones and an the vertexbuffer containing bone index and bone weight.
      Now i have implemented realtime environment  probe cubemaping so i have to render my scene from many point of views and the time for skinning takes too long because it is recalculated for every side of the cubemap.
      For Info i am working on Win7 an therefore use one Shadermodel 5.0 not 5.x that have more options, or is there a way to use 5.x in Win 7
      My Graphic Card is Directx 12 compatible NVidia GTX 960
      the member turanszkij has posted a good for me understandable compute shader. ( for Info: in his engine he uses an optimized version of it )
      https://turanszkij.wordpress.com/2017/09/09/skinning-in-compute-shader/
      Now my questions
       is it possible to feed the compute shader with my orignial vertexbuffer or do i have to copy it in several ByteAdressBuffers as implemented in the following code ?
        the same question is about the constant buffer of the matrixes
       my more urgent question is how do i feed my normal pipeline with the result of the compute Shader which are 2 RWByteAddressBuffers that contain position an normal
      for example i could use 2 vertexbuffer bindings
      1 containing only the uv coordinates
      2.containing position and normal
      How do i copy from the RWByteAddressBuffers to the vertexbuffer ?
       
      (Code from turanszkij )
      Here is my shader implementation for skinning a mesh in a compute shader:
      1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 struct Bone { float4x4 pose; }; StructuredBuffer<Bone> boneBuffer;   ByteAddressBuffer vertexBuffer_POS; // T-Pose pos ByteAddressBuffer vertexBuffer_NOR; // T-Pose normal ByteAddressBuffer vertexBuffer_WEI; // bone weights ByteAddressBuffer vertexBuffer_BON; // bone indices   RWByteAddressBuffer streamoutBuffer_POS; // skinned pos RWByteAddressBuffer streamoutBuffer_NOR; // skinned normal RWByteAddressBuffer streamoutBuffer_PRE; // previous frame skinned pos   inline void Skinning(inout float4 pos, inout float4 nor, in float4 inBon, in float4 inWei) {  float4 p = 0, pp = 0;  float3 n = 0;  float4x4 m;  float3x3 m3;  float weisum = 0;   // force loop to reduce register pressure  // though this way we can not interleave TEX - ALU operations  [loop]  for (uint i = 0; ((i &lt; 4) &amp;&amp; (weisum&lt;1.0f)); ++i)  {  m = boneBuffer[(uint)inBon].pose;  m3 = (float3x3)m;   p += mul(float4(pos.xyz, 1), m)*inWei;  n += mul(nor.xyz, m3)*inWei;   weisum += inWei;  }   bool w = any(inWei);  pos.xyz = w ? p.xyz : pos.xyz;  nor.xyz = w ? n : nor.xyz; }   [numthreads(1024, 1, 1)] void main( uint3 DTid : SV_DispatchThreadID ) {  const uint fetchAddress = DTid.x * 16; // stride is 16 bytes for each vertex buffer now...   uint4 pos_u = vertexBuffer_POS.Load4(fetchAddress);  uint4 nor_u = vertexBuffer_NOR.Load4(fetchAddress);  uint4 wei_u = vertexBuffer_WEI.Load4(fetchAddress);  uint4 bon_u = vertexBuffer_BON.Load4(fetchAddress);   float4 pos = asfloat(pos_u);  float4 nor = asfloat(nor_u);  float4 wei = asfloat(wei_u);  float4 bon = asfloat(bon_u);   Skinning(pos, nor, bon, wei);   pos_u = asuint(pos);  nor_u = asuint(nor);   // copy prev frame current pos to current frame prev pos streamoutBuffer_PRE.Store4(fetchAddress, streamoutBuffer_POS.Load4(fetchAddress)); // write out skinned props:  streamoutBuffer_POS.Store4(fetchAddress, pos_u);  streamoutBuffer_NOR.Store4(fetchAddress, nor_u); }  
    • By mister345
      Hi, can someone please explain why this is giving an assertion EyePosition!=0 exception?
       
      _lightBufferVS->viewMatrix = DirectX::XMMatrixLookAtLH(XMLoadFloat3(&_lightBufferVS->position), XMLoadFloat3(&_lookAt), XMLoadFloat3(&up));
      It looks like DirectX doesnt want the 2nd parameter to be a zero vector in the assertion, but I passed in a zero vector with this exact same code in another program and it ran just fine. (Here is the version of the code that worked - note XMLoadFloat3(&m_lookAt) parameter value is (0,0,0) at runtime - I debugged it - but it throws no exceptions.
          m_viewMatrix = DirectX::XMMatrixLookAtLH(XMLoadFloat3(&m_position), XMLoadFloat3(&m_lookAt), XMLoadFloat3(&up)); Here is the repo for the broken code (See LightClass) https://github.com/mister51213/DirectX11Engine/blob/master/DirectX11Engine/LightClass.cpp
      and here is the repo with the alternative version of the code that is working with a value of (0,0,0) for the second parameter.
      https://github.com/mister51213/DX11Port_SoftShadows/blob/master/Engine/lightclass.cpp
    • By mister345
      Hi, can somebody please tell me in clear simple steps how to debug and step through an hlsl shader file?
      I already did Debug > Start Graphics Debugging > then captured some frames from Visual Studio and
      double clicked on the frame to open it, but no idea where to go from there.
       
      I've been searching for hours and there's no information on this, not even on the Microsoft Website!
      They say "open the  Graphics Pixel History window" but there is no such window!
      Then they say, in the "Pipeline Stages choose Start Debugging"  but the Start Debugging option is nowhere to be found in the whole interface.
      Also, how do I even open the hlsl file that I want to set a break point in from inside the Graphics Debugger?
       
      All I want to do is set a break point in a specific hlsl file, step thru it, and see the data, but this is so unbelievably complicated
      and Microsoft's instructions are horrible! Somebody please, please help.
       
       
       

    • By mister345
      I finally ported Rastertek's tutorial # 42 on soft shadows and blur shading. This tutorial has a ton of really useful effects and there's no working version anywhere online.
      Unfortunately it just draws a black screen. Not sure what's causing it. I'm guessing the camera or ortho matrix transforms are wrong, light directions, or maybe texture resources not being properly initialized.  I didnt change any of the variables though, only upgraded all types and functions DirectX3DVector3 to XMFLOAT3, and used DirectXTK for texture loading. If anyone is willing to take a look at what might be causing the black screen, maybe something pops out to you, let me know, thanks.
      https://github.com/mister51213/DX11Port_SoftShadows
       
      Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.
      https://github.com/mister51213/DX11Port_ShadowMapping
       
    • By xhcao
      Is Direct3D 11 an api function like glMemoryBarrier in OpenGL? For example, if binds a texture to compute shader, compute shader writes some values to texture, then dispatchCompute, after that, read texture content to CPU side. I know, In OpenGL, we could call glMemoryBarrier before reading to assure that texture all content has been updated by compute shader.
      How to handle incoherent memory access in Direct3D 11? Thank you.
  • Advertisement