• 12
• 12
• 9
• 10
• 13
• ### Similar Content

• By elect
Hi,
ok, so, we are having problems with our current mirror reflection implementation.
At the moment we are doing it very simple, so for the i-th frame, we calculate the reflection vectors given the viewPoint and some predefined points on the mirror surface (position and normal).
Then, using the least squared algorithm, we find the point that has the minimum distance from all these reflections vectors. This is going to be our virtual viewPoint (with the right orientation).
After that, we render offscreen to a texture by setting the OpenGL camera on the virtual viewPoint.
And finally we use the rendered texture on the mirror surface.
So far this has always been fine, but now we are having some more strong constraints on accuracy.
What are our best options given that:
- we have a dynamic scene, the mirror and parts of the scene can change continuously from frame to frame
- we have about 3k points (with normals) per mirror, calculated offline using some cad program (such as Catia)
- all the mirror are always perfectly spherical (with different radius vertically and horizontally) and they are always convex
- a scene can have up to 10 mirror
- it should be fast enough also for vr (Htc Vive) on fastest gpus (only desktops)

Looking around, some papers talk about calculating some caustic surface derivation offline, but I don't know if this suits my case
Also, another paper, used some acceleration structures to detect the intersection between the reflection vectors and the scene, and then adjust the corresponding texture coordinate. This looks the most accurate but also very heavy from a computational point of view.

Other than that, I couldn't find anything updated/exhaustive around, can you help me?

• Hello all,
I am currently working on a game engine for use with my game development that I would like to be as flexible as possible.  As such the exact requirements for how things should work can't be nailed down to a specific implementation and I am looking for, at least now, a default good average case scenario design.
Here is what I have implemented:
Deferred rendering using OpenGL Arbitrary number of lights and shadow mapping Each rendered object, as defined by a set of geometry, textures, animation data, and a model matrix is rendered with its own draw call Skeletal animations implemented on the GPU.   Model matrix transformation implemented on the GPU Frustum and octree culling for optimization Here are my questions and concerns:
Doing the skeletal animation on the GPU, currently, requires doing the skinning for each object multiple times per frame: once for the initial geometry rendering and once for the shadow map rendering for each light for which it is not culled.  This seems very inefficient.  Is there a way to do skeletal animation on the GPU only once across these render calls? Without doing the model matrix transformation on the CPU, I fail to see how I can easily batch objects with the same textures and shaders in a single draw call without passing a ton of matrix data to the GPU (an array of model matrices then an index for each vertex into that array for transformation purposes?) If I do the matrix transformations on the CPU, It seems I can't really do the skinning on the GPU as the pre-transformed vertexes will wreck havoc with the calculations, so this seems not viable unless I am missing something Overall it seems like simplest solution is to just do all of the vertex manipulation on the CPU and pass the pre-transformed data to the GPU, using vertex shaders that do basically nothing.  This doesn't seem the most efficient use of the graphics hardware, but could potentially reduce the number of draw calls needed.

Really, I am looking for some advice on how to proceed with this, how something like this is typically handled.  Are the multiple draw calls and skinning calculations not a huge deal?  I would LIKE to save as much of the CPU's time per frame so it can be tasked with other things, as to keep CPU resources open to the implementation of the engine.  However, that becomes a moot point if the GPU becomes a bottleneck.

