# DX11 [D3D11] Simple textured triangle won't draw

## Recommended Posts

You might have seen my previous post about my textured quad not drawing.  This time, I wanted to just slightly modify the SlimDX SimpleTriangle example to see If I could get a simple textured triangle to draw.  This time, the application compiles and runs, but produces a black triangle instead of one with a texture on it.  Any Ideas on what's wrong?

Here's the C# code:

namespace SimpleTriangle
{

[StructLayout(LayoutKind.Explicit, Size = 20)]
public struct Vertex
{
[FieldOffset(0)]
public Vector3 Position;

[FieldOffset(12)]
public Vector2 TexCoord;
}

static class Program
{
static void Main()
{
Device device;
SwapChain swapChain;

var form = new RenderForm("Tutorial 3: Simple Triangle");
var description = new SwapChainDescription()
{
BufferCount = 2,
Usage = Usage.RenderTargetOutput,
OutputHandle = form.Handle,
IsWindowed = true,
ModeDescription = new ModeDescription(0, 0, new Rational(60, 1), Format.R8G8B8A8_UNorm),
SampleDescription = new SampleDescription(1, 0),
Flags = SwapChainFlags.AllowModeSwitch,
};

Device.CreateWithSwapChain(DriverType.Hardware, DeviceCreationFlags.Debug, description, out device, out swapChain);

// create a view of our render target, which is the backbuffer of the swap chain we just created
RenderTargetView renderTarget;
using (var resource = Resource.FromSwapChain<Texture2D>(swapChain, 0))
renderTarget = new RenderTargetView(device, resource);

// setting a viewport is required if you want to actually see anything
var context = device.ImmediateContext;
var viewport = new Viewport(0.0f, 0.0f, form.ClientSize.Width, form.ClientSize.Height);
context.OutputMerger.SetTargets(renderTarget);
context.Rasterizer.SetViewports(viewport);

{
}

String file = "C:/Users/Jared/Documents/Visual Studio 2010/Projects/Dx11Test/Dx11Test/Texture.bmp";
Texture2D texture = Texture2D.FromFile(device, file);

// create test vertex data, making sure to rewind the stream afterward
var vertices = new DataStream(Marshal.SizeOf(typeof(Vertex)) * 3, true, true);
vertices.Write(new Vertex() { Position = new Vector3(0.0f, 0.5f, 0.5f), TexCoord = new Vector2(0.5f, 0.0f) });
vertices.Write(new Vertex() { Position = new Vector3(0.5f, -0.5f, 0.5f), TexCoord = new Vector2(1.0f, 1.0f) });
vertices.Write(new Vertex() { Position = new Vector3(-0.5f, -0.5f, 0.5f), TexCoord = new Vector2(0.0f, 1.0f) });
vertices.Position = 0;

// create the vertex layout and buffer
var elements = new[] { new InputElement("POSITION", 0, Format.R32G32B32_Float, 0), new InputElement("TEXCOORD", 0, Format.R32G32_Float, 0) };
var layout = new InputLayout(device, inputSignature, elements);
var vertexBuffer = new SlimDX.Direct3D11.Buffer(device, vertices, Marshal.SizeOf(typeof(Vertex)) * 3, ResourceUsage.Default, BindFlags.VertexBuffer, CpuAccessFlags.None, ResourceOptionFlags.None, 0);

// configure the Input Assembler portion of the pipeline with the vertex data
context.InputAssembler.InputLayout = layout;
context.InputAssembler.PrimitiveTopology = PrimitiveTopology.TriangleList;
context.InputAssembler.SetVertexBuffers(0, new VertexBufferBinding(vertexBuffer, 20, 0));

// set the sampler
SamplerDescription sampleDescr = new SamplerDescription();
sampleDescr.Filter = Filter.MinMagMipLinear;
sampleDescr.MipLodBias = 0.0f;
sampleDescr.MaximumAnisotropy = 1;
sampleDescr.ComparisonFunction = Comparison.Always;
sampleDescr.BorderColor = System.Drawing.Color.White;
sampleDescr.MinimumLod = 0;
sampleDescr.MaximumLod = float.MaxValue;

SamplerState samplerState = SamplerState.FromDescription(device, sampleDescr);

// prevent DXGI handling of alt+enter, which doesn't work properly with Winforms
using (var factory = swapChain.GetParent<Factory>())
factory.SetWindowAssociation(form.Handle, WindowAssociationFlags.IgnoreAltEnter);

// handle alt+enter ourselves
form.KeyDown += (o, e) =>
{
if (e.Alt && e.KeyCode == Keys.Enter)
swapChain.IsFullScreen = !swapChain.IsFullScreen;
};

// handle form size changes
form.UserResized += (o, e) =>
{
renderTarget.Dispose();

swapChain.ResizeBuffers(2, 0, 0, Format.R8G8B8A8_UNorm, SwapChainFlags.AllowModeSwitch);
using (var resource = Resource.FromSwapChain<Texture2D>(swapChain, 0))
renderTarget = new RenderTargetView(device, resource);

context.OutputMerger.SetTargets(renderTarget);
};

MessagePump.Run(form, () =>
{
// clear the render target to a soothing blue
context.ClearRenderTargetView(renderTarget, new Color4(0.5f, 0.5f, 1.0f));

// draw the triangle
context.Draw(3, 0);
swapChain.Present(0, PresentFlags.None);
});

// clean up all resources
// anything we missed will show up in the debug output
vertices.Close();
vertexBuffer.Dispose();
layout.Dispose();
inputSignature.Dispose();
renderTarget.Dispose();
swapChain.Dispose();
device.Dispose();
}
}
}


