# DX11 [DX11] Render scene to multiple windows

This topic is 2354 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Hi all, I'm trying to create a level editor and haven't picked up directx since dx9. For simplicity's sake imagine that I have two windows that I need to render my scene to. It's the same scene but need to render it differently for each window i.e one with perspective camera, one with orthographic camera and in wireframe.

I've seen a lot of different explanations of how to do this and these include using multiple devices, multiple swapchains and multiple render targets.

Since this is all new to me could somebody shed some light as to the method I need to use and how to go about it?

I cant seem to find any resources that explain how it all fits together and what each component(device, factory, swapchain, immediate context, render targets) actually do. If there was any information on this I might have a better understanding of it all and a chance to work it out myself.

Any help would be much appreciated, thank you.

##### Share on other sites
You want to use multiple swap chains. A swap chain is your interface for rendering to any particular window. When you create it you bind it to an HWND, and it provides you with a backbuffer which is a render target texture. So then each time you want to render to the window, you set the backbuffer render target as the current render target and then do all of your rendering. Then you call Present on that swap chain, and the contents of the backbuffer are copied to the window.

##### Share on other sites
You might also be interested in taking a look at this thread, which also has some description of the same topic. I assume you are looking for D3D11 material, right???

##### Share on other sites
Thanks Matt and Jason for your quick and helpful replies. It's a bit late in the day to be tinkering right now but I think you've set me along the right track. I'll have a fiddle and see what I can come up with tmw and post if I have any further questions.

Oh and also I would like to mention how funny it is that only last week did I ask for your book to be put on my xmas wishlist and have a feeling it might be wrapped up somewhere in the house haha. If only I could find it there might not have been a need for this post after all.

Many thanks.

##### Share on other sites
For all of our sakes, I hope your not on the naughty list this year

##### Share on other sites
Forgive me for this nooby question but could you explain the purpose of the immediate context to me. As I am at the very start of implementing DX into my winform editor I merely have this to change the window to red:
 void Engine::Render() { float clearColor[] = {1.0f, 0, 0, 1.0f}; _ImmediateContext->ClearRenderTargetView(_RtvBackbuffer, clearColor); _SwapChain->Present(0, 0); } 

Am I correct in thinking I only need the one immediate context and if I wanted to render to two windows and different colours it would be as such:
 void Engine::Render() { float clearColor[] = {1.0f, 0, 0, 1.0f}; _ImmediateContext->ClearRenderTargetView(_RtvBackbuffer[0], clearColor); _SwapChain[0]->Present(0, 0); clearColor[] = {0, 1.0f, 0, 1.0f}; _ImmediateContext->ClearRenderTargetView(_RtvBackbuffer[1], clearColor); _SwapChain[1]->Present(0, 0); } 

Finally, and I'm getting ahead of myself here, but when I come to rendering models/simple triangles with vertex buffers; what is it that I need to alter to render in wireframe mode? As I understand it, its a rasterizer state that can be set on the device...but surely that would make all render targets draw in wireframe when I only want a certain window. I take it I set wireframe setting in a shader and render that swapchain rendertargetview separately with that shader?

Oh and finally, finally, what is OMSetRenderTargets used for? Its used on all the samples I have, even the most basic directx11 tutorial where they only create the window and colour the window as I have with ClearRenderTargetView but mine seems to do the same job without it. My guess was that its sole purpose was to set the device to render to multiple targets at once yet all the dx samples use it and they only ever have the one window.

Many thanks to anyone who could shed some light on all this for me, I really wish there were some better resources about for learning all this stuff.

##### Share on other sites
The basic layout of the API is that you have a ID3D11Device which is responsible for all D3D object creation, while there is an ID3D11DeviceContext which is responsible for actually setting state and drawing something. The device context is essentially your way of interacting with the rendering pipeline to get something done.

With D3D11 there is the concept of an immediate device context and a deferred device context. The deferred variant is only used for multithreaded rendering support, which you can safely ignore for now until you get the basics down. So in this case, you will use the immediate context for all of your interactions with the pipeline, and use the device itself to create resources.

1. Your second code snippet is correct, as long as the two render target views were acquired for the swap chain of the window that you want to render into. You render into this RTV, and when you are done then you present the results to the window through the swap chain interface (that you created) for that window.

2. Fill mode is a part of the Rasterizer state, so you would set it there. This involves creating a state object with the desired settings, then binding that state to the pipeline through the immediate context (ID3D11DeviceContext::RSSetState()). If you want to draw different windows with different fill modes, you just need to create separate state objects and use them accordingly when rendering to each window.

