Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Beginner
90 Views

Direct3D11 with GDI Compatible creates the Drawing artifacts

Hi All.
I'm using Direct3D11 with GDI compatible, but i have some artifacts on some new Intel GPU(530, 630)
 
Steps to Reproduce:
-------------------------------
 
1) Init Direct3D11 API: Create IDXGISwapChain with GDI Compatible:
 
DXGI_SWAP_CHAIN_DESC::Flags = DXGI_SWAP_CHAIN_FLAG_ALLOW_MODE_SWITCH;
DXGI_SWAP_CHAIN_DESC::BufferDesc.Format = DXGI_FORMAT_B8G8R8A8_UNORM;

2)

IDXGISurface1: IDXGISwapChain->GetBuffer(0, __uuidof(IDXGISurface1), reinterpret_cast<void **>(&pDXGISurface));

3) Drawing Pseudocode Code:

ID3D11DeviceContext::OMSetRenderTargets, ClearRenderTargetView, ClearDepthStencilView
//Draw 3D data normaly...
3. Draw GDI Text:
HDC dxgiHDC = 0;
IDXGISurface1::GetDC(FALSE, &dxgiHDC); 
//DrawText using GDI functions
IDXGISurface1::ReleaseDC(0);
4. End Drawing:
IDXGISwapChain::Present(0, 0); 

 

Expected Results:
-------------------------------
 
 
Actual Results:
-------------------------------
Direct3D11_GDI_Bug.png
 
Additional Information:
-------------------------------
1. Bug is not reproduced on AMD/nVidia, also on Intel HD 4000, Intel HD 4600.
2.Do you need some minimal test application ?
 
System Setup Information:
-----------------------------------------  
 
System Used: Dell Inc, OptiPlex 7040 
CPU SKU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 3408 Mhz, 4 Core(s), 8 Logical Processor(s) 
GPU SKU: Intel HD Graphics 530 (06B9)
Processor Line: (Y-Series, U-Series, etc.)
System BIOS Version: Dell Inc. 1.4.5, 27.06.2016 (UEFI)
CMOS settings: 
Graphics Driver Version: 22.20.16.4836 (17.10.2017)
GOP/VBIOS Version: 1043.14
Operating System: Microsoft Windows 10 Enterprise 
OS Version: 10.0.16299 Build 16299
API: Direct3D11
Occurs on non-Intel GPUs? No, AMD/nVidia it is working Correctly.  
 
I attached sample project with executable file.
There is some screenshots with results on Intel
det.png
 
nVidia:
 
d3d11_GDI_nVidia.png
 
Thanks!
 
 
0 Kudos
0 Replies