[Bug 57995] New: The Testament of Sherlock Holmes: Failed Vulkan Assert in winevulkan/loader_thunks.c (vkCreateGraphicsPipelines)

[WineHQ Bugzilla]

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

Bug ID: 57995
           Summary: The Testament of Sherlock Holmes: Failed Vulkan Assert
                    in winevulkan/loader_thunks.c
                    (vkCreateGraphicsPipelines)
           Product: Wine
           Version: 10.3
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: winevulkan
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 78256
  --> https://bugs.winehq.org/attachment.cgi?id=78256
Vanilla Wine 10.3 Log

The game works enough to get to the main menu with just DXVK, but Wine throws a
failed Vulkan assert immediately upon actually starting a new game session
after confirming at the main menu: not even a loading screen is seen before it
happens.

The log points to: winevulkan/loader_thunks.c, line 3190
(vkCreateGraphicsPipelines)

https://gitlab.winehq.org/wine/wine/-/blob/wine-10.3/dlls/winevulkan/loader_...

There's also mentions of failing to map memory elsewhere in the log, which I
don't really understand?
(Correct me if I'm misunderstanding the issue, but my hardware is far above
minimum spec for this game.)

----

Distro: Gentoo Linux (x86_64)
Desktop Environment: KDE Plasma 6.2.5 (Wayland)
CPU: Ryzen 3700X @ 4.98 GHz
RAM: 32GBs @ 3600 MHz
GPU: AMD RX 7800 XT
Mesa Version: 25.0.1

Wine Version: 10.3 (vanilla)
DXVK Version: 2.6
Gamescope Version: 3.16.2

[Bug 57995] The Testament of Sherlock Holmes: Failed Vulkan Assert in winevulkan/loader_thunks.c (vkCreateGraphicsPipelines)

[WineHQ Bugzilla]

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

Neko-san  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
       Distribution|---                         |Gentoo
                URL|                            |https://www.gog.com/en/game
                   |                            |/testament_of_sherlock_holm
                   |                            |es_the

[Bug 57995] The Testament of Sherlock Holmes: Failed Vulkan Assert in winevulkan/loader_thunks.c (vkCreateGraphicsPipelines)

[WineHQ Bugzilla]

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

Zeb Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Zeb Figura  ---
DXVK is not supported in this bug tracker; please test with unmodified Wine or
report bugs to DXVK.

[Bug 57995] The Testament of Sherlock Holmes: Failed Vulkan Assert in winevulkan/loader_thunks.c (vkCreateGraphicsPipelines)

[WineHQ Bugzilla]

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

Neko-san  changed:

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

--- Comment #2 from Neko-san  ---
In that case, I used "winetricks -q physx" (it's required to run) on a new
prefix without DXVK and it seems to run fine with the default wined3d...

I'm assuming it's a DXVK bug, in that case; I'll report it over there (I didn't
realize DXVK could trip winevulkan itself like that)

[Bug 57995] The Testament of Sherlock Holmes: Failed Vulkan Assert in winevulkan/loader_thunks.c (vkCreateGraphicsPipelines)

[WineHQ Bugzilla]

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

--- Comment #3 from Neko-san  ---
After further investigation it seems this was because the game isn't Large
Address Aware, and this becomes more apparent when using DXVK: however, this
being the case is also a problem with wined3d albiet not for the same reason -
the game just simply runs out of memory sometimes at runtime (which I had
happen during my testing while I was saving the game - which is arguably also
pretty bad even though it's not consistent)