Closed nta closed 7 years ago
This is probably a simple fix but I need to find a simpler example program I can test with, I'll see what I can do.
I forgot to update this bug - I think this is fixed now, at least with the simple test program I found.
Let me know if it works for you. I'm just kicking a new nightly build now so there should be one available shortly.
Yeah - this particular issue seems to be resolved now. I've not taken an in-depth look yet, but the DComp-based devices in Chrome appear to be detected now.
When trying to capture a process that uses D3D11 with a swap chain using DirectComposition (
IDXGIFactory2::CreateSwapChainForComposition
), the UI will stay on 'No API detected', and the log will show the following:This seems to be because of d3d11_device.cpp using the
OutputWindow
in the swap chain description as key for this internal structure, where this type of swap chain has no output window.I encountered this while trying to debug CEF, which seems to use this particular device creation mode ANGLE offers for the backing D3D device.