3. The OM stands for Output Merger, which is the last stage in the pipeline. This is where you bind a render target view to the pipeline to receive the output of the pipeline. You may not need to use it right now since you are just clearing the resource color, but once you start doing some rendering then you will need to bind the render targets to the pipeline.

There are some good resources out there (and some not so good too...), but if you are a complete beginner to the topic then I would recommend getting a book or two to get you going. Some of these old journal posts might help you get started too:

Direct3D 11 Programming Tip #1

Direct3D 11 Programming Tip #2
Direct3D 11 Programming Tip #3
Direct3D 11 Programming Tip #4
Direct3D 11 Programming Tip #5
Direct3D 11 Programming Tip #6

##### Share on other sites
Thanks again Jason, again you've been quick and concise and have my gratitude. You've cleared up a lot about the pipeline for me, I wish it was easier to find such clear info elsewhere. I will get onto reading those articles post haste.

You sir have earned yourself a 'like'.

Much appreciated.

##### Share on other sites
Oh one more quick question and then I'll stop bugging you for a while I promise. This is just so I know for later when I start some proper rendering. If in my scenario I have:
• 1 scene
• 4 windows(1 is a perspective viewpoint and the other 3 are orthographic, wireframed and the cameras are set at different positions).This means I have 4 swapchains and their accompanying rtv's.

Now let me know if I've got this wrong but wouldn't I have to set the rasterizer state on the device context to a solid state to render the first window and then have to change the rasterizer state to wireframe and render the next 3 windows? In which case doesnt that meant I couldn't use OMSetRenderTargets to set all 4 rtv's as they would all be drawn the same using only the rasterizer state that is currently set on the context? Would I have to individually set each rtv to the context using OMSetRenderTargets each time I rendered a different window? Ive seen that you can pass in multiple rtv's into OMSetRenderTargets at once so would it be possible for me to do that and yet still receive the desired different rendering for each window or would all rtv's be drawn the same?

##### Share on other sites
You would need to set the render target for each swap chain one at a time, draw, present, and then switch to the render target for the next display. Multiple render targets doesn't work for your scenario of having multiple displays, since with multiple render targets every triangle you draw gets rasterized the same way to every render target that's bound. So the only thing that changes is the pixel color/value that you write out from your pixel shader. In your case you want to set each render target individually, because each you will render with a different viewpoint (as well as rasterizer settings for wireframe) for each window.

• 10
• 17
• 9
• 13
• 41
• ### Similar Content

