[Bug 48165] New: vk_error_incompatible_driver - The Surge 2
https://bugs.winehq.org/show_bug.cgi?id=48165 Bug ID: 48165 Summary: vk_error_incompatible_driver - The Surge 2 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahmed.com(a)protonmail.com Distribution: --- Created attachment 65795 --> https://bugs.winehq.org/attachment.cgi?id=65795 vk_error_incompatible_driver I get the error message "vk_error_incompatible_driver" when trying to run "The Surge 2" with Wine-staging 4.20, but I don't get this error message when using Proton 4.11-8 which is an older version of Wine. There is many versions of Wine between these two. I don't know if there is a patch that Proton uses to fix this issue that has not merged yest, or if there is a regression happened between Wine 4.11, and Wine 4.20. The game has other issues with RADV, and AMDVLK, and I have to hard shutdown my machine when that happens, so I am not willing to do more testing, because of that. -- 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=48165 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be Version|unspecified |4.20 --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Unfortunately, unless someone else is experiencing the issue, you'll have to test the application at least one more time to provide terminal output. I suggest you attach to this bug a debug trace with WINEDEBUG=+loaddll,+vulkan. You can find instructions to get a debug trace at point 10.1.2 there: https://wiki.winehq.org/FAQ#get_log Also please indicate: - Your linux distribution; - Where your copy of wine-staging 4.20 comes from: build from source yourself, package from OS distribution or other repository? - The model of your AMD/ATI card and version of the driver. - Version of the vulkan support library package of your OS (the name vary from distributions; it's libvulkan1 on Debian) - Do you use vkd3d or dxvk (which version)? Regards. -- 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=48165 Ahmed Elsayed <ahmed.com(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu -- 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=48165 --- Comment #2 from Ahmed Elsayed <ahmed.com(a)protonmail.com> --- Created attachment 65801 --> https://bugs.winehq.org/attachment.cgi?id=65801 The terminal log file -- 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=48165 --- Comment #3 from Ahmed Elsayed <ahmed.com(a)protonmail.com> --- Thanks for your reply, and I am sorry for the lack of useful information. System info: Linux distribution: Linux Mint Cinnamon 19.2 / Kernel: 5.0.0-36 GPU: AMD HD 8750M Driver: MESA 20 LLVM 9 (OBIAF PPA) DXVK Version: 1.4.5 I use only Wine-staging from your official repository for Ubuntu 18.04 located in your website, and I don't use VKD3D, I use only DXVK (v. 1.4.5) I have libvulkan1 version 1.1.126.0~rc1-1ubuntu18.04.1.1 that I got from Vulkan-SDK official repository for Ubuntu 18.04 located in that link: https://vulkan.lunarg.com/doc/sdk/1.1.126.0/linux/getting_started_ubuntu.htm... -- 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=48165 --- Comment #4 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, There is a possible workaround that consists of installing Windows version of Vulkan SDK and Vulkan Run-Time in the wineprefix. Can you make a backup clone of your wineprefix and try this command? (Assuming the wineprefix is ~/.wine. If not, change that part to the actual path of your wineprefix.) WINEPREFIX=~/.wine winetricks vulkansdk vulkanrt Then test the application again. If anything goes wrong you can restore the wineprefix from the backup. Note that DXVK is not supported here but has its own bug tracker: https://github.com/doitsujin/dxvk/issues The workaround is expected to make the application run with wine-staging+DXVK. If it doesn't work, it's probably a DXVK issue and you should report the issue to them. Regards. -- 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=48165 --- Comment #5 from Ahmed Elsayed <ahmed.com(a)protonmail.com> --- The game now crashes instead of hanging. I don't know if he can help with this issue, but I will report it anyway. -- 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=48165 Philip Rebohle <philip.rebohle(a)tu-dortmund.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |philip.rebohle(a)tu-dortmund. | |de --- Comment #6 from Philip Rebohle <philip.rebohle(a)tu-dortmund.de> --- (In reply to Olivier F. R. Dierick from comment #4)
Hello,
There is a possible workaround that consists of installing Windows version of Vulkan SDK and Vulkan Run-Time in the wineprefix.
Note that the Windows Vulkan loader uses DXGI to enumerate adapters, which currently doesn't work on wine due to (I think) LUID shenanigans. It *definitely* won't work for anyone using DXVK, ever, because DXVK uses Vulkan to enumerate DXGI devices. -- 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=48165 --- Comment #7 from Ahmed Elsayed <ahmed.com(a)protonmail.com> --- Setting vulkan-1.dll, and DXGI.dll to bultin make the game to go a little further, but the game hangs with RADV, and with AMDVLK I can go to the main menu, but after starting a new game, the game hangs after the cutscenes. -- 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=48165 --- Comment #8 from Philip Rebohle <philip.rebohle(a)tu-dortmund.de> --- Try RADV_DEBUG=zerovram. If that fixes it, you're running into a well-known game bug. -- 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=48165 --- Comment #9 from Ahmed Elsayed <ahmed.com(a)protonmail.com> --- (In reply to Philip Rebohle from comment #8)
Try RADV_DEBUG=zerovram. If that fixes it, you're running into a well-known game bug.
The game now crashes instead of hanging, but thank you for your suggestion. That is not the first Vulkan game that I couldn't run on my PC. It will be cool to have OpenGL as an option to these game like Doom 2016. -- 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=48165 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #10 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Ahmed Elsayed from comment #9)
(In reply to Philip Rebohle from comment #8)
Try RADV_DEBUG=zerovram. If that fixes it, you're running into a well-known game bug.
The game now crashes instead of hanging, but thank you for your suggestion. That is not the first Vulkan game that I couldn't run on my PC. It will be cool to have OpenGL as an option to these game like Doom 2016.
Hello, Maybe you want to give vkd3d a try? https://wiki.winehq.org/Vkd3d You can file new bugs about vkd3d issues here. (Marking this bug invalid for the reason: DXVK.) Regards. -- 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=48165 --- Comment #11 from Ahmed Elsayed <ahmed.com(a)protonmail.com> --- How is this bug related to DXVK?!! It is a vulkan game that doesn't work on WINE. Anyway, I will stop reporting games here if it doesn't work on 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=48165 --- Comment #12 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Ahmed Elsayed from comment #11)
How is this bug related to DXVK?!! It is a vulkan game that doesn't work on WINE. Anyway, I will stop reporting games here if it doesn't work on WINE.
Hello, (In reply to Ahmed Elsayed from comment #3)
DXVK Version: 1.4.5
I use only Wine-staging from your official repository for Ubuntu 18.04 located in your website, and I don't use VKD3D, I use only DXVK (v. 1.4.5)
I think you said that you were using DXVK. When DXVK is installed in a wineprefix it overrides some DLLs. If it was the case, then the application was using DXVK's vulkan implementation and you'll have to restart from scratch in a clean wineprefix to test the application without DXVK. Regards. -- 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=48165 --- Comment #13 from Ahmed Elsayed <ahmed.com(a)protonmail.com> --- I already did that, but the game freezes after the first cutscene, and I have to set vulkan-1 to builtin to overcome the error message: "vk_error_incompatible_driver" The game freezes whatever I use RADV or AMDVLK, but when using RADV, it freezes before reaching the main menu. I don't know if this issue is related to WINE, RADV, or AMDVLK, and I already reported a bug to everything related, but I only got response here. -- 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=48165 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #14 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, 1. I tested the application myself. The computer were I tested the application has a nvidia card, proprietary driver 430.50 on 64-bit Debian 8 Jessie. This was plain wine version 4.21 in a fresh 64-bit wineprefix. corefonts was installed with winetricks to accommodate Steam internal browser issue. 1. I could reproduce the "vk_error_incompatible_driver" issue. Currently, Wine is set to prefer 'native' over 'builtin' vulkan-1, and since the application ships its own vulkan-1.dll, it tries to use that by default. I haven't debugged the issue that makes the native vulkan-1.dll freaks out (I don't have the skills for that). Setting 'vulkan-1' to 'builtin' in winecfg works around the issue. I've reopened the bug for that issue as it happens without DXVK or vkd3d. The next point is only a workaround and issues with it should not be discussed here. It's provided here for the record only and help should be asked for privately or on the forums. 2. With vulkan-1 set to 'builtin', I could run the game. I could not reproduce any crash or hang. I could get to the main menu, start a new game, watch the intro video, create a character and start the first level where the player must escape what looks like a prison. I couldn't finish the level because I was playing badly, but overall the game ran fin with nice framerate and no visual or audio glitch, as far as I can tell. Keyboard/mouse controls were working fine too. With AMD cards, you need to use RADV_DEBUG=zerovram to workaround the application bug, as stated in comment 8. This is used in the command to launch the game like this: $ RADV_DEBUG=zerovram wine TheSurge2.exe Or you can export the variable first before launching the command: $ export RADV_DEBUG=zerovram $ wine TheSurge2.exe I've seen somewhere that AMD_DEBUG was used instead of RADV_DEBUG: https://www.phoronix.com/scan.php?page=news_item&px=RadeonSI-Rocket-League-v... MESA RADV driver includes a patch to workaround the vRAM issue since September 24: https://github.com/mesa3d/mesa/commit/780182f0a0caa9b6f48f87b1930b3bcba1ac93... I don't know which version of mesa it is, though, so maybe you still need to use RADV_DEBUG. Regards. -- 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=48165 --- Comment #15 from Ahmed Elsayed <ahmed.com(a)protonmail.com> --- Thanks for your efforts. RADV_DEBUG=zerovram don't work with me, but I don't need it, because I use Mesa 19.3 RC6 that is far beyond the commit that fixed this issue. I reported this issue to mesa gitlab, but they closed it as a duplicate of an old issue that is fixed 2 months ago. The game doesn't work either with AMDVLK, but it is a different issue. It is not a WINE bug anyway, so I will not add any more replies here. -- 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=48165 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #16 from Matteo Bruni <matteo.mystral(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #10)
Hello,
Maybe you want to give vkd3d a try? https://wiki.winehq.org/Vkd3d
You can file new bugs about vkd3d issues here.
(Marking this bug invalid for the reason: DXVK.)
vkd3d and DXVK are not mutually exclusive: vkd3d is used in Wine to provide a d3d12 implementation, DXVK is an alternative d3d11 implementation. (In reply to Ahmed Elsayed from comment #15)
Thanks for your efforts.
RADV_DEBUG=zerovram don't work with me, but I don't need it, because I use Mesa 19.3 RC6 that is far beyond the commit that fixed this issue.
I reported this issue to mesa gitlab, but they closed it as a duplicate of an old issue that is fixed 2 months ago.
Thank you for the update, closing the bug since it's been fixed upstream. -- 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=48165 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #17 from Matteo Bruni <matteo.mystral(a)gmail.com> --- Closing fixed upstream bug. -- 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)
-
WineHQ Bugzilla