Sign in to follow this  

DX11 DX11-Window Rect vs render target buffer size.

Recommended Posts

I just realize that doesnt matter the size I specifie on the swap chain desc buffer, it always paints the entire window rect? Why this happens? I mean, Lets say I set everything to 640x480( swapchain`s backbuffer/rendertarget), if my window is 700x800 it will all be cleared by my clear color, why? What is the size of the swapchain desc for?

Share this post

Link to post
Share on other sites
The viewport have the same size of the back buffer specified on the swap chain desc.

Doesnt matter what value I put on the viewport or in the buffer description, notting changes, but Im not rendering anything, just clearing the render target with a color and presenting..

Share this post

Link to post
Share on other sites
The size you give for the swap chain will specify the size of the backbuffer. No matter what size you choose, the backbuffer is scaled to the size of the window's client area. If you don't want this behavior, you'll have to implement it manually either by adjusting your viewport or through some other means.

Share this post

Link to post
Share on other sites
But adjusting the viewport dont works either!

What I want specifialy is let a space for the status bar that my app have( The status bar is drawed at the window client area)

some code:

//here I change the original size of the window, so lets say it have height 480+20=500

MoveWindow( hWnd_p, wndrect_p.left,, wndrect_p.right, wndrect_p.bottom+sbHeight, TRUE );

//the swap chain description is filled with the original wndrect values(640x480)
sw.BufferCount = 2;
sw.BufferDesc.Format = DXGI_FORMAT_R8G8B8A8_UNORM;
sw.BufferDesc.RefreshRate.Numerator = 60;
sw.BufferDesc.RefreshRate.Denominator = 1;
sw.BufferDesc.Width = wndrect_p.right;
sw.BufferDesc.Height = wndrect_p.bottom;
sw.Flags = NULL;
sw.OutputWindow = hWnd_p;
sw.SampleDesc.Count = 1;
sw.SampleDesc.Quality = 0;
sw.Windowed = TRUE;

//and so is the view port:
//note that I alredy tried a lot of values here, like toplefx/y = 0 and width/height=100, notting changes.

D3D11_VIEWPORT vp = {0};
vp.Width = (FLOAT)wndrect_p.right;
vp.Height = (FLOAT)wndrect_p.bottom;
vp.MinDepth = 0.0f; vp.MaxDepth = 1.0f;
vp.TopLeftX = (FLOAT)wndrect_p.left; vp.TopLeftY = (FLOAT);

pDIContext_p->RSSetViewports( 1, &vp );//Render Stage

//here is how Im setting the rendertarget view:
ID3D11Texture2D *pTex2DBBuff = NULL;//resource to get the back buffer

if( pSC_p->GetBuffer( 0, __uuidof(ID3D11Texture2D), (VOID**)&pTex2DBBuff ) != S_OK ) return E_FAIL;

if( pDevice_p->CreateRenderTargetView( pTex2DBBuff, NULL, &pRTV_p ) != S_OK ) return E_FAIL;

g_pDIContext->OMSetRenderTargets( 1, &g_pRTV, NULL);//Output Merger Stage

How can I make it render just on a part of the client area? Am Im doing something wrong?
When I create the render target view Im specifiing NULL as description, on the sdk it says "Set this parameter to NULL to create a view that accesses all of the subresources in mipmap level 0." My subresource is the backbuffer specified at the swap chain desc and have the righ size. Checking this struct at the SDK dont help much, I cant find a member data that would have something to do with this, but Im a moron, maybe it do...It have a member View Dimensions(enum), but the values possible are weird, I cant understand:

Its problay simple stuff..Render to just a part of client area is commom, someones alredy figured it out..o.o

Share this post

Link to post
Share on other sites
Someone could also explain me the D3D11_BUFFER_RTV struct please...On the SDK it have 2 members, but it have 4 members:
What is a buffer element?

Share this post

Link to post
Share on other sites
When you give the swap chain a handle to the window, it pretty much "owns" the entire client area. There's not really a good way to make it play nice with other child windows in the same client area.

What might be an easier approach for you would be to create the status bar as a child window, and then make another borderless child window that fills up the rest of the main window's client area. Then you can just present to that child window.

Share this post

Link to post
Share on other sites
I just figure out that the view port works, the stuff is rendered and clipped just on the view port part of the client area, but the entire client area is cleared(painted) with the clear color... Im sure must be some detail that I didnt find yet..

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  

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By schneckerstein
      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?
      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...
    • By Baemz
      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.

    • 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!
  • Popular Now