I tried with my RTX 4080 using the 550.54.14 drivers on Experimental and Experimental Bleeding Edge, but it also starts fine.

I tried with my RTX 4080 using the 550.54.14 drivers on Experimental and Experimental Bleeding Edge, but it also starts fine.

I also just tried with the new 550.54.14 drivers and it still crashes just the same for me. I did look around on Proton issue tracker and even posted there once but it seems like I'm the only one with this issue. Tried wiping my root partition and reinstalling Arch recently but no dice.

Launching in DX12 also results in same swapchain creation failed messages printed but no crash, but that ones takes much longer before it's printed. I think it's because the game spends a while after opening just compiling shaders. Running in DX11 results in a crash almost immediately, so that's why I reported here since it's much faster to reproduce the crash on my machine. Here's a link to my comment of Proton issuetracker: Proton#7317.

To add some extra details I have a laptop with an Intel Integrated GPU and NVIDIA 1660Ti with an external monitor connected. I run Hyprland with the variable WLR_DRM_DEVICES=/dev/dri/card0:/dev/dri/card1 where card0 is my NVIDIA card. Laptop display is a lil broken so I only use external monitor and hence the variable so that it renders on my NVIDIA card. It gets me better performance and laptop display always stays off either way.

Hopefully this helps a little at least. I'm always willing to provide logs or compile things from source and test if required. Thanks and have a good day!

I tried with my RTX 4080 using the 550.54.14 drivers on Experimental and Experimental Bleeding Edge, but it also starts fine.

I also just tried with the new 550.54.14 drivers and it still crashes just the same for me. I did look around on Proton issue tracker and even posted there once but it seems like I'm the only one with this issue. Tried wiping my root partition and reinstalling Arch recently but no dice.

Launching in DX12 also results in same swapchain creation failed messages printed but no crash, but that ones takes much longer before it's printed. I think it's because the game spends a while after opening just compiling shaders. Running in DX11 results in a crash almost immediately, so that's why I reported here since it's much faster to reproduce the crash on my machine. Here's a link to my comment of Proton issuetracker: Proton#7317.

To add some extra details I have a laptop with an Intel Integrated GPU and NVIDIA 1660Ti with an external monitor connected. I run Hyprland with the variable WLR_DRM_DEVICES=/dev/dri/card0:/dev/dri/card1 where card0 is my NVIDIA card. Laptop display is a lil broken so I only use external monitor and hence the variable so that it renders on my NVIDIA card. It gets me better performance and laptop display always stays off either way.

Hopefully this helps a little at least. I'm always willing to provide logs or compile things from source and test if required. Thanks and have a good day!

have you tested proton 9(beta) to see if that makes any difference?

have you tested proton 9(beta) to see if that makes any difference?

Yup I did, just today. Doesn't really make a difference, same crash as always.

Could you check if "Force Full Composition Pipeline" is turned on in the Nvidia settings app and if yes then try turning it off.

Another thing to try is running with VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.json

Also it might be interesting to see if it runs with older dxvk versions like 1.10.3 or 2.0

Could you check if "Force Full Composition Pipeline" is turned on in the Nvidia settings app and if yes then try turning it off.

I don't see this option in the NVIDIA settings app, probably because I'm using Wayland right now.

Another thing to try is running with VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.json

This works! So I'm assuming somehow my laptop tries to use a different driver to render and it fails at swapchain creation? Will I always need the variable if I'm playing this game? Also I wonder why it wouldn't select the NVIDIA driver by default for Vulkan, while all other games seem to work just fine without this variable? Anyways, thanks a lot, it's good to be able to play the game again!

I can't really personally give a reason why it only works with the variable and why other games don't have issues.
Multiple GPUs can sometimes just be a bit of a mess on Linux i feel and there are many variables that influence it from various software, drivers, which GPU drives the display etc etc.

I can't really personally give a reason why it only works with the variable and why other games don't have issues. Multiple GPUs can sometimes just be a bit of a mess on Linux i feel and there are many variables that influence it from various software, drivers, which GPU drives the display etc etc.

Ah I see. Thanks a lot for figuring it out for me, closing the issue now.

Just wanted to comment that this solution also worked for me to get Age of Empires II DE (AoE) working with proton on a multi-GPU linux setup - might be useful for anyone searching CreateSwapChain() Failed