First, some technical details out of the way:

  • OS: Bazzite, should be latest version.
  • CPU: Ryzen 5600x
  • GPU: Intel Arc A770 16 GB
  • RAM: 32 GB DDR 4
  • MESA: 25.2.7

When attempting to launch an Unreal Engine game with Proton version above 9.0-4, or Proton Experimental, or above GE-Proton 10-1 I get this crash and error:

!status && "vkQueuePresentKHR"

I’ve searched for this error and only found some old threads pointing to Steam Overlay being a problem. However, disabling Steam Overlay does not stop this issue.

Some of the UE games I play function on lower versions of Proton, others refuse to launch at all.

What could be causing this issue? What would I do to fix it?

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    7 hours ago

    Just don’t run this version of Proton with this game.

    The reason they make all versions of Proton available at all times is because the rolling Proton version may break game configs for various reasons, in this case it looks like a Vulkan rendering queue issue where the call is blocking: https://docs.vulkan.org/refpages/latest/refpages/source/vkQueuePresentKHR.html

    You can check ProtonDB to see if anyone has a workaround for newer versions of Proton, but it’s mostly unnecessary unless there’s some specific features a specific point release you care about. Just pin the game to a working version and go.

  • nyankas@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 hours ago

    If you’re comfortable with helping the Proton developers fix the issue, I‘d recommend searching Proton‘s Github issues for the game that won‘t run.

    If your problem hasn‘t already been reported, create a proton log (run the game with the launch option PROTON_LOG=1 %command% once and find the log in your home directory). If an issue for the game doesn‘t exist already, you can open up a new one. Otherwise, append your log to the existing issue in a comment and describe what‘s happening exactly.

    The devs over there are usually really helpful and nice. Many of my reports have been fixed within hours or days in bleeding-edge, although it can of course take longer if the issue is more complicated.