http://bugs.winehq.org/show_bug.cgi?id=55432 Wehrwolfmann <wehrwolfmann@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wehrwolfmann@gmail.com --- Comment #6 from Wehrwolfmann <wehrwolfmann@gmail.com> --- Still present in wine-11.15 (vanilla, 64-bit, clean prefix). Since the reports in this bug so far were taken with DXVK, here is a measurement made without DXVK, without Steam and without any application -- a ~90 line program that only loads dcomp.dll and calls the three device creation entry points (attached as dcomp_min.c, build with x86_64-w64-mingw32-gcc dcomp_min.c -o dcomp_min.exe -ld3d11 -ldxgi -lole32): reported Windows version: 10.0 build 19045 D3D11CreateDevice hr=0x00000000 feature_level=0xb000 QI IDXGIDevice hr=0x00000000 DCompositionCreateDevice(IDCompositionDevice) hr=0x80004001 DCompositionCreateDevice2(IDCompositionDevice2) hr=0x80004001 DCompositionCreateDevice3(IDCompositionDesktopDevice) hr=0x80004001 fixme:dcomp:DCompositionCreateDevice ..., {c37ea93a-e7aa-450d-b16f-9746cb0407f3}, ... fixme:dcomp:DCompositionCreateDevice2 ..., {75f6468d-1b8e-447c-9bc6-75fea80b5b25}, ... fixme:dcomp:DCompositionCreateDevice3 ..., {5f4633fe-1e08-4cb8-8c75-ce24333f5602}, ... The D3D11 device and its IDXGIDevice are created fine; only the DirectComposition device creation fails, which matches dlls/dcomp/device.c in current master, where all three entry points are FIXME + E_NOTIMPL. This is not limited to game launchers. Anything built on Chromium's compositor takes the same path once the prefix reports Windows 8.1 or newer, which currently includes every application embedding the WebView2 runtime -- see bug 58921, where forcing the Windows version down to win7/win8 for the Chromium process alone is the workaround. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.