• Hello!
I would like to introduce Diligent Engine, a project that I've been recently working on. Diligent Engine is a light-weight cross-platform abstraction layer between the application and the platform-specific graphics API. Its main goal is to take advantages of the next-generation APIs such as Direct3D12 and Vulkan, but at the same time provide support for older platforms via Direct3D11, OpenGL and OpenGLES. Diligent Engine exposes common front-end for all supported platforms and provides interoperability with underlying native API. Shader source code converter allows shaders authored in HLSL to be translated to GLSL and used on all platforms. Diligent Engine supports integration with Unity and is designed to be used as a graphics subsystem in a standalone game engine, Unity native plugin or any other 3D application. It is distributed under Apache 2.0 license and is free to use. Full source code is available for download on GitHub.
Features:
True cross-platform Exact same client code for all supported platforms and rendering backends No #if defined(_WIN32) ... #elif defined(LINUX) ... #elif defined(ANDROID) ... No #if defined(D3D11) ... #elif defined(D3D12) ... #elif defined(OPENGL) ... Exact same HLSL shaders run on all platforms and all backends Modular design Components are clearly separated logically and physically and can be used as needed Only take what you need for your project (do not want to keep samples and tutorials in your codebase? Simply remove Samples submodule. Only need core functionality? Use only Core submodule) No 15000 lines-of-code files Clear object-based interface No global states Key graphics features: Automatic shader resource binding designed to leverage the next-generation rendering APIs Multithreaded command buffer generation 50,000 draw calls at 300 fps with D3D12 backend Descriptor, memory and resource state management Modern c++ features to make code fast and reliable The following platforms and low-level APIs are currently supported:
Windows Desktop: Direct3D11, Direct3D12, OpenGL Universal Windows: Direct3D11, Direct3D12 Linux: OpenGL Android: OpenGLES MacOS: OpenGL iOS: OpenGLES API Basics
Initialization
The engine can perform initialization of the API or attach to already existing D3D11/D3D12 device or OpenGL/GLES context. For instance, the following code shows how the engine can be initialized in D3D12 mode:
#include "RenderDeviceFactoryD3D12.h" using namespace Diligent; // ...  GetEngineFactoryD3D12Type GetEngineFactoryD3D12 = nullptr; // Load the dll and import GetEngineFactoryD3D12() function LoadGraphicsEngineD3D12(GetEngineFactoryD3D12); auto *pFactoryD3D11 = GetEngineFactoryD3D12(); EngineD3D12Attribs EngD3D12Attribs; EngD3D12Attribs.CPUDescriptorHeapAllocationSize[0] = 1024; EngD3D12Attribs.CPUDescriptorHeapAllocationSize[1] = 32; EngD3D12Attribs.CPUDescriptorHeapAllocationSize[2] = 16; EngD3D12Attribs.CPUDescriptorHeapAllocationSize[3] = 16; EngD3D12Attribs.NumCommandsToFlushCmdList = 64; RefCntAutoPtr<IRenderDevice> pRenderDevice; RefCntAutoPtr<IDeviceContext> pImmediateContext; SwapChainDesc SwapChainDesc; RefCntAutoPtr<ISwapChain> pSwapChain; pFactoryD3D11->CreateDeviceAndContextsD3D12( EngD3D12Attribs, &pRenderDevice, &pImmediateContext, 0 ); pFactoryD3D11->CreateSwapChainD3D12( pRenderDevice, pImmediateContext, SwapChainDesc, hWnd, &pSwapChain ); Creating Resources
Device resources are created by the render device. The two main resource types are buffers, which represent linear memory, and textures, which use memory layouts optimized for fast filtering. To create a buffer, you need to populate BufferDesc structure and call IRenderDevice::CreateBuffer(). The following code creates a uniform (constant) buffer:
BufferDesc BuffDesc; BufferDesc.Name = "Uniform buffer"; BuffDesc.BindFlags = BIND_UNIFORM_BUFFER; BuffDesc.Usage = USAGE_DYNAMIC; BuffDesc.uiSizeInBytes = sizeof(ShaderConstants); BuffDesc.CPUAccessFlags = CPU_ACCESS_WRITE; m_pDevice->CreateBuffer( BuffDesc, BufferData(), &m_pConstantBuffer ); Similar, to create a texture, populate TextureDesc structure and call IRenderDevice::CreateTexture() as in the following example:
TextureDesc TexDesc; TexDesc.Name = "My texture 2D"; TexDesc.Type = TEXTURE_TYPE_2D; TexDesc.Width = 1024; TexDesc.Height = 1024; TexDesc.Format = TEX_FORMAT_RGBA8_UNORM; TexDesc.Usage = USAGE_DEFAULT; TexDesc.BindFlags = BIND_SHADER_RESOURCE | BIND_RENDER_TARGET | BIND_UNORDERED_ACCESS; TexDesc.Name = "Sample 2D Texture"; m_pRenderDevice->CreateTexture( TexDesc, TextureData(), &m_pTestTex ); Initializing Pipeline State
Diligent Engine follows Direct3D12 style to configure the graphics/compute pipeline. One big Pipelines State Object (PSO) encompasses all required states (all shader stages, input layout description, depth stencil, rasterizer and blend state descriptions etc.)
To create a shader, populate ShaderCreationAttribs structure. An important member is ShaderCreationAttribs::SourceLanguage. The following are valid values for this member:
SHADER_SOURCE_LANGUAGE_DEFAULT  - The shader source format matches the underlying graphics API: HLSL for D3D11 or D3D12 mode, and GLSL for OpenGL and OpenGLES modes. SHADER_SOURCE_LANGUAGE_HLSL  - The shader source is in HLSL. For OpenGL and OpenGLES modes, the source code will be converted to GLSL. See shader converter for details. SHADER_SOURCE_LANGUAGE_GLSL  - The shader source is in GLSL. There is currently no GLSL to HLSL converter. To allow grouping of resources based on the frequency of expected change, Diligent Engine introduces classification of shader variables:
Static variables (SHADER_VARIABLE_TYPE_STATIC) are variables that are expected to be set only once. They may not be changed once a resource is bound to the variable. Such variables are intended to hold global constants such as camera attributes or global light attributes constant buffers. Mutable variables (SHADER_VARIABLE_TYPE_MUTABLE) define resources that are expected to change on a per-material frequency. Examples may include diffuse textures, normal maps etc. Dynamic variables (SHADER_VARIABLE_TYPE_DYNAMIC) are expected to change frequently and randomly. This post describes the resource binding model in Diligent Engine.
The following is an example of shader initialization:
To create a pipeline state object, define instance of PipelineStateDesc structure. The structure defines the pipeline specifics such as if the pipeline is a compute pipeline, number and format of render targets as well as depth-stencil format:
// This is a graphics pipeline PSODesc.IsComputePipeline = false; PSODesc.GraphicsPipeline.NumRenderTargets = 1; PSODesc.GraphicsPipeline.RTVFormats[0] = TEX_FORMAT_RGBA8_UNORM_SRGB; PSODesc.GraphicsPipeline.DSVFormat = TEX_FORMAT_D32_FLOAT; The structure also defines depth-stencil, rasterizer, blend state, input layout and other parameters. For instance, rasterizer state can be defined as in the code snippet below:
// Init rasterizer state RasterizerStateDesc &RasterizerDesc = PSODesc.GraphicsPipeline.RasterizerDesc; RasterizerDesc.FillMode = FILL_MODE_SOLID; RasterizerDesc.CullMode = CULL_MODE_NONE; RasterizerDesc.FrontCounterClockwise = True; RasterizerDesc.ScissorEnable = True; //RSDesc.MultisampleEnable = false; // do not allow msaa (fonts would be degraded) RasterizerDesc.AntialiasedLineEnable = False; When all fields are populated, call IRenderDevice::CreatePipelineState() to create the PSO:
Shader resource binding in Diligent Engine is based on grouping variables in 3 different groups (static, mutable and dynamic). Static variables are variables that are expected to be set only once. They may not be changed once a resource is bound to the variable. Such variables are intended to hold global constants such as camera attributes or global light attributes constant buffers. They are bound directly to the shader object:

