https://bugs.winehq.org/show_bug.cgi?id=45080
--- Comment #14 from Toni eldrad@autistici.org --- (In reply to Nikolay Sivov from comment #13)
I don't think it's useful. If you're going to edit it, you should be adding new methods too so you don't have to guess later why it failed.
Well, it's the easiest thing to try first, then of course the new methods need to be added but that will require more work, and my suggestion is to just try and add -that one line- and see what happens. Also, looking at the new methods in IDXGIDevice2 they don't even look that useful for a game, so who knows. If the app fails afterwards in an undeclared IDXGIDevice2 method it will be really obvious in apitrace since it will be the last line, akin to what happened in bug 41063.
Anyways you seem like the right person to provide an stub implementation of IDXGIDevice2 if you think it's better to start there, I'm still a bit lost with advanced interface stuff, besides adding fake/partial interface declarations for debugging. It astonished me how fast you implemented those stubs for ID3D11Device1 and ID3D11DeviceContext1.