[Bug 36828] New: Multiple DirectX11 games need D3D11CreateDevice implementation with D3D_FEATURE_LEVEL_11_x support (Sniper Elite 3)
https://bugs.winehq.org/show_bug.cgi?id=36828
Bug ID: 36828 Summary: Multiple DirectX11 games need D3D11CreateDevice implementation with D3D_FEATURE_LEVEL_11_x support (Sniper Elite 3) Product: Wine Version: 1.7.21 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: focht@gmx.net
Hello folks,
a collector bug to capture all games that require/request D3D_FEATURE_LEVEL_11_x support through 'D3D11CreateDevice'.
Bug 34008 is about D3D_FEATURE_LEVEL_10_x support
'Sniper Elite 3' requires DirectX 11, it complains with 'Failed to initialise D3D11; Error Code 0' message box.
--- snip --- ... fixme:d3d11:D3D11CreateDevice stub: adapter (nil), driver_type D3D_DRIVER_TYPE_HARDWARE, swrast (nil), flags 0, feature_levels 0x33fd10, levels 0x3, sdk_version 7, device 0xd712f4, feature_level (nil), context 0xd712f8 55 return E_OUTOFMEMORY;
Wine-dbg>bt Backtrace: =>0 0x7edfd01b D3D11CreateDevice+0xb4(adapter=(nil), driver_type=D3D_DRIVER_TYPE_HARDWARE, swrast=(nil), flags=0, feature_levels=0x33fd10, levels=0x3, sdk_version=0x7, device=0xd712f4, feature_level=(nil), context=0xd712f8) [/home/focht/projects/wine/wine.repo/src/dlls/d3d11/d3d11_main.c:55] in d3d11 (0x0033fcd4) 1 0x0040cd00 in sniperelite3 (+0xccff) (0x0033fd20) 2 0x00958919 in sniperelite3 (+0x558918) (0x0033fd2c) 3 0x009f7429 in sniperelite3 (+0x5f7428) (0x0033fd54) 4 0x00937a07 in sniperelite3 (+0x537a06) (0x0033fd70) 5 0x00631ef1 in sniperelite3 (+0x231ef0) (0x0033fd8c) 6 0x00a1d9c1 in sniperelite3 (+0x61d9c0) (0x0033fe20) 7 0x7b863ddc call_process_entry+0xb() in kernel32 (0x0033fe38) ... Wine-dbg>p *feature_levels D3D_FEATURE_LEVEL_11_0 --- snip ---
Interestingly, the call site looks like it's able to pass D3D_FEATURE_LEVEL_10_x too but currently there is no way to influence this from command line (the global variable responsible for this is only read).
Maybe there will be a command line option with a later game update, that allows to force the game into 'DirectX10' feature level.
Regards
https://bugs.winehq.org/show_bug.cgi?id=36828
John the.ideals@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |the.ideals@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=36828
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
--- Comment #1 from Adam Bolte abolte@systemsaviour.com --- Seems to affect Far Cry 4 (once a work-around for bug #33776 and #34870 is in place).
fixme:d3d11:D3D11CreateDevice stub: adapter 0x1183bae0, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0, feature_levels 0x1b4fe0b8, levels 0x3, sdk_version 7, device 0x1bf0ad08, feature_level 0x1b4fe240, context 0x182d7d030
Minimum requirements include Windows 7 64-bit, and all minimum graphics cards are DirectX 11.
https://support.ubi.com/en-GB/FAQ/9/4277/system-requirements-for-far-cry-4/k...
http://store.steampowered.com/app/298110/
https://bugs.winehq.org/show_bug.cgi?id=36828
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mitchwharper@gmail.com
--- Comment #2 from Austin English austinenglish@gmail.com --- *** Bug 38078 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36828
Qian Hong fracting@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fracting@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=36828
Luke gaming4jc2@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gaming4jc2@yahoo.com
--- Comment #3 from Luke gaming4jc2@yahoo.com --- Also seems to affect "The Talos Principle Demo" (free download for testing). --- fixme:d3d11:D3D11CreateDevice adapter (nil), driver_type D3D_DRIVER_TYPE_HARDWARE, swrast (nil), flags 0x20, feature_levels 0x33f9b4, levels 0x6, sdk_version 7, device 0x158e4c8, feature_level 0x14fb2a0, context 0x286c580 stub! ERR: Cannot set requested display mode 800x600: GfxAPI error: ERR: Direct3D error: Cannot start Direct3D 11 device and/or context! ERR: INF: (display mode already stopped) fixme:win:EnumDisplayDevicesW ((null),0,0x33f304,0x00000000), stub! fixme:d3d11:D3D11CreateDevice adapter 0x14b180, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0x20, feature_levels 0x33f9b4, levels 0x6, sdk_version 7, device 0x158e4c8, feature_level 0x14fb2a0, context 0x2878b98 stub! fixme:d3d11:D3D11CreateDevice adapter (nil), driver_type D3D_DRIVER_TYPE_HARDWARE, swrast (nil), flags 0x20, feature_levels 0x33f9b4, levels 0x6, sdk_version 7, device 0x158e4c8, feature_level 0x14fb2a0, context 0x2878b98 stub! ERR: Cannot set requested display mode 640x480: GfxAPI error: ERR: Direct3D error: Cannot start Direct3D 11 device and/or context! ---
http://store.steampowered.com/app/257510/
https://bugs.winehq.org/show_bug.cgi?id=36828
--- Comment #4 from Luke gaming4jc2@yahoo.com --- (In reply to Anastasius Focht from comment #0)
Maybe there will be a command line option with a later game update, that allows to force the game into 'DirectX10' feature level.
It didn't work on the demo I just posted, but I wonder if passing -dxlevel would work on some games. Worth a try, see here: https://developer.valvesoftware.com/wiki/Command_Line_Options
https://bugs.winehq.org/show_bug.cgi?id=36828
--- Comment #5 from Andrey Gusev andrey.goosev@gmail.com --- Please retest on 1.7.51 or higher.
https://bugs.winehq.org/show_bug.cgi?id=36828
Alessandro Pezzoni alessandro.pezzoni@runbox.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alessandro.pezzoni@runbox.c | |om
https://bugs.winehq.org/show_bug.cgi?id=36828
--- Comment #6 from Adam Bolte abolte@systemsaviour.com --- Created attachment 53748 --> https://bugs.winehq.org/attachment.cgi?id=53748 1.9.4+-uplay-far_cry-4.log
Far Cry 4 via Wine 1.9.4+ (master HEAD at 1510b8b9).
The wineprefix was configured to default to Windows XP 64-bit, but the FarCry4.exe executable was set to Windows 7. This was necessary to work around a Uplay launch bug when Windows Vista or higher is selected in a 64-bit wineprefix.
No dll overrides were configured. The game was not cracked, etc.
Is this still considered the same bug?
https://bugs.winehq.org/show_bug.cgi?id=36828
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair@hotmail.com
--- Comment #7 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Fixed by? http://source.winehq.org/git/wine.git/?a=commit;h=ce32dccee79088fdb64c5b01a9...
https://bugs.winehq.org/show_bug.cgi?id=36828
Józef Kucia joseph.kucia@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Fixed by SHA1| |ce32dccee79088fdb64c5b01a96 | |906e033529d21 Resolution|--- |FIXED CC| |joseph.kucia@gmail.com
--- Comment #8 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Alistair Leslie-Hughes from comment #7)
Fixed by? http://source.winehq.org/git/wine.git/?a=commit; h=ce32dccee79088fdb64c5b01a96906e033529d21
Let's mark it as fixed.
https://bugs.winehq.org/show_bug.cgi?id=36828
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.9.16.
-
wine-bugs＠winehq.org