# DX11 First time DX11

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

## Recommended Posts

I am trying to migrate from dx9 to dx11, but have difficulty setting my project to build properly (express version of VS 2013).

1. I set the path to inc & lib dirs of my dx sdk (june 2010)

2. I set in linker options to include these libs:

d3d11.lib

d3dcompiler.lib

d3dx11d.lib


3. I have included DirectxTK library into my "solution" using guidelines from this site since this documentation say that D3DX11CreateShaderResourceViewFromFile is deprecated (tho i am on Windows7 still), and i want to be able to load my textures.

When i build my solution i get this errors/warnings, but they are all related to stuff from win/dx sdk:

##### Share on other sites

The macro redef is because you're including the Directx SDK found with the Windows SDK along with your version of Directx 11, I had these warnings, an easy and clean way would be to disable the warning ( What I do )  .

This article does a better job than I do in describing it:

http://msdn.microsoft.com/en-us/library/windows/desktop/ee663275.aspx

The easy way out:

"You can disablewarning C4005 if needed; however, this warning indicates you are using the older version of these headers."

##### Share on other sites

I read article you have provided but still having problems, i even removed directxtk from my solution so i can be sure it is not cause of trouble.

I dont know where did i specify to load dx sdk from win sdk, when i explicitly set the path to dx sdk june 2010?!?

OMG, this pisses me off to boiling point.

How do i force it to load proper libs and headers from "normal" dx sdk june 2010?

##### Share on other sites

I dont know where did i specify to load dx sdk from win sdk, when i explicitly set the path to dx sdk june 2010?!?

You don't specify it. You obviously need the Windows SDK to build Windows app. The SDK that ships with VS2013 includes DirectX in the Windows SDK. Therefor, if you build with 2013, you're going to get these issues.

One option is to just stop using the June 2010 SDK. Replace your D3DX usage with the various Shared Source libraries Microsoft published on Codeplex, see http://blogs.msdn.com/b/chuckw/archive/2013/08/21/living-without-d3dx.aspx for more information.

##### Share on other sites

SeanMiddleditch has it right - you should seriously consider getting out of the D3DX library and instead use an alternative.  It is possible to continue using it, but you will run into issues like these until you just get rid of the DXSDK.  Embrace the change!

• ### Similar Content

• 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

• 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.

Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.

• 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.
• By _Engine_
Atum engine is a newcomer in a row of game engines. Most game engines focus on render
techniques in features list. The main task of Atum is to deliver the best toolset; that’s why,
as I hope, Atum will be a good light weighted alternative to Unity for indie games. Atum already
has fully workable editor that has an ability to play test edited scene. All system code has
simple ideas behind them and focuses on easy to use functionality. That’s why code is minimized
as much as possible.
Currently the engine consists from:
- Scene Editor with ability to play test edited scene;
- Powerful system for binding properties into the editor;
- Render system based on DX11 but created as multi API; so, adding support of another GAPI
is planned;
- Controls system based on aliases;
- Font system based on stb_truetype.h;
- Support of PhysX 3.0, there are samples in repo that use physics;
- Network code which allows to create server/clinet; there is some code in repo which allows
to create a simple network game
I plan to use this engine in multiplayer game - so, I definitely will evolve the engine. Also
I plan to add support for mobile devices. And of course, the main focus is to create a toolset
that will ease games creation.
Link to repo on source code is - https://github.com/ENgineE777/Atum
Video of work process in track based editor can be at follow link:

• I made a spotlight that
1. Projects 3d models onto a render target from each light POV to simulate shadows
2. Cuts a circle out of the square of light that has been projected onto the render target
as a result of the light frustum, then only lights up the pixels inside that circle
(except the shadowed parts of course), so you dont see the square edges of the projected frustum.

After doing an if check to see if the dot product of light direction and light to vertex vector is greater than .95
to get my initial cutoff, I then multiply the light intensity value inside the resulting circle by the same dot product value,
which should range between .95 and 1.0.

This should give the light inside that circle a falloff from 100% lit to 0% lit toward the edge of the circle. However,
there is no falloff. It's just all equally lit inside the circle. Why on earth, I have no idea. If someone could take a gander