m_pPSO->CreateShaderResourceBinding(&m_pSRB); Dynamic and mutable resources are then bound through SRB object:
m_pSRB->GetVariable(SHADER_TYPE_VERTEX, "tex2DDiffuse")->Set(pDiffuseTexSRV); m_pSRB->GetVariable(SHADER_TYPE_VERTEX, "cbRandomAttribs")->Set(pRandomAttrsCB); The difference between mutable and dynamic resources is that mutable ones can only be set once for every instance of a shader resource binding. Dynamic resources can be set multiple times. It is important to properly set the variable type as this may affect performance. Static variables are generally most efficient, followed by mutable. Dynamic variables are most expensive from performance point of view. This post explains shader resource binding in more details.
Setting the Pipeline State and Invoking Draw Command
Before any draw command can be invoked, all required vertex and index buffers as well as the pipeline state should be bound to the device context:
// Clear render target const float zero[4] = {0, 0, 0, 0}; m_pContext->ClearRenderTarget(nullptr, zero); // Set vertex and index buffers IBuffer *buffer[] = {m_pVertexBuffer}; Uint32 offsets[] = {0}; Uint32 strides[] = {sizeof(MyVertex)}; m_pContext->SetVertexBuffers(0, 1, buffer, strides, offsets, SET_VERTEX_BUFFERS_FLAG_RESET); m_pContext->SetIndexBuffer(m_pIndexBuffer, 0); m_pContext->SetPipelineState(m_pPSO); Also, all shader resources must be committed to the device context:
m_pContext->CommitShaderResources(m_pSRB, COMMIT_SHADER_RESOURCES_FLAG_TRANSITION_RESOURCES); When all required states and resources are bound, IDeviceContext::Draw() can be used to execute draw command or IDeviceContext::DispatchCompute() can be used to execute compute command. Note that for a draw command, graphics pipeline must be bound, and for dispatch command, compute pipeline must be bound. Draw() takes DrawAttribs structure as an argument. The structure members define all attributes required to perform the command (primitive topology, number of vertices or indices, if draw call is indexed or not, if draw call is instanced or not, if draw call is indirect or not, etc.). For example:
DrawAttribs attrs; attrs.IsIndexed = true; attrs.IndexType = VT_UINT16; attrs.NumIndices = 36; attrs.Topology = PRIMITIVE_TOPOLOGY_TRIANGLE_LIST; pContext->Draw(attrs); Tutorials and Samples
The GitHub repository contains a number of tutorials and sample applications that demonstrate the API usage.

