protonscr

[Monster Hunter Wilds] Crash on Intel Arc B580 (Linux + xe driver) - semaphore error in vkd3d-proton

vkd3dopen
HansKristian-Work/vkd3d-proton#2439 · opened 2025-04-10 by wakabaken · updated 2025-11-25 · 6 comments · github
Wwakabaken 2025-04-10 github

Environment

  • Game: Monster Hunter Wilds (tested on preview/full release)
  • OS: Ubuntu 24.10 (oracular)
  • GPU: Intel Arc B580 (Battlemage G21)
  • Kernel GPU driver: xe
  • Driver: Mesa 24.2.8 (default on Ubuntu 24.10)
  • Vulkan driver: Intel open-source Mesa driver (vulkaninfo confirmed)
  • Vulkan extensions: VK_KHR_synchronization2 is listed as supported
  • Proton versions tested: Proton Experimental, GE-Proton 9-27
  • Launch options tested:
    • VKD3D_CONFIG=dxr-fallback
    • MESA_LOADER_DRIVER_OVERRIDE=iris
    • PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1
    • vblank_mode=0

Issue Description

The game crashes during the shader compilation stage, before reaching the main menu. The following messages repeat in vkd3d.log:

warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Failed to increment swapchain semaphore. Did application forget to acquire? warn:vkd3d-proton:vkd3d_native_sync_handle_release: Failed to release semaphore (#12a).

This appears to be a synchronization or swapchain handling issue between vkd3d-proton and Intel’s Vulkan driver (Mesa with the xe kernel driver).

The exact same hardware runs Monster Hunter Wilds correctly on Windows using Intel’s official driver, so this appears to be a Linux-specific issue related to Proton or Mesa.

The same hardware and OS setup also runs Monster Hunter Rise (another DirectX 12 game using vkd3d-proton) without crashing. Rise shows no semaphore errors in the logs and functions normally (aside from a separate performance issue where the game is limited to 30fps).

This strongly suggests that the crash in Wilds is likely caused by a game-specific interaction with vkd3d-proton and/or Mesa, rather than a general DX12 failure on Intel Arc.

Notes

  • Monster Hunter Rise was tested using the same options. Although it is limited to 30fps (possibly due to driver-level VSync or clock control), it does not crash.
  • VK_KHR_synchronization2 is reported as supported via vulkaninfo, but it may not be functioning reliably on this driver stack.

Suggested Action

Please investigate potential incompatibility between vkd3d-proton and Intel Arc (with the xe driver and Mesa), especially around semaphore and swapchain synchronization.

If there's any additional information, testing, or logs I can provide to help narrow this down, I'm happy to assist.

Ddoitsujin maintainer 2025-04-10 github

Please don't file AI-generated bug reports, this entire write-up is pure garbage with no actual information whatsoever.

Not sure what your issue is, but the semaphore error is benign and happens due to something that the game deliberately chooses to do.

BBlisto91 2025-04-10 github

I'll also note that, while I haven't tested this game, a lot of issues have been fixed in in ANV (mesa) since the version noted here. So it is probably worth trying a newer version if able.

Nnyannoying1337 2025-04-17 github

@doitsujin well for what its worth i cannot get into the game getting the following error

Image

im on Mesa 25.1.0-devel (git-69a6db4b2b) (LLVM 19.1.7)

Wwakabaken 2025-04-18 github

@Lolihunter1337 I’m seeing the same error on Arc B580 (with Mesa 24.2.8).
Looks like it’s not just a one-off then — maybe something Arc-related?
Thanks for posting this!

Nnick16384 2025-05-07 github

Same error here on Arc A770 and mesa 25.1.0-rc3 trying to run Halo Infinite.

SShinusagi 2025-11-25 github

Same issue on ARC B580 on a Intel I5 12400 with 24 GB DDR5
I checked and it seems to be an issue with the Mesa drivers for this:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/13011

Sadly on Windows I had some really bad crashes and BSOD with the latest Drivers, since Monster Hunter Wilds does not officially support Intel Cards, so I just moved into playing it on Linux and I can't right now...
On another machine with both AMD CPU and GPU I have no issues on Linux running the game, so we can only wait and hope for a fix soonish.

Proton versions

Launch options