SamplerState SamplerType;
Texture2D Texture;

{
float4 position : POSITION;
float2 TexCoord : TEXCOORD0;
};

{
float4 position : SV_POSITION;
float2 TexCoord : TEXCOORD0;
};

{

output.position = input.position;
output.TexCoord = input.TexCoord;

return output;
}

{
float4 textureSample = Texture.Sample(SamplerType, input.TexCoord);

return textureSample;
}


##### Share on other sites

Usually a black texture result means either that the texture coordinates are out of range, or that the texture resource isn't properly bound to the pipeline.  Have you tried to use PIX and/or the VS2012 Graphics Debugger to inspect your rendered frames?  If not, it is worth the time to get acquainted with these tools, because they will help you understand what is going on with your application (both in times when things aren't working, and also when things are working but you want to collect data about your usage of the API)!

##### Share on other sites

Okay, got it fixed.  Turned out that I had bound the TextureResourceView to the wrong slot inside the shader.

I use PIX but I'm not exactly sure how I would read memory to figure this out.  From what I see, PIX only shows which resources I've created, not where/how they are bound to the pipeline.

##### Share on other sites

Okay, got it fixed.  Turned out that I had bound the TextureResourceView to the wrong slot inside the shader.

I use PIX but I'm not exactly sure how I would read memory to figure this out.  From what I see, PIX only shows which resources I've created, not where/how they are bound to the pipeline.

If you capture a frame by hitting F12, then go to a draw call in the lower half of the screen, then you will be able to right click on the textures being bound in your Set* calls.  This is a quick and easy way to see if you are really doing what you think you are.

## Create an account

Register a new account

• ### Forum Statistics

• Total Topics
627778
• Total Posts
2979026
• ### Similar Content

• I wanted to get some advice on what everyone thinks of this debugger, I've been getting some strange results from testing my code and I wanted to see if anyone else had an issues.
For instance, I added three "ClearRenderTargetView" calls and three "Draw full screen quad" calls and my reported fps became a fifth of what it usually was. Thank you.