• By chiffre
Introduction:
In general my questions pertain to the differences between floating- and fixed-point data. Additionally I would like to understand when it can be advantageous to prefer fixed-point representation over floating-point representation in the context of vertex data and how the hardware deals with the different data-types. I believe I should be able to reduce the amount of data (bytes) necessary per vertex by choosing the most opportune representations for my vertex attributes. Thanks ahead of time if you, the reader, are considering the effort of reading this and helping me.
I found an old topic that shows this is possible in principal, but I am not sure I understand what the pitfalls are when using fixed-point representation and whether there are any hardware-based performance advantages/disadvantages.
(TLDR at bottom)
The Actual Post:
To my understanding HLSL/D3D11 offers not just the traditional floating point model in half-,single-, and double-precision, but also the fixed-point model in form of signed/unsigned normalized integers in 8-,10-,16-,24-, and 32-bit variants. Both models offer a finite sequence of "grid-points". The obvious difference between the two models is that the fixed-point model offers a constant spacing between values in the normalized range of [0,1] or [-1,1], while the floating point model allows for smaller "deltas" as you get closer to 0, and larger "deltas" the further you are away from 0.
To add some context, let me define a struct as an example:
struct VertexData { float[3] position; //3x32-bits float[2] texCoord; //2x32-bits float[3] normals; //3x32-bits } //Total of 32 bytes Every vertex gets a position, a coordinate on my texture, and a normal to do some light calculations. In this case we have 8x32=256bits per vertex. Since the texture coordinates lie in the interval [0,1] and the normal vector components are in the interval [-1,1] it would seem useful to use normalized representation as suggested in the topic linked at the top of the post. The texture coordinates might as well be represented in a fixed-point model, because it seems most useful to be able to sample the texture in a uniform manner, as the pixels don't get any "denser" as we get closer to 0. In other words the "delta" does not need to become any smaller as the texture coordinates approach (0,0). A similar argument can be made for the normal-vector, as a normal vector should be normalized anyway, and we want as many points as possible on the sphere around (0,0,0) with a radius of 1, and we don't care about precision around the origin. Even if we have large textures such as 4k by 4k (or the maximum allowed by D3D11, 16k by 16k) we only need as many grid-points on one axis, as there are pixels on one axis. An unsigned normalized 14 bit integer would be ideal, but because it is both unsupported and impractical, we will stick to an unsigned normalized 16 bit integer. The same type should take care of the normal vector coordinates, and might even be a bit overkill.
struct VertexData { float[3] position; //3x32-bits uint16_t[2] texCoord; //2x16bits uint16_t[3] normals; //3x16bits } //Total of 22 bytes Seems like a good start, and we might even be able to take it further, but before we pursue that path, here is my first question: can the GPU even work with the data in this format, or is all I have accomplished minimizing CPU-side RAM usage? Does the GPU have to convert the texture coordinates back to a floating-point model when I hand them over to the sampler in my pixel shader? I have looked up the data types for HLSL and I am not sure I even comprehend how to declare the vertex input type in HLSL. Would the following work?
struct VertexInputType { float3 pos; //this one is obvious unorm half2 tex; //half corresponds to a 16-bit float, so I assume this is wrong, but this the only 16-bit type I found on the linked MSDN site snorm half3 normal; //same as above } I assume this is possible somehow, as I have found input element formats such as: DXGI_FORMAT_R16G16B16A16_SNORM and DXGI_FORMAT_R16G16B16A16_UNORM (also available with a different number of components, as well as different component lengths). I might have to avoid 3-component vectors because there is no 3-component 16-bit input element format, but that is the least of my worries. The next question would be: what happens with my normals if I try to do lighting calculations with them in such a normalized-fixed-point format? Is there no issue as long as I take care not to mix floating- and fixed-point data? Or would that work as well? In general this gives rise to the question: how does the GPU handle fixed-point arithmetic? Is it the same as integer-arithmetic, and/or is it faster/slower than floating-point arithmetic?
Assuming that we still have a valid and useful VertexData format, how far could I take this while remaining on the sensible side of what could be called optimization? Theoretically I could use the an input element format such as DXGI_FORMAT_R10G10B10A2_UNORM to pack my normal coordinates into a 10-bit fixed-point format, and my verticies (in object space) might even be representable in a 16-bit unsigned normalized fixed-point format. That way I could end up with something like the following struct:
struct VertexData { uint16_t[3] pos; //3x16bits uint16_t[2] texCoord; //2x16bits uint32_t packedNormals; //10+10+10+2bits } //Total of 14 bytes Could I use a vertex structure like this without too much performance-loss on the GPU-side? If the GPU has to execute some sort of unpacking algorithm in the background I might as well let it be. In the end I have a functioning deferred renderer, but I would like to reduce the memory footprint of the huge amount of vertecies involved in rendering my landscape.
TLDR: I have a lot of vertices that I need to render and I want to reduce the RAM-usage without introducing crazy compression/decompression algorithms to the CPU or GPU. I am hoping to find a solution by involving fixed-point data-types, but I am not exactly sure how how that would work.
• By cozzie
Hi all,
I was wondering it it matters in which order you draw 2D and 3D items, looking at the BeginDraw/EndDraw calls on a D2D rendertarget.
The order in which you do the actual draw calls is clear, 3D first then 2D, means the 2D (DrawText in this case) is in front of the 3D scene.
The question is mainly about when to call the BeginDraw and EndDraw.
Note that I'm drawing D2D stuff through a DXGI surface linked to the 3D RT.
Option 1:
A - Begin frame, clear D3D RT
B - Draw 3D
C - BeginDraw D2D RT
D - Draw 2D
E - EndDraw D2D RT
F - Present
Option 2:
A - Begin frame, clear D3D RT + BeginDraw D2D RT
B - Draw 3D
C - Draw 2D
D - EndDraw D2D RT
E- Present
Would there be a difference (performance/issue?) in using option 2? (versus 1)
Any input is appreciated.

• Do you know any papers that cover custom data structures like lists or binary trees implemented in hlsl without CUDA that work perfectly fine no matter how many threads try to use them at any given time?
• By cozzie
Hi all,
Last week I noticed that when I run my test application(s) in Renderdoc, it crashes when it enable my code that uses D2D/DirectWrite. In Visual Studio no issues occur (debug or release), but when I run the same executable in Renderdoc, it crashes somehow (assert of D2D rendertarget or without any information). Before I spend hours on debugging/ figuring it out, does someone have experience with this symptom and/or know if Renderdoc has known issues with D2D? (if so, that would be bad news for debugging my application in the future );
I can also post some more information on what happens, code and which code commented out, eliminates the problems (when running in RenderDoc).
Any input is appreciated.

• Hi Guys,
I understand how to create input layouts etc... But I am wondering is it at all possible to derive an input layout from a shader and create the input layout directly from this? (Rather than manually specifying the input layout format?)