• Advertisement
  • Popular Tags

  • Popular Now

  • Advertisement
  • Similar Content

    • By fs1
      I have been trying to see how the ID3DInclude, and how its methods Open and Close work.
      I would like to add a custom path for the D3DCompile function to search for some of my includes.
      I have not found any working example. Could someone point me on how to implement these functions? I would like D3DCompile to look at a custom C:\Folder path for some of the include files.
      Thanks
    • By stale
      I'm continuing to learn more about terrain rendering, and so far I've managed to load in a heightmap and render it as a tessellated wireframe (following Frank Luna's DX11 book). However, I'm getting some really weird behavior where a large section of the wireframe is being rendered with a yellow color, even though my pixel shader is hard coded to output white. 

      The parts of the mesh that are discolored changes as well, as pictured below (mesh is being clipped by far plane).

      Here is my pixel shader. As mentioned, I simply hard code it to output white:
      float PS(DOUT pin) : SV_Target { return float4(1.0f, 1.0f, 1.0f, 1.0f); } I'm completely lost on what could be causing this, so any help in the right direction would be greatly appreciated. If I can help by providing more information please let me know.
    • By evelyn4you
      Hello,
      i try to implement voxel cone tracing in my game engine.
      I have read many publications about this, but some crucial portions are still not clear to me.
      At first step i try to emplement the easiest "poor mans" method
      a.  my test scene "Sponza Atrium" is voxelized completetly in a static voxel grid 128^3 ( structured buffer contains albedo)
      b. i dont care about "conservative rasterization" and dont use any sparse voxel access structure
      c. every voxel does have the same color for every side ( top, bottom, front .. )
      d.  one directional light injects light to the voxels ( another stuctured buffer )
      I will try to say what i think is correct ( please correct me )
      GI lighting a given vertecie  in a ideal method
      A.  we would shoot many ( e.g. 1000 ) rays in the half hemisphere which is oriented according to the normal of that vertecie
      B.  we would take into account every occluder ( which is very much work load) and sample the color from the hit point.
      C. according to the angle between ray and the vertecie normal we would weigth ( cosin ) the color and sum up all samples and devide by the count of rays
      Voxel GI lighting
      In priciple we want to do the same thing with our voxel structure.
      Even if we would know where the correct hit points of the vertecie are we would have the task to calculate the weighted sum of many voxels.
      Saving time for weighted summing up of colors of each voxel
      To save the time for weighted summing up of colors of each voxel we build bricks or clusters.
      Every 8 neigbour voxels make a "cluster voxel" of level 1, ( this is done recursively for many levels ).
      The color of a side of a "cluster voxel" is the average of the colors of the four containing voxels sides with the same orientation.

      After having done this we can sample the far away parts just by sampling the coresponding "cluster voxel with the coresponding level" and get the summed up color.
      Actually this process is done be mip mapping a texture that contains the colors of the voxels which places the color of the neighbouring voxels also near by in the texture.
      Cone tracing, howto ??
      Here my understanding is confus ?? How is the voxel structure efficiently traced.
      I simply cannot understand how the occlusion problem is fastly solved so that we know which single voxel or "cluster voxel" of which level we have to sample.
      Supposed,  i am in a dark room that is filled with many boxes of different kind of sizes an i have a pocket lamp e.g. with a pyramid formed light cone
      - i would see some single voxels near or far
      - i would also see many different kind of boxes "clustered voxels" of different sizes which are partly occluded
      How do i make a weighted sum of this ligting area ??
      e.g. if i want to sample a "clustered voxel level 4" i have to take into account how much per cent of the area of this "clustered voxel" is occluded.
      Please be patient with me, i really try to understand but maybe i need some more explanation than others
      best regards evelyn
       
       
    • By Endemoniada

      Hi guys, when I do picking followed by ray-plane intersection the results are all wrong. I am pretty sure my ray-plane intersection is correct so I'll just show the picking part. Please take a look:
       
      // get projection_matrix DirectX::XMFLOAT4X4 mat; DirectX::XMStoreFloat4x4(&mat, projection_matrix); float2 v; v.x = (((2.0f * (float)mouse_x) / (float)screen_width) - 1.0f) / mat._11; v.y = -(((2.0f * (float)mouse_y) / (float)screen_height) - 1.0f) / mat._22; // get inverse of view_matrix DirectX::XMMATRIX inv_view = DirectX::XMMatrixInverse(nullptr, view_matrix); DirectX::XMStoreFloat4x4(&mat, inv_view); // create ray origin (camera position) float3 ray_origin; ray_origin.x = mat._41; ray_origin.y = mat._42; ray_origin.z = mat._43; // create ray direction float3 ray_dir; ray_dir.x = v.x * mat._11 + v.y * mat._21 + mat._31; ray_dir.y = v.x * mat._12 + v.y * mat._22 + mat._32; ray_dir.z = v.x * mat._13 + v.y * mat._23 + mat._33;  
      That should give me a ray origin and direction in world space but when I do the ray-plane intersection the results are all wrong.
      If I click on the bottom half of the screen ray_dir.z becomes negative (more so as I click lower). I don't understand how that can be, shouldn't it always be pointing down the z-axis ?
      I had this working in the past but I can't find my old code
      Please help. Thank you.
    • By turanszkij
      Hi,
      I finally managed to get the DX11 emulating Vulkan device working but everything is flipped vertically now because Vulkan has a different clipping space. What are the best practices out there to keep these implementation consistent? I tried using a vertically flipped viewport, and while it works on Nvidia 1050, the Vulkan debug layer is throwing error messages that this is not supported in the spec so it might not work on others. There is also the possibility to flip the clip scpace position Y coordinate before writing out with vertex shader, but that requires changing and recompiling every shader. I could also bake it into the camera projection matrices, though I want to avoid that because then I need to track down for the whole engine where I upload matrices... Any chance of an easy extension or something? If not, I will probably go with changing the vertex shaders.
  • Advertisement
  • Advertisement
Sign in to follow this  

DX11 DX11 Sprite Like Technique - With a quad

This topic is 1855 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

Hi guys,

 

right now I'm having a small quad with a texture on it, and I wan't it to face my camera. The reason for that is because I wan't to mess around with Post Processing, It looks for me right now:

 

if ssao

  Render Normals to TEXTUREN

  Render Position to TEXTUREP

Render Diffuse     to TEXTURED

 

Render Plane with TEXTUREN | TEXTUREP | TEXTURED - To do some post processing

Show it!

 

Now please correct me if this is a wrong way!

 

But how is it possible to rotate and translate a quad to face the player/camera, looking like it's a real 3d scene (with some post processing) ?

 

Thank You

Share this post


Link to post
Share on other sites
Advertisement

But how is it possible to rotate and translate a quad to face the player/camera, looking like it's a real 3d scene (with some post processing) ?

There are a number of ways to do a full screen quad.  Typically you just send four vertices with already transformed content (i.e. w=1 already) and their positions are in the clip space corners.  They would be something like this:

 

(-1,1,0,1) for upper left

(1,1,0,1) for upper right

(-1,-1,0,1) for lower left

(1,-1,0,1) for lower right

 

Since these are in clip space, you are guaranteed to cover the entire viewport regardless of the actual size of it.

Share this post


Link to post
Share on other sites

But how in terms of HLSL would this be possible?

 

So would i specify those 4 points and directly map them into HLSL, without any use of any Matrices? Sorry, I'm not very familiar with this topic of view space conversions...

Share this post


Link to post
Share on other sites

But how in terms of HLSL would this be possible?

 

So would i specify those 4 points and directly map them into HLSL, without any use of any Matrices? Sorry, I'm not very familiar with this topic of view space conversions...

Yup - that's exactly right.  The vertices are already ready to go to the rasterizer, so you just pass them through the vertex shader.  Just make sure your w-values are equal to 1, and it should work fairly easily.  To test it out, you can also try modifying the values to cover half the screen, a quarter of the screen, etc...

Share this post


Link to post
Share on other sites

Sorry to take your time, I do understand the concept, but I'm doing it wrong somehow.

 

Post Process Shader file for now: (Where shader stuff and quad is created)

 

#include "stdafx.h"
#include "PostProcess.h"

#include <d3dcompiler.h>
#include <DxErr.h>

#define CE_WARNING(title, message) MessageBoxA(NULL, message, title, 0) 

BOOL PostProcessClass::Create( ID3D11Device *&dev, ID3D11DeviceContext *&devcon )
{
	string finals = string(
		"C:\\Users\\Utilizador\\Documents\\Visual Studio 2012\\Projects\\Cube3D\\Product\\Bin32\\") + string("PostProcessShader.hlsl").c_str();

	ID3D10Blob *vserrors;
	ID3D10Blob *pserrors;
	HRESULT HR;

	D3DX11CompileFromFile(finals.c_str(), 0, 0, "VShader", "vs_5_0", D3DCOMPILE_DEBUG, 0, 0, &VS, &vserrors, &HR);
	D3DX11CompileFromFile(finals.c_str(), 0, 0, "PShader", "ps_5_0", D3DCOMPILE_DEBUG, 0, 0, &PS, &pserrors, &HR);
	
	// create the shader objects
	if (!VS)
	{
		DXTRACE_ERR(TEXT(DXGetErrorDescription(HR)),HR);

		MessageBoxA(NULL, "The Post Process vertex shader creation has failed, program will now exit!", "ERROR", 0);
		exit(0);
	}
	if (!PS)
	{
		DXTRACE_ERR(TEXT(DXGetErrorDescription(HR)),HR);

		MessageBoxA(NULL, "The Post Process pixel shader creation has failed, program will now exit!", "ERROR", 0);
		exit(0);
	}
	
	dev->CreateVertexShader(VS->GetBufferPointer(), VS->GetBufferSize(), NULL, &pVS);
	dev->CreatePixelShader(PS->GetBufferPointer(), PS->GetBufferSize(), NULL, &pPS);

	D3D11_INPUT_ELEMENT_DESC ied[] =
	{
		{"POSITION", 0, DXGI_FORMAT_R32G32B32_FLOAT, 0, D3D11_APPEND_ALIGNED_ELEMENT, D3D11_INPUT_PER_VERTEX_DATA, 0}
	};
	
	if (dev->CreateInputLayout(ied, 1, VS->GetBufferPointer(), VS->GetBufferSize(), &pLayout) != S_OK)
		CE_WARNING("Input Layout Creation", "Input Layout creation in Post Process has failed!");

	// create the vertex buffer
	D3D11_BUFFER_DESC bd;
	ZeroMemory(&bd, sizeof(bd));

	Vertices[0] = D3DXVECTOR3(-1, 0, 1);
	Vertices[1] = D3DXVECTOR3(1, 0, 1);
	Vertices[2] = D3DXVECTOR3(-1, 0, -1);
	Vertices[3] = D3DXVECTOR3(1, 0, 1);

	Indices[0] = 3;
	Indices[1] = 1;
	Indices[2] = 2;
	Indices[3] = 2;
	Indices[4] = 1;
	Indices[5] = 0;

	bd.Usage = D3D11_USAGE_DYNAMIC;
	bd.ByteWidth = sizeof(D3DXVECTOR3) * 4;
	bd.BindFlags = D3D11_BIND_VERTEX_BUFFER;
	bd.CPUAccessFlags = D3D11_CPU_ACCESS_WRITE;
	
	dev->CreateBuffer(&bd, NULL, &vBFF);

	D3D11_MAPPED_SUBRESOURCE ms;
	// copy the vertices into the buffer
	devcon->Map(vBFF, NULL, D3D11_MAP_WRITE_DISCARD, NULL, &ms);    // map the buffer
	memcpy(ms.pData, Vertices, sizeof(Vertices));                 // copy the data
	devcon->Unmap(vBFF, NULL);

	//**INDICES**//

	bd.Usage = D3D11_USAGE_DYNAMIC;
	bd.ByteWidth = sizeof(DWORD) * 6;
	bd.BindFlags = D3D11_BIND_INDEX_BUFFER;
	bd.CPUAccessFlags = D3D11_CPU_ACCESS_WRITE;
	
	dev->CreateBuffer(&bd, NULL, &iBFF);

	D3D11_MAPPED_SUBRESOURCE msI;
	// copy the vertices into the buffer
	devcon->Map(iBFF, NULL, D3D11_MAP_WRITE_DISCARD, NULL, &msI);    // map the buffer
	memcpy(msI.pData, Indices, sizeof(Indices));                 // copy the data
	devcon->Unmap(iBFF, NULL);
}

void PostProcessClass::ApplyShader(ID3D11Device *&dev, ID3D11DeviceContext *&devcon)
{
	// set the shader objects
	devcon->VSSetShader(pVS, 0, 0);
	devcon->PSSetShader(pPS, 0, 0);
	devcon->IASetInputLayout(pLayout);
}

void PostProcessClass::Render(ID3D11DeviceContext *&devcon, ID3D11Device *&dev)
{
	ApplyShader(dev, devcon);

	UINT stride = sizeof(D3DXVECTOR3);
	UINT offset = 0;

	devcon->IASetVertexBuffers(0, 1, &vBFF, &stride, &offset);
	devcon->IASetIndexBuffer(iBFF, DXGI_FORMAT_R32_UINT, 0);

	devcon->DrawIndexed(6, 0, 0);
}

 

Now the output is a black screen, and heres the reason from debugging:

 

9sw294.png

 

When you look at the vertex shader, the result is a straight line, which isn't exactly what I wanted happy.png

 

Now the question is why?

 

Ohh, almost forgot, my shader (it's simple for now for debugging):

 

struct VOut
{
    float4 position : SV_POSITION;
};

VOut VShader(float3 position : POSITION)
{
    VOut output;

    output.position = float4(position, 1.0f);
	output.position.w = 1.0f;
	
    return output;
}

float4 PShader(VOut input) : SV_TARGET
{
	return float4(1, 0, 0, 1);
}
Edited by Migi0027

Share this post


Link to post
Share on other sites

Wait, so what should I do, I'm probably not understanding this then... What's wrong with my code?

Edited by Migi0027

Share this post


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

  • Advertisement