[Bug 44123] New: Elder Scrolls Online: Game fails to launch citing incompatible DirectX version
https://bugs.winehq.org/show_bug.cgi?id=44123 Bug ID: 44123 Summary: Elder Scrolls Online: Game fails to launch citing incompatible DirectX version Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: andrew.mrolko(a)gmail.com Distribution: --- Created attachment 59855 --> https://bugs.winehq.org/attachment.cgi?id=59855 log In a brand new wine prefix, I receive a popup dialogue box immediately after clicking "Play" from the game's launcher stating that the DirectX version I have installed is not compatible with the game. (Please see attached screenshot) I have tried the following: -Install d3dx11_43 via winetricks -Put override in place via winecfg (issue persists at this point) -Run DirectX installation from the executable which is bundled with the title (issue persists at this point) I have included two screenshots with this ticket, showing the error and the associated libraries/overrides that are in place to try and mitigate it. I also have a screenshot of '$ screenfetch' to show my GPU model and kernel/distro. NOTE: The game does run flawlessly on this machine in Windows 7. I also have a log file which indicates that the directx version I have installed could be the culprit of this issue. (Although a dev will have to confirm that for me) Thanks -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #1 from Andrew <andrew.mrolko(a)gmail.com> --- Created attachment 59856 --> https://bugs.winehq.org/attachment.cgi?id=59856 screenfetch system configuration screenshot -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #2 from Andrew <andrew.mrolko(a)gmail.com> --- Created attachment 59857 --> https://bugs.winehq.org/attachment.cgi?id=59857 Installed WINE libraries and overrides -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #3 from Andrew <andrew.mrolko(a)gmail.com> --- Created attachment 59858 --> https://bugs.winehq.org/attachment.cgi?id=59858 Error that appears on a black screen -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Andrew <andrew.mrolko(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.mrolko(a)gmail.com, | |Mlendea.Horatiu(a)GMail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia(a)gmail.com --- Comment #4 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Andrew from comment #0)
Created attachment 59855 [details] log
fixme:winediag:dxgi_check_feature_level_support None of the requested D3D feature levels is supported on this GPU with the current shader backend.
You need to set "MaxVersionGL" registry key. See https://wiki.winehq.org/Useful_Registry_Keys. It's also recommend to not install a lot of native DLLs unnecessarily. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3dx11 |directx-d3d -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC| |dark.shadow4(a)web.de --- Comment #5 from Fabian Maurer <dark.shadow4(a)web.de> ---
You need to set "MaxVersionGL" registry key. Alternatively, use wine-staging.
Most likely not a wine problem. If the issue should persist, please reopen. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #6 from Andrew <andrew.mrolko(a)gmail.com> --- (In reply to Józef Kucia from comment #4)
(In reply to Andrew from comment #0)
Created attachment 59855 [details] log
fixme:winediag:dxgi_check_feature_level_support None of the requested D3D feature levels is supported on this GPU with the current shader backend.
You need to set "MaxVersionGL" registry key. See https://wiki.winehq.org/Useful_Registry_Keys. It's also recommend to not install a lot of native DLLs unnecessarily.
With the registry version added, specifically: MaxVersionGL, 40005 in decimal and 30002 in hex, the issue persists. Furthermore, users are reporting in the comment section here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34927 that this does not necessarily fix the issue. The dlls that I have installed in the screenshot are the pre-populated components with the creation of a brand new, clean wine prefix. There has been absolutely nothing modified on this prefix up until this point. Many users are reporting the exact issue I have outlined in this ticket upon the release of the Thieves Guild patch, which removed support for OpenGL and DirectX versions below 11. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #7 from Andrew <andrew.mrolko(a)gmail.com> --- Created attachment 59869 --> https://bugs.winehq.org/attachment.cgi?id=59869 System configuration report generated by the ESO launcher I have attached a text file which is a system report generated by the game launcher. The game recognizes that my machine is running Windows XP with a DirectX version of 9.0. This holds true even though I Windows 10 as my OS version associated with the game, and launcher's executables in winecfg. Perhaps there is an issue with the game not recognizing the installed DirectX components of WINE? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Andrew <andrew.mrolko(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #8 from Andrew <andrew.mrolko(a)gmail.com> --- I have re-opened the ticket, as this issue still remains. The registry key workaround does not fix the issue anymore. Please see the link to the thread that I put in the comment section of this ticket. Many users are experiencing this issue. The game no long supports OpenGl or DirectX versions below 11 anymore. When that update was pushed out, many users have been experiencing this very problem with running the game under WINE. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #9 from Andrew <andrew.mrolko(a)gmail.com> --- My apologies for restating the issue in a stuttery and not-so eloquent fashion over the past 3 comments. The bug tracker I use at work behaves slightly differently than this one, and I was not anticipating that all changes to this ticket would appear in the comment section. I did not mean to restate the same thing in 3 different posts. Please disregard redundancies among the statements that I have made. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #10 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Andrew from comment #6)
With the registry version added, specifically: MaxVersionGL, 40005 in decimal and 30002 in hex, the issue persists. Furthermore, users are reporting in the comment section here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34927 that this does not necessarily fix the issue.
Please attach a +dxgi,+d3d11 log. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #11 from Andrew <andrew.mrolko(a)gmail.com> --- (In reply to Józef Kucia from comment #10)
(In reply to Andrew from comment #6)
With the registry version added, specifically: MaxVersionGL, 40005 in decimal and 30002 in hex, the issue persists. Furthermore, users are reporting in the comment section here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34927 that this does not necessarily fix the issue.
Please attach a +dxgi,+d3d11 log.
Would running the command: $ WINEDEBUG=+dxgi,+d3d11 wine Steam.exe &>log.txt And then launching the game from Steam achieve what you're looking for? Or would it be wise to bypass Steam and the Launcher all together, by executing: $ WINEDEBUG=+dxgi,+d3d11 wine eso64.exe &>log.txt I ask, because I'm not sure if the issue appears when WINE is originally invoked (starting Steam) and the GPU type is not being detected correctly. Or if the issue appears when the launcher calls upon the application's executable. Thanks -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #12 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Andrew from comment #11)
(In reply to Józef Kucia from comment #10)
(In reply to Andrew from comment #6)
With the registry version added, specifically: MaxVersionGL, 40005 in decimal and 30002 in hex, the issue persists. Furthermore, users are reporting in the comment section here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34927 that this does not necessarily fix the issue.
Please attach a +dxgi,+d3d11 log.
Would running the command: $ WINEDEBUG=+dxgi,+d3d11 wine Steam.exe &>log.txt
And then launching the game from Steam achieve what you're looking for?
Yes, that should work. The log will include calls generated by Steam and the game as well. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #13 from Andrew <andrew.mrolko(a)gmail.com> --- Created attachment 59877 --> https://bugs.winehq.org/attachment.cgi?id=59877 Log from running 'WINEDEBUG=+dxgi,+d3d11 wine Steam.exe &>log.txt' -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #14 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Andrew from comment #13)
Created attachment 59877 [details] Log from running 'WINEDEBUG=+dxgi,+d3d11 wine Steam.exe &>log.txt'
trace:dxgi:dxgi_check_feature_level_support Feature level D3D_FEATURE_LEVEL_11_0 not supported, trying next fallback if available. fixme:winediag:dxgi_check_feature_level_support None of the requested D3D feature levels is supported on this GPU with the current shader backend.
It looks like MaxVersionGL is not set correctly, or your GPU/OpenGL isn't sufficient to run Direct3D11. Please attach a +d3d log or glxinfo output. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Andrew <andrew.mrolko(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #59855|0 |1 is obsolete| | Attachment #59877|0 |1 is obsolete| | --- Comment #15 from Andrew <andrew.mrolko(a)gmail.com> --- Created attachment 59881 --> https://bugs.winehq.org/attachment.cgi?id=59881 Log from running 'WINEDEBUG=+dxgi,+d3d11 wine Steam.exe &>log.txt' with the MaxVersionGL key set correct;y I reran the test using the winedebug command that you had mentioned above. I also double checked my MaxVersionGL key in the registry, and noted that it was indeed set incorrectly. I had it set to 40005 (which I assume corresponds to OpenGL v4.5) but my GPU does not support that version of OpenGL. According to AMD's website, the R9 200 series GPUs support only up to OpenGL v4.3 (and up to DirectX 12, not just DirectX11) NOTE: I have an R9 280X. I went ahead and changed that key in the registry to 40003 as I believe that is correct. Although I don't know enough about the Windows registry to verify that. I just extrapolated it from reading other people's posts. That said, I still get the same error as before, although I think my wineprefix's configuration is closer to what it needs to be. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #16 from Andrew <andrew.mrolko(a)gmail.com> --- Created attachment 59882 --> https://bugs.winehq.org/attachment.cgi?id=59882 glxinfo -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #17 from Fabian Maurer <dark.shadow4(a)web.de> --- Did you already try wine-staging? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #18 from Fabian Maurer <dark.shadow4(a)web.de> --- Created attachment 59883 --> https://bugs.winehq.org/attachment.cgi?id=59883 Reg file for MaxVersionGL Sorry for the double, but I attached a registry file for setting MaxVersionGL correctly. Just to make sure you have set it right, import that and try again. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #19 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Andrew from comment #15)
Created attachment 59881 [details] Log from running 'WINEDEBUG=+dxgi,+d3d11 wine Steam.exe &>log.txt' with the MaxVersionGL key set correct;y
It doesn't seem like you set MaxVersionGL key correctly. You should see the following line in the terminal: err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version Try the reg file attached by Fabian. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #20 from Andrew <andrew.mrolko(a)gmail.com> --- (In reply to Fabian Maurer from comment #18)
Created attachment 59883 [details] Reg file for MaxVersionGL
Sorry for the double, but I attached a registry file for setting MaxVersionGL correctly. Just to make sure you have set it right, import that and try again.
I imported your file and the game immediately worked. I launched the game normally from Steam and made it all the way to gameplay. Proof: https://imgur.com/a/xFcD1 I see now that I was creating the key incorrectly. I was right clicking on the file tree on the left and using the first option "key" which appears to create folders, NOT the desired key. Foolish mistake on my part, apologies. That said, I have three follow up questions before we close this ticket: 1. Is the key that you posted here valid for all GPUs? Or is it specific to the OpenGL version that a given GPU supports? Would this (30002 in hexadecimal) be something that we could post on the Wineappdb page and have everyone use as a work around to get things going? It would be great to have a tried and true method for getting this game running on everyone's machine (at least with AMD GPUs) to get more people on Linux from Windows. I'd be happy to make a spreadsheet of GPUs and associated registry keys if necessary. 2. 0x30002 translates to 196610 in decimal. How did that actually end up fixing my issue? 196610 doesn't appear to translate to a specific version of OpenGL, unless of course I am mistaken. 3. Would it be possible to script the addition of this registry key as part of the default settings on a new wine prefix? Or is that ill advised since (to my knowledge) this only fixes one application, and could introduce a host of other issues? Thanks for your help Fabian and Józef. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #21 from Fabian Maurer <dark.shadow4(a)web.de> --- 1.) It works for every GPU that support OpenGL 3.2, that is, most modern GPUs, and everyone that can support DX11. As said, wine-staging has a workaround so you don't even need that key. 2.) View it as high-word low-word, then 0x30002 is HIGH(0x0003) and LOW(0x0002) 3.) Problem is, some drivers don't have backwards compatibility with OpenGL 3.2 profiles, while wine still uses a bit of that functionality. It will be changed once wine doesn't need that anymore, I think. In the meantime, use wine-staging or the key. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 --- Comment #22 from Józef Kucia <joseph.kucia(a)gmail.com> --- Glad that the game finally worked for you. The registry key is required because wined3d doesn't fully support OpenGL core contexts yet (see bug 38648). FWIW, we are considering adding a hack for Wine 3.0 to make the registry key unnecessary. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |DUPLICATE --- Comment #23 from Józef Kucia <joseph.kucia(a)gmail.com> --- *** This bug has been marked as a duplicate of bug 38648 *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #24 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Duplicate -- 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.
https://bugs.winehq.org/show_bug.cgi?id=44123 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- 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.
participants (1)
-
wine-bugs＠winehq.org