AntTweakBar sample demonstrates how to use AntTweakBar library to create simple user interface.

Atmospheric scattering sample is a more advanced example. It demonstrates how Diligent Engine can be used to implement various rendering tasks: loading textures from files, using complex shaders, rendering to textures, using compute shaders and unordered access views, etc.

The repository includes Asteroids performance benchmark based on this demo developed by Intel. It renders 50,000 unique textured asteroids and lets compare performance of D3D11 and D3D12 implementations. Every asteroid is a combination of one of 1000 unique meshes and one of 10 unique textures.

Integration with Unity
Diligent Engine supports integration with Unity through Unity low-level native plugin interface. The engine relies on Native API Interoperability to attach to the graphics API initialized by Unity. After Diligent Engine device and context are created, they can be used us usual to create resources and issue rendering commands. GhostCubePlugin shows an example how Diligent Engine can be used to render a ghost cube only visible as a reflection in a mirror.

• By Yxjmir
I'm trying to load data from a .gltf file into a struct to use to load a .bin file. I don't think there is a problem with how the vertex positions are loaded, but with the indices. This is what I get when drawing with glDrawArrays(GL_LINES, ...):

Also, using glDrawElements gives a similar result. Since it looks like its drawing triangles using the wrong vertices for each face, I'm assuming it needs an index buffer/element buffer. (I'm not sure why there is a line going through part of it, it doesn't look like it belongs to a side, re-exported it without texture coordinates checked, and its not there)
I'm using jsoncpp to load the GLTF file, its format is based on JSON. Here is the gltf struct I'm using, and how I parse the file:
glBindVertexArray(g_pGame->m_VAO);
glDrawElements(GL_LINES, g_pGame->m_indices.size(), GL_UNSIGNED_BYTE, (void*)0); // Only shows with GL_UNSIGNED_BYTE
glDrawArrays(GL_LINES, 0, g_pGame->m_vertexCount);
So, I'm asking what type should I use for the indices? it doesn't seem to be unsigned short, which is what I selected with the Khronos Group Exporter for blender. Also, am I reading part or all of the .bin file wrong?
Test.gltf
Test.bin

