Sign in to follow this  
keinmann

DX11 Engine design questions...

Recommended Posts

keinmann    122
Hey guys,

The porting of my old code base over to SlimDX (using exclusively Dx11) has been going quite well. But I'm not liking the way some of my old, naive code is looking. A lot of things are so radically different from Dx9/XNA -> Dx11 that it facilitates throwing the old junk away and writing completely new code. So I've been posed with a few questions that I'd like to get some peer feedback on.

FYI, so you know, I'm trying my best to abstract away a lot of the pain involved with writing straight DX applications with this engine, but not so much that those who WANT lots of nit-picky features can't get to them (not an easy feat, and sometimes not possible).

1) Graphics Settings :

Any engine worth its salt has an fairly intuitive way of changing graphics settings on the fly and often by configuration files; thus enabling programmers to create nice little graphics settings/options menus for their games. I'm brand new to DX11/SlimDX API, so I'm probably missing a lot of stuff and just not seeing it. I'm from the days of "PresentationParameters" and all that jazz. :) So I'm wondering, to begin with, what range of graphics settings/options will be vital to a SlimDX/DX11-based engine? What things do I need to look up and learn about to make an effective graphics settings system? Any particular classes in the API that can help me not reinvent the wheel (as I often do when I'm ignorant of an API's features)? What things are/may be rarely used and not very important to include?

One other question that's been bugging me is about the ModeDescription property for SwapChainDescriptions, concerning their refresh rates. Obviously, when windowed, your application can effectively use any resolution which will fit in the display bounds and match the window size. But what about the refresh rate? Do we have to perfectly match the display mode's refresh rate in windowed mode, or is it only a requirement in full-screen? I remember the DX11 doc said it's vital to get the refresh rate correct in full-screen.

Also, are there any examples on the proper way to switch graphics (Device/SwapChain) settings at runtime? I'm not really sure if the way I switch from windowed to fullscreen is a "good" way of doing things lol. The limited samples and incomplete docs have left me guessing on a lot of things. :P

2) "Main Loop" and timing:

I've already implemented a new, internal clock/timer class which is very similar to the one buried in the XNA framework; although it's lighter and cleaner imho. I've tested it and it's as accurate as it gets on my system. In XNA, the "Game" class is fixed-timestep by default, and has a target update interval of 1/60th second (roughly 16.666something6667-something ms). Question is, what is the best way to ensure you stay within a reasonable tolerance of your update interval? What if the loop completes super fast and you have only a tiny bit of elapsed time between updates? Do you intentionally wait a bit and try to adjust the speed? Or should you just rock out the Update(...) calls as fast as they can go?

I'm also planning to add the ability to have parallel update and rendering loops on separate threads; each keeping their own time and handling their own problems. So I'm wondering if anyone has some advice for me on this front as well.

Wow, big post. Any input/tips/advice will be greatly appreciated. I'm just trying to figure out where I'm going with my ideas and what things I should be aware of before I make big, time consuming mistakes!

Share this post


Link to post
Share on other sites
Hodgman    51342
Quote:
Original post by keinmann
What things do I need to look up and learn about to make an effective graphics settings system?
I'm not particularly familiar with the API, but DX11 has "feature levels" that describe what the graphics card is capable of. If you're using new features added in DX10/11, but want to have fallbacks for older-cards, make sure you check the card's feature level.
Quote:
Question is, what is the best way to ensure you stay within a reasonable tolerance of your update interval? What if the loop completes super fast and you have only a tiny bit of elapsed time between updates? Do you intentionally wait a bit and try to adjust the speed? Or should you just rock out the Update(...) calls as fast as they can go?
A lot of games use a fixed time-step, where update is only called if 16.67ms have elapsed. If 33.3ms have elapsed, you call update twice, etc...
If less than 16ms have elapsed, you hand your time-slice back to the CPU.
On Windows there's functions like YieldProcessor, SwitchToThread, Sleep, etc for this.
Quote:
I'm also planning to add the ability to have parallel update and rendering loops on separate threads; each keeping their own time and handling their own problems. So I'm wondering if anyone has some advice for me on this front as well.
If you go down this path, I'd keep them separated and communicate via double-buffered state. To do this, you have two 'communication' structures. At any one time, the Update thread is writing to one, and the Render thread is reading from the other. At the end of each frame, the threads synch up and swap structures with each other.

However, this isn't the most scalable approach to threading -- you're targeting a dual core processor. Quad-core is standard on PCs now, and consoles have been doing ~6 hardware threads for years now.
Another approach is the task-pool model, where you make one worker thread per core (or per hardware thread), and then break up your update and render code into lots of isolated tasks that communicate via asynchronous message passing.

Share this post


