• Advertisement

champloo

Member
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

147 Neutral

About champloo

  • Rank
    Member
  1.   Thank you so much. you are right, structured buffer cannot be used as an indirect args buffer. didn't know I can create device with the debug flag, it's very helpful.
  2. Hi,   here is what I am trying to do, which is just to create a structured buffer. D3D11_BUFFER_DESC sb_desc; sb_desc.ByteWidth = stride * numElements; sb_desc.Usage = D3D11_USAGE_DEFAULT; sb_desc.BindFlags = D3D11_BIND_SHADER_RESOURCE | D3D11_BIND_UNORDERED_ACCESS; sb_desc.CPUAccessFlags = 0; sb_desc.MiscFlags = D3D11_RESOURCE_MISC_BUFFER_STRUCTURED; sb_desc.MiscFlags |= drawIndirect ? D3D11_RESOURCE_MISC_DRAWINDIRECT_ARGS : 0; sb_desc.StructureByteStride = stride; DXCall( device->CreateBuffer( &sb_desc, NULL, &sb ) ); It fails every time, and if I remove the D3D11_RESOURCE_MISC_DRAWINDIRECT_ARGS flag, the error goes away.   I've tried different parameters but no luck at this point. Any help is appreciated.
  3. inconsistent frametime

    no I cannot feel the stutter when dragging the camera around. I am calling timeGetTime() to get the value. and that's the value I'm using to update all my systems.
  4. inconsistent frametime

    update: I'm debugging on my laptop. which has two graphics cards. and I was running the app on the nvidia card. and I tried it on the Intel card, it runs without significant stuttering, although the frame time is longer. it's something like: 0.009 0.009 0.010 0.008 ... so is it safe to say it's the graphics card?
  5. inconsistent frametime

    Thanks for that comment, yes it's under Visual Studio 10 with DX11. and it still stutters outside the debugger. Even when there is no polygon on screen, or if I reduce number of the render targets I'm using, the frame time still stutters. but in a smaller range. like: 0.002 0.002 0.005 0.001 0.002 ... it's interesting that every longer frame is followed by a shorter frame. and they add up to the average frame time.
  6. Hello all, I have a scene with nothing but 4 instances of a 26K vertices model. and there are two post passes. with one deferred shader and an anti-aliasing pass. the resolution is 1280x720. and my frame time follows this pattern: 0.006 0.005 0.005 0.006 0.005 0.012 0.001 0.005 ... This has been bothering me for a long time. Does anyone know why this happens?
  7. Thanks a lot for your answers. So it seems what I'm doing now is not absolutely wrong. One more question, do I need to change the viewport everytime I change to a render target of different resolution?
  8. I did some research on downsampling recently but couldn't find a clear answer, it almost feels like everybody thinks it's too simple to mention.. Currently my way of doing downsampling is to draw a smaller textured quad to a smaller render target. So if I want to downsample my diffuse map which is 1280x720, to a quarter sized texture. I will have to draw a 640x360 textured quad to a 640x360 render target. and I'm not sure if it's the right way. Also, if I want to render my scene onto a render target of a different size, do I modify the SV_Position inside the shader or change the projection transformation, or is there some other way to do it?
  9. [quote name='MJP' timestamp='1327897650' post='4907527'] [quote name='champloo' timestamp='1327877993' post='4907460'] Is it normal or did I do something wrong? [/quote] That depends on the hardware, your resolution, and what you're doing. Adding an addition 7-8ms just for one post-processing effect does sound wayyyy too high, unless the hardware is extremely weak (Intel integrated graphics) and/or you're doing something really complex. What kind of hardware are you running on? [/quote] it's a nvidia gt 525M. And the resolution is 1280x720. and removing both post-processing effects causes my frametime drop to 1-2ms.
  10. [quote name='mhagain' timestamp='1327880309' post='4907471'] Yup, that's normal. PP is fillrate sensitive and even a "do nothing" pass still needs to write out everything in the framebuffer all over again. [/quote] got it, guess i need to squeeze more stuff in one pass then
  11. I'm new to graphics and still wondering how do people set up their post processing passes. so I draw all my object onto a render target texture. and then apply FXAA on that texture and output to the back buffer. This takes 7-8ms every frame. Then I added another post process shader which do nothing but pass through color. And the frametime goes up to 14-15ms. Is it normal or did I do something wrong? the pipeline is something like this: draw objects onto a screen size texture -> render the same texture onto another screen size texture -> apply fxaa to this texture and output to backbuffer thanks,
  • Advertisement