• That means how do I use base DirectX or OpenGL api's to make a physics based destruction simulation?
Will it be just smart rendering or something else is required?

# OpenGL [SOLVED] D3D11 and Direct2D

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

## Recommended Posts

##### Share on other sites
Have you used the D3D11_CREATE_DEVICE_BGRA_SUPPORT flag when creating the device? This is required for Direct2D interoperability. See D3D11_CREATE_DEVICE_FLAG in the SDK docs.

##### Share on other sites
AFAIK D3D11/Direct2D interop is not implemented yet, maybe in the next SDK.

##### Share on other sites
There was a long thread about this not long ago, with several posts from someone on the DirectX team, as well as reports from people using it in different ways. If you read it all the way through it should give you a lot of information on this: http://www.gamedev.net/community/forums/topic.asp?topic_id=547920.

##### Share on other sites
Quote:
 Original post by ET3DHave you used the D3D11_CREATE_DEVICE_BGRA_SUPPORT flag when creating the device? This is required for Direct2D interoperability. See D3D11_CREATE_DEVICE_FLAG in the SDK docs.

I'm using D3D10_CREATE_DEVICE_BGRA_SUPPORT at the moment. I can change this to D3D11_CREATE_DEVICE_BGRA_SUPPORT tonight but I have a feeling it will not matter - sadly. Thanks though!

Erik: I've read it through (thus the 2 devices comment in my original post) - but couldn't get it to work as OpenSharedResource fails with E_INVALIDARG. Definitely a coding error on my behalf due to being relatively new to D3D (coming from OpenGL). And unless I missed it there was no code samples other than the pseudo code ones. Sadly, neither the DXSDK (August 2009) nor the 7.0A WinSDK seem to provide samples for D2D at all unless I missed a setting somewhere. (they do both provide headers and libs for it though *sigh*)

I would rather get the HWND-method working if at all possible rather than the two-device method though. If they do provide proper interop soon enough the HWND-method would only require one #define and two lines change.

It would be nice to get some feedback on "we're working on this" or "not going to happen at all" because if it's soon enough I could work on other parts of the code in the meantime. If not at all, biting the ugly bullet would be the only way.

##### Share on other sites
Quote:
 Original post by DEVLiNI'm using D3D10_CREATE_DEVICE_BGRA_SUPPORT at the moment. I can change this to D3D11_CREATE_DEVICE_BGRA_SUPPORT tonight but I have a feeling it will not matter - sadly. Thanks though!

I suspect you're right, since they have the same value.

There's a D2D-D3D interop sample here at Microsoft's site. It uses D3D 10.1, which may be good enough for you.

##### Share on other sites
Make sure the D3D11 and D3D10.1 device are created on the same DXGI1.1 adapter, and create the shared texture with render target as well as shader resource usage. Also remember the D3D10.1 device must also use the BGRA flag. For me this doesn't work with feature level 10.0 (I seem to recall there was a mention in the old thread that BGRA was removed in 10.0), and I need to use the 9.3 feature level. On my laptop I must use 9.1.

