17
Error when launching Unreal Engine games with the latest Proton version(s) "!status && "vkQueuePresentKHR"" (lemmy.world)
submitted 1 year ago by to c/linux_gaming@lemmy.world
3 comments fedilink hide all child comments
 

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?

EDIT:

Apparently it's an Intel card issue with a new feature in Mesa and Proton. It's so obscure and specific to Intel cards that I couldn't find anything on it.

So apparently there is some sort of anti-lag feature in the current latest version of Mesa that the newest versions of Proton can use which needs to be disabled for Intel cards with this launch command:

DISABLE_LAYER_MESA_ANTI_LAG=1 %command%

I added this to Arc Raiders, a UE 5 game that didn't launch with the latest Proton versions, and it solved the issue. There has already been a case opened on the Bazzite Github: https://github.com/ublue-os/bazzite/issues/3252

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 year ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 1 year ago

    Apparently it's an Intel card issue with a new feature in Mesa and Proton. It's so obscure and specific to Intel cards that I couldn't find anything on it.

    So apparently there is some sort of anti-lag feature in the current latest version of Mesa that the newest versions of Proton can use which needs to be disabled for Intel cards with this launch command:

    DISABLE_LAYER_MESA_ANTI_LAG=1 %command%

    I added this to Arc Raiders, a UE 5 game that didn't launch with the latest Proton versions, and it solved the issue. There has already been a case opened on the Bazzite Github: https://github.com/ublue-os/bazzite/issues/3252

  • permalink
  • fedilink
  • source
  • parent