• Hello,
I manged so far to implement NVIDIA's NDF-Filtering at a basic level (the paper can be found here). Here is my code so far:
//... // project the half vector on the normal (?) float3 hppWS = halfVector / dot(halfVector, geometricNormal) float2 hpp = float2(dot(hppWS, wTangent), dot(hppWS, wBitangent)); // compute the pixel footprint float2x2 dhduv = float2x2(ddx(hpp), ddy(hpp)); // compute the rectangular area of the pixel footprint float2 rectFp = min((abs(dhduv[0]) + abs(dhduv[1])) * 0.5, 0.3); // map the area to ggx roughness float2 covMx = rectFp * rectFp * 2; roughness = sqrt(roughness * roughness + covMx); //... Now I want combine this with LEAN mapping as state in Chapter 5.5 of the NDF paper.
But I struggle to understand what theses sections actually means in Code:
I suppose the first-order moments are the B coefficent of the LEAN map, however things like
float3 hppWS = halfVector / dot(halfVector, float3(lean_B, 0)); doesn't bring up anything usefull.
Next theres:
This simply means:
// M and B are the coefficents from the LEAN map float2x2 sigma_mat = float2x2( M.x - B.x * B.x, M.z - B.x * B.y, M.z - B.x * B.y, M.y - B.y * B.y); does it?
Finally:
This is the part confuses me the most: how am I suppose to convolute two matrices? I know the concept of convolution in terms of functions, not matrices. Should I multiple them? That didn't make any usefully output.
I hope someone can help with this maybe too specific question, I'm really despaired to make this work and i've spend too many hours of trial & error...
Cheers,
Julian
• By Baemz
Hello,
I've been working on some culling-techniques for a project. We've built our own engine so pretty much everything is built from scratch. I've set up a frustum with the following code, assuming that the FOV is 90 degrees.
float angle = CU::ToRadians(45.f); Plane<float> nearPlane(Vector3<float>(0, 0, aNear), Vector3<float>(0, 0, -1)); Plane<float> farPlane(Vector3<float>(0, 0, aFar), Vector3<float>(0, 0, 1)); Plane<float> right(Vector3<float>(0, 0, 0), Vector3<float>(angle, 0, -angle)); Plane<float> left(Vector3<float>(0, 0, 0), Vector3<float>(-angle, 0, -angle)); Plane<float> up(Vector3<float>(0, 0, 0), Vector3<float>(0, angle, -angle)); Plane<float> down(Vector3<float>(0, 0, 0), Vector3<float>(0, -angle, -angle)); myVolume.AddPlane(nearPlane); myVolume.AddPlane(farPlane); myVolume.AddPlane(right); myVolume.AddPlane(left); myVolume.AddPlane(up); myVolume.AddPlane(down); When checking the intersections I am using a BoundingSphere of my models, which is calculated by taking the average position of all vertices and then choosing the furthest distance to a vertex for radius. The actual intersection test looks like this, where the "myFrustum90" is the actual frustum described above.
The orientationInverse is the viewMatrix in this case.
bool CFrustum::Intersects(const SFrustumCollider& aCollider) { CU::Vector4<float> position = CU::Vector4<float>(aCollider.myCenter.x, aCollider.myCenter.y, aCollider.myCenter.z, 1.f) * myOrientationInverse; return myFrustum90.Inside({ position.x, position.y, position.z }, aCollider.myRadius); } The Inside() function looks like this.
template <typename T> bool PlaneVolume<T>::Inside(Vector3<T> aPosition, T aRadius) const { for (unsigned short i = 0; i < myPlaneList.size(); ++i) { if (myPlaneList[i].ClassifySpherePlane(aPosition, aRadius) > 0) { return false; } } return true; } And this is the ClassifySpherePlane() function. (The plane is defined as a Vector4 called myABCD, where ABC is the normal)
template <typename T> inline int Plane<T>::ClassifySpherePlane(Vector3<T> aSpherePosition, float aSphereRadius) const { float distance = (aSpherePosition.Dot(myNormal)) - myABCD.w; // completely on the front side if (distance >= aSphereRadius) { return 1; } // completely on the backside (aka "inside") if (distance <= -aSphereRadius) { return -1; } //sphere intersects the plane return 0; }
Please bare in mind that this code is not optimized nor well-written by any means. I am just looking to get it working.
The result of this culling is that the models seem to be culled a bit "too early", so that the culling is visible and the models pops away.
How do I get the culling to work properly?
I have tried different techniques but haven't gotten any of them to work.
If you need more code or explanations feel free to ask for it.

Thanks.

• hi,
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
or
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:
perform drawcall       ( buffer_A is used )

perform drawcall   ( buffer_B is used )
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

• 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

• 11
• 10
• 10
• 23
• 9