Here's an example I've tested with, it's just one function creating the resources from top to bottom that you can compare with if you still get errors (it should run pasted to an empty VC++ project). It uses CopyResource to put the D2D content in the back-buffer which you probably don't want, but the set-up is the same and it's a bit less code than setting up shaders to draw it with a quad.
#include <windows.h>#include <D3D11.h>#include <D3D10_1.h>#include <D2D1.h>#include <DXErr.h>#include <DXGI.h>// Libs#pragma comment (lib, "D3D11.lib")#pragma comment (lib, "D3D10_1.lib")#pragma comment (lib, "D2D1.lib")#pragma comment (lib, "DXErr.lib")#pragma comment (lib, "DXGI.lib")LRESULT CALLBACK WndProc(HWND hWnd, UINT msg, WPARAM wParam, LPARAM lParam);// Mainint WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow) {	// Register windowclass	WNDCLASSEX wc;	ZeroMemory(&wc, sizeof(wc));	wc.cbSize = sizeof(wc);	wc.lpszClassName = TEXT("MyClass");	wc.hInstance = hInstance;	wc.lpfnWndProc = WndProc;	wc.hCursor = LoadCursor(NULL, IDC_ARROW);	wc.hIcon = LoadIcon(NULL, IDI_APPLICATION);	RegisterClassEx(&wc);		// Create window	HWND hWnd = CreateWindow(		wc.lpszClassName,		TEXT("D3D11 with Direct2D"),		WS_OVERLAPPEDWINDOW,		CW_USEDEFAULT,		CW_USEDEFAULT,		CW_USEDEFAULT,		CW_USEDEFAULT,		NULL,		NULL,		hInstance,		NULL	);		// Create DXGI factory to enumerate adapters	IDXGIFactory1 *pDXGIFactory;		HRESULT hResult = CreateDXGIFactory1(__uuidof(IDXGIFactory1), (void**)&pDXGIFactory);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("CreateDXGIFactory1"), MB_OK);		return 0;	}		// Use the first adapter	IDXGIAdapter1 *pAdapter;		hResult = pDXGIFactory->EnumAdapters1(0, &pAdapter);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("EnumAdapters1"), MB_OK);		return 0;	}		pDXGIFactory->Release();		// Create D3D11 device and swapchain	DXGI_SWAP_CHAIN_DESC scd;	ID3D11Device *pDevice11;	IDXGISwapChain *pSwapChain;	ID3D11DeviceContext *pImmediateContext;		ZeroMemory(&scd, sizeof(scd));	scd.BufferDesc.Format = DXGI_FORMAT_B8G8R8A8_UNORM;	scd.SampleDesc.Count = 1;	scd.BufferUsage = DXGI_USAGE_RENDER_TARGET_OUTPUT;	scd.BufferCount = 1;	scd.OutputWindow = hWnd;	scd.SwapEffect = DXGI_SWAP_EFFECT_DISCARD;	scd.Windowed = TRUE;		hResult = D3D11CreateDeviceAndSwapChain(		pAdapter,		D3D_DRIVER_TYPE_UNKNOWN,		NULL,		D3D11_CREATE_DEVICE_DEBUG |			D3D11_CREATE_DEVICE_BGRA_SUPPORT |			D3D11_CREATE_DEVICE_SINGLETHREADED,		NULL,		0,		D3D11_SDK_VERSION,		&scd,		&pSwapChain,		&pDevice11,		NULL,		&pImmediateContext	);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("D3D11CreateDeviceAndSwapChain"), MB_OK);		return 0;	}		// Create D3D10.1 device	ID3D10Device1 *pDevice101;		hResult = D3D10CreateDevice1(		pAdapter,		D3D10_DRIVER_TYPE_HARDWARE,		NULL,		D3D10_CREATE_DEVICE_DEBUG |			D3D10_CREATE_DEVICE_BGRA_SUPPORT |			D3D10_CREATE_DEVICE_SINGLETHREADED,		D3D10_FEATURE_LEVEL_9_3,		D3D10_1_SDK_VERSION,		&pDevice101	);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("D3D10CreateDevice1"), MB_OK);		return 0;	}		pAdapter->Release();		// Get the D3D11 back-buffer	ID3D11Texture2D *pBackBuffer11;	D3D11_TEXTURE2D_DESC backBufferDesc;		hResult = pSwapChain->GetBuffer(0, __uuidof(ID3D11Texture2D), reinterpret_cast<void**>(&pBackBuffer11));	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pSwapChain->GetBuffer for ID3D11Texture2D"), MB_OK);		return 0;	}		pBackBuffer11->GetDesc(&backBufferDesc);		// Create the shared texture to draw D2D content to	D3D11_TEXTURE2D_DESC sharedTextureDesc;	ID3D11Texture2D *pSharedTexture11;		ZeroMemory(&sharedTextureDesc, sizeof(sharedTextureDesc));	sharedTextureDesc.Width = backBufferDesc.Width;	sharedTextureDesc.Height = backBufferDesc.Height;	sharedTextureDesc.MipLevels = 1;	sharedTextureDesc.ArraySize = 1;	sharedTextureDesc.Format = DXGI_FORMAT_B8G8R8A8_UNORM;	sharedTextureDesc.SampleDesc.Count = 1;	sharedTextureDesc.Usage = D3D11_USAGE_DEFAULT;	sharedTextureDesc.BindFlags = D3D11_BIND_SHADER_RESOURCE | D3D11_BIND_RENDER_TARGET;	sharedTextureDesc.MiscFlags = D3D11_RESOURCE_MISC_SHARED_KEYEDMUTEX;		hResult = pDevice11->CreateTexture2D(&sharedTextureDesc, NULL, &pSharedTexture11);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pDevice11->CreateTexture2D for shared texture"), MB_OK);		return 0;	}		// Get the keyed mutex for the shared texture (for D3D11)	IDXGIKeyedMutex *pKeyedMutex11;		hResult = pSharedTexture11->QueryInterface(__uuidof(IDXGIKeyedMutex), (void**)&pKeyedMutex11);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pSharedTexture11->QueryInterface for IDXGIKeyedMutex"), MB_OK);		return 0;	}		// Get the shared handle needed to open the shared texture in D3D10.1	IDXGIResource *pSharedResource11;	HANDLE hSharedHandle11;		hResult = pSharedTexture11->QueryInterface(__uuidof(IDXGIResource), (void**)&pSharedResource11);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pSharedTexture11->QueryInterface for IDXGIResource"), MB_OK);		return 0;	}		pSharedResource11->GetSharedHandle(&hSharedHandle11);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pSharedResource11->GetSharedHandle"), MB_OK);		return 0;	}		pSharedResource11->Release();		// Open the surface for the shared texture in D3D10.1	IDXGISurface1 *pSharedSurface10;		hResult = pDevice101->OpenSharedResource(hSharedHandle11, __uuidof(IDXGISurface1), (void**)(&pSharedSurface10));	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pDevice101->OpenSharedResource"), MB_OK);		return 0;	}		// Get the keyed mutex for the shared texture (for D3D10.1)	IDXGIKeyedMutex *pKeyedMutex10;		hResult = pSharedSurface10->QueryInterface(__uuidof(IDXGIKeyedMutex), (void**)&pKeyedMutex10);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pSharedSurface10->QueryInterface for IDXGIKeyedMutex"), MB_OK);		return 0;	}		// Create D2D factory	ID2D1Factory *pD2DFactory;		hResult = D2D1CreateFactory(D2D1_FACTORY_TYPE_SINGLE_THREADED, __uuidof(ID2D1Factory), (void**)&pD2DFactory);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("D2D1CreateFactory"), MB_OK);		return 0;	}		// Create D2D render target from the surface for the shared texture, which was opened in D3D10.1	D2D1_RENDER_TARGET_PROPERTIES renderTargetProperties;	ID2D1RenderTarget *pD2DRenderTarget;		ZeroMemory(&renderTargetProperties, sizeof(renderTargetProperties));	renderTargetProperties.type = D2D1_RENDER_TARGET_TYPE_HARDWARE;	renderTargetProperties.pixelFormat = D2D1::PixelFormat(DXGI_FORMAT_UNKNOWN, D2D1_ALPHA_MODE_PREMULTIPLIED);		hResult = pD2DFactory->CreateDxgiSurfaceRenderTarget(pSharedSurface10, &renderTargetProperties, &pD2DRenderTarget);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pD2DFactory->CreateDxgiSurfaceRenderTarget"), MB_OK);		return 0;	}		pSharedSurface10->Release();	pD2DFactory->Release();		// Create a solid color brush to draw something with	ID2D1SolidColorBrush *pBrush;		hResult = pD2DRenderTarget->CreateSolidColorBrush(D2D1::ColorF(1.0f, 1.0f, 0.0f, 1.0f), &pBrush);	if(FAILED(hResult)) {		MessageBox(NULL, DXGetErrorDescription(hResult), TEXT("pD2DRenderTarget->CreateSolidColorBrush"), MB_OK);		return 0;	}		// Tell the debug output to be quiet..	pDevice101->IASetPrimitiveTopology(D3D10_PRIMITIVE_TOPOLOGY_POINTLIST);		// Main loop	float angle = 0.0f;		ShowWindow(hWnd, nCmdShow);	while(true) {		MSG msg;		if(PeekMessage(&msg, NULL, 0, 0, PM_REMOVE) != 0) {			if(msg.message == WM_QUIT)				break;			else {				TranslateMessage(&msg);				DispatchMessage(&msg);			}		}		else {			// Sync the shared texture for D3D10.1			pKeyedMutex10->AcquireSync(0, INFINITE);						// Draw D2D content			angle += 360.0f / 200.0f;						pD2DRenderTarget->BeginDraw();						pD2DRenderTarget->Clear(D2D1::ColorF(0.0f, 0.7f, 0.0f, 1.0f));						D2D1_SIZE_F size = pD2DRenderTarget->GetSize();						pD2DRenderTarget->SetTransform(D2D1::Matrix3x2F::Rotation(angle, D2D1::Point2F(size.width/2.0f, size.height/2.0f)));						pBrush->SetColor(D2D1::ColorF(1.0f, 1.0f, 0.0f, 1.0f));			pD2DRenderTarget->DrawEllipse(				D2D1::Ellipse(D2D1::Point2F(size.width/2.0f, size.height/2.0f), size.height/3.0f, size.height/3.0f),				pBrush,				32.0f,				NULL			);						pBrush->SetColor(D2D1::ColorF(1.0f, 0.0f, 0.0f, 1.0f));			pD2DRenderTarget->DrawEllipse(				D2D1::Ellipse(D2D1::Point2F(size.width/4.0f, size.height/2.0f), size.height/4.0f, size.height/4.0f),				pBrush,				32.0f,				NULL			);						pBrush->SetColor(D2D1::ColorF(0.0f, 0.0f, 1.0f, 1.0f));			pD2DRenderTarget->DrawEllipse(				D2D1::Ellipse(D2D1::Point2F(size.width*3.0f/4.0f, size.height/2.0f), size.height/4.0f, size.height/4.0f),				pBrush,				32.0f,				NULL			);						pD2DRenderTarget->EndDraw();						// Release sync			pKeyedMutex10->ReleaseSync(1);									// Sync the shared texture for D3D11			pKeyedMutex11->AcquireSync(1, INFINITE);						// Copy the content from the shared texture to the back-buffer			pImmediateContext->CopyResource(pBackBuffer11, pSharedTexture11);						// Release sync			pKeyedMutex11->ReleaseSync(0);									// Present to screen			pSwapChain->Present(1, 0);		}	}		// Release	pSwapChain->SetFullscreenState(FALSE, NULL);		pImmediateContext->ClearState();		pBrush->Release();	pD2DRenderTarget->Release();		pKeyedMutex10->Release();	pKeyedMutex11->Release();	pSharedTexture11->Release();	pBackBuffer11->Release();		pImmediateContext->Flush();		pDevice101->Release();		pImmediateContext->Release();	pSwapChain->Release();	pDevice11->Release();		UnregisterClass(wc.lpszClassName, hInstance);		return 0;}// Window procedureLRESULT CALLBACK WndProc(HWND hWnd, UINT msg, WPARAM wParam, LPARAM lParam) {	switch(msg) {		// Window destroyed.		case WM_DESTROY:			PostQuitMessage(0);		return 0;	}		return DefWindowProc(hWnd, msg, wParam, lParam);}

##### Share on other sites
Thanks a lot guys - I'll give it a try. :)

Just curious though - is there any way to overlay a hwndsurfacerendertarget or is that bound to fail?

##### Share on other sites
I'm not sure, haven't tried that path, but you can create the swap-chain with the GDI compatible flag, and use GetDC on the back-buffer and draw to that with a DC D2D render target. It's not very fast (I think it draws in software, or at least copies to system-memory in between), but if you only draw to part of the screen and specify an update rectangle it isn't very slow.