[Bug 48165] vk_error_incompatible_driver - The Surge 2

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48165

Olivier F. R. Dierick <o.dierick at piezo-forte.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |---

--- Comment #14 from Olivier F. R. Dierick <o.dierick at 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-vRAM

MESA RADV driver includes a patch to workaround the vRAM issue since September
24:
https://github.com/mesa3d/mesa/commit/780182f0a0caa9b6f48f87b1930b3bcba1ac9319#diff-e26c4d39e73dea3b18f723b444d35c04
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.