VK_EXT_swapchain_maintenance1 being forced on for DXVK/VKD3D applications appears to cause games not to launch on the Deck under SteamOS main channel and Proton 8/9 and the current driver

[JDGBOLT]

On the Steam Deck, at least for the Oled, it appears that this commit that was added a while ago 927c565 causes games running using dxvk or vkd3d-proton to fail to initialize the 3d acceleration, various games will show different error messages, but I know it's specifically that commit because I bisected gamescope for these issues and did determine the issue. Patching gamescope to disable that particular commit caused the games to be able to start up normally, so it appears there is still something with dxvk/vkd3d-proton and the current Steam Deck graphics driver to fail to start games in the development versions of SteamOS. May be a similar story with regards to this comment as well: #1182 (comment) .

[sharkautarch]

On the Steam Deck, at least for the Oled, it appears that this commit that was added a while ago 927c565 causes games running using dxvk or vkd3d-proton to fail to initialize the 3d acceleration, various games will show different error messages, but I know it's specifically that commit because I bisected gamescope for these issues and did determine the issue. Patching gamescope to disable that particular commit caused the games to be able to start up normally, so it appears there is still something with dxvk/vkd3d-proton and the current Steam Deck graphics driver to fail to start games in the development versions of SteamOS. May be a similar story with regards to this comment as well: #1182 (comment) .

hmmm, maybe grabbing a dump of the vulkan api calls might help:
First you’ll need to install the vulkan-extra-layers package w/ pacman -Sy vulkan-extra-layers
It looks like the vulkan-extra-layers is included in the steamdeck’s holo extra repo
Note that I believe there are a couple steps you have to take in order to install packages on the steamdeck: https://www.reddit.com/r/SteamDeck/comments/t8al0i/install_arch_packages_on_your_steam_deck/

assuming you are able to install the vulkan-extra-layers package, then you can run this command:
gamescope -- env VK_APIDUMP_OUTPUT_RANGE='0,1' VK_LOADER_LAYERS_ENABLE='*FROG*,*api*' <game or something> |& tee /home/deck/gamescope_swap_maint.log

[Joshua-Ashton]

The reason is that we are simply just missing a newer Mesa on SteamOS Main. It's being updated soon.

[JDGBOLT]

It appears that the new mesa driver has fixed game crashing for at least some games, but others still crash on startup. It appears it's some sort of recent regression in DXVK/VKD3D-Proton perhaps, as I have Elden Ring and Alien Isolation crashing on startup with Proton-GE as well as Proton Experimental with Elden Ring, and Proton 9 Beta, Proton Experimental, and Proton-GE with Alien Isolation.

[Joshua-Ashton]

This is already all fixed and will be in the next Main image

[JDGBOLT]

If you are referring to the gamescope 3.14.7 release, I already had that installed on my deck manually, figured I would test it with the latest code before reporting. Also did a test with disabling it with the latest 3.14.7 package source and it did fix the issue, so it's not some new regression at least from what I can tell.

[sharkautarch]

If you are referring to the gamescope 3.14.7 release, I already had that installed on my deck manually, figured I would test it with the latest code before reporting. Also did a test with disabling it with the latest 3.14.7 package source and it did fix the issue, so it's not some new regression at least from what I can tell.

I believe that Joshua-Ashton is actually referring to the mesa driver version
Check what your current mesa driver version is by running the following command on the terminal:
vulkaninfo | grep -i driverVersion

When Joshua-Ashton is talking about a "newer mesa", I believe they are talking about mesa versions >= 24.1