Link to post
Share on other sites
CadetUmfer    234
Quote:
Original post by keinmann
Question is, what is the best way to ensure you stay within a reasonable tolerance of your update interval? What if the loop completes super fast and you have only a tiny bit of elapsed time between updates? Do you intentionally wait a bit and try to adjust the speed? Or should you just rock out the Update(...) calls as fast as they can go?


A common way is to use an accumulator.

float accumulator;
const float TimeStep = 0.2f;
public void Frame(float dt) {
accumulator += dt;
while (accumulator > TimeStep) {
accumulator -= TimeStep;
Update(TimeStep); // fixed timestep update
}
}

Share this post


Link to post
Share on other sites
Dranith    504
To add to the last post, here is a full article on how to manage fixed timesteps well. It is pretty good.

http://gafferongames.com/game-physics/fix-your-timestep/

Share this post


Link to post
Share on other sites
keinmann    122
Thanks for the answers everyone. And I like the article, Dranith. I've also used variable time-step and just let it run as fast as possible. But now I know exactly how to implement a reliable fixed-timestep system. I think it will be important to do so with the accuracy I demand of the physics, especially aerodynamics.

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  

  • Partner Spotlight

  • Similar Content

    • By RubenRS
      How do i open an image to use it as Texture2D information without D3DX11CreateShaderResourceViewFromFile? And how it works for different formats like (JPG, PNG, BMP, DDS,  etc.)?
      I have an (512 x 512) image with font letters, also i have the position and texcoord of every letter. The main idea is that i want to obtain the image pixel info, use the position and texcoords to create a new texture with one letter and render it. Or am I wrong in something?
    • By thmfrnk
      Hey,
      I found a very interesting blog post here: https://bartwronski.com/2017/04/13/cull-that-cone/
      However, I didn't really got how to use his "TestConeVsSphere" test in 3D (last piece of code on his post). I have the frustumCorners of a 2D Tile cell in ViewSpace and my 3D Cone Origin and Direction, so where to place the "testSphere"? I thought about to also move the Cone into viewspace and put the sphere to the Center of the Cell with the radius of half-cellsize, however what about depth? A sphere does not have inf depth?
      I am missing anything? Any Ideas?
      Thx, Thomas
    • By Modymek
      hi all
      I want to enable and disable shader in MPCH Media player Classic
      the MPCH have shader option using HLSL shaders
      I want the shader to read each file extension before it plays the file
      so if the video file name is video.GR.Mp4 it will play it in Grayscale shader 
      if it is not and standard file name Video.Mp4 without GR. unique extension so it plays standard without shader or end the shader
      here is the shader I have for grayscale
      // $MinimumShaderProfile: ps_2_0
      sampler s0 : register(s0);
      float4 main(float2 tex : TEXCOORD0) : COLOR {
          float c0 = dot(tex2D(s0, tex), float4(0.299, 0.587, 0.114, 0));
          return c0;
      }
       
      I want to add if or block stantement or bloean to detect file name before it call the shader in order to go to the procedure or disable it or goto end direct without it
       
      any thoughts or help
    • By noodleBowl
      I've gotten to part in my DirectX 11 project where I need to pass the MVP matrices to my vertex shader. And I'm a little lost when it comes to the use of the constant buffer with the vertex shader
      I understand I need to set up the constant buffer just like any other buffer:
      1. Create a buffer description with the D3D11_BIND_CONSTANT_BUFFER flag 2. Map my matrix data into the constant buffer 3. Use VSSetConstantBuffers to actually use the buffer But I get lost at the VertexShader part, how does my vertex shader know to use this constant buffer when we get to the shader side of things
      In the example I'm following I see they have this as their vertex shader, but I don't understand how the shader knows to use the MatrixBuffer cbuffer. They just use the members directly. What if there was multiple cbuffer declarations like the Microsoft documentation says you could have?
      //Inside vertex shader cbuffer MatrixBuffer { matrix worldMatrix; matrix viewMatrix; matrix projectionMatrix; }; struct VertexInputType { float4 position : POSITION; float4 color : COLOR; }; struct PixelInputType { float4 position : SV_POSITION; float4 color : COLOR; }; PixelInputType ColorVertexShader(VertexInputType input) { PixelInputType output; // Change the position vector to be 4 units for proper matrix calculations. input.position.w = 1.0f; // Calculate the position of the vertex against the world, view, and projection matrices. output.position = mul(input.position, worldMatrix); output.position = mul(output.position, viewMatrix); output.position = mul(output.position, projectionMatrix); // Store the input color for the pixel shader to use. output.color = input.color; return output; }  
    • By gomidas
      I am trying to add normal map to my project I have an example of a cube: 
      I have normal in my shader I think. Then I set shader resource view for texture (NOT BUMP)
                  device.ImmediateContext.PixelShader.SetShaderResource(0, textureView);             device.ImmediateContext.Draw(VerticesCount,0); What should I do to set my normal map or how it is done in dx11 generally example c++?
  • Popular Now