Proton isn't functioning properly on Arch even though my GPU is working in all other tests I've run.
Proton isn't functioning properly on Arch even though my GPU is working in all other tests I've run.
I found a curious release of Arco Linux, an Arch-based build packed with pre-set tools. After testing it for a couple of days, I moved my primary Arch drive there and was quite satisfied. The next day I wanted to play MSFS 2020, opened Steam, installed the game, and hit that Wine warning pop-up: "Please make sure your hardware supports this game. D3D11_Z." I dug into the issue, learned it’s a Windows problem caused by missing DirectX redistributions, and found Proton should handle it. I spent several hours searching online, trying various fixes—removing Steam, reinstalling, changing builds—but nothing worked. I also removed the Steam folder completely and tested both runtime and native builds. My 5700XT uses an AMD GPU, and I’ve installed multiple drivers (XF86-Mesa, Vulkan-Radeon, DXVK, VDPAU, plus their X86 versions via Multilib). Wayland didn’t help either; it just crashed the game. On the other hand, running MSFS, Superposition, and VKMark with Proton worked perfectly. It seems Proton isn’t compatible with this setup, and I’m stuck without a clear way to diagnose further. Need some guidance.
Consider setting up Proton locally according to the instructions on the GitHub page or via the AUR package, and check if this improves performance.
This was intended as my next step—I actually created valve-wine yesterday just to be ready—but I thought of Proton standalone as a tool for running apps and games outside of Steam, while Steam keeps its own local copies. I assume it should fix any dependency problems. Edit – It looks like you can assemble your own and then add it to Steam. I hope it doesn’t take as long as valve-wine’s build time.
Ensure the listed packages are present on your system. Add PROTON_LOG=1 %command% to the game startup settings. After launching, share the generated log file in your home directory. When using DXVK via the AUR, run "setup_dxvk install" to complete setup. Regarding AMDGPU, it depends on whether you include a recent kernel and Mesa build; if you built Mesa from the AUR, make sure vulkan-radeon and vdpau are included, though mesa-git is not recommended. For a ready Native Arch version of Proton-TKG compatible with Steam, refer to the provided GitHub link. This ProtonGE AUR package typically replaces Steam Runtime in favor of a native solution, which performs better. Avoid downloading proton-ge-custom-bin as it targets Steam Runtime specifically. Updated August 3, 2021 by Nayr438
After reviewing the logs, I took additional steps. MSFS was missing certain DLLs from its main folder, downloaded them from downloads site and bypassed the previous issue. Now it’s crashing with the same error as C&C does—information: Game: ClientLauncherG.exe info: DXVK: v1.9 information: Built-in extension providers: info: Win32 WSI information: OpenVR information: OpenXR information: Enabled instance extensions: info: VK_KHR_get_surface_capabilities2 info: VK_KHR_surface info: VK_KHR_win32_surface warning: DXVK: No adapters found. Please verify your device filter settings and Vulkan configuration. Edit – In reality MSFS is crashing to a different error err:module:LdrInitializeThunk Importing dlls for LZ:\\home\\carl\\.local\\share\\Steam\\steamapps\\common\\MicrosoftFlightSimulator\\FlightSimulator.exe failed, status c0000135 Edit 2 Found a post in Steam support that suggests blacklisting the "radeon" module so the system forces amdgpu; however, neither amdgpu nor radeon is detected via modprobe.
I completely removed Steam and began from scratch with new downloads. Adding DLLs manually wasn't wise—it turned out Wine (and Proton too) doesn't handle it well, leading to serious issues. Even though I managed to undo all the changes, I opted to just re-download everything again. Now I'm facing the same problems, as all games crash with this error: info: Game: ClientLauncherG.exe info: DXVK: v1.9 info: Built-in extension providers: info: Win32 WSI info: OpenVR info: OpenXR info: Enabled instance extensions: info: VK_KHR_get_surface_capabilities2 info: VK_KHR_surface info: VK_KHR_win32_surface warn: DXVK: No adapters found. Please check your device filter settings and Vulkan setup. Outside of Proton, Vulkan works fine—I can run non-Proton games and benchmarks. VulkanInfo confirms the card is detected and functioning. This must be a Proton bug; its implementation of DXVK isn't recognizing my GPU at all.
It's not necessarilyy that it cant find your GPU, its that it cant find a compatible Vulkan Implentation. Your log should have mentioned which icd it was trying to load, if you can look for that and share it. Also can you share the ouput of "ls /usr/share/vulkan/icd.d/" and verify that the following packages are installed pacman -Sy lib32-mesa vulkan-radeon lib32-vulkan-radeon vulkan-mesa-layers lib32-vulkan-mesa-layers vulkan-icd-loader lib32-vulkan-icd-loader
Sure, everything is set up now. The log doesn’t reference anything about ICD. I’m thinking about adding amdgpu-pro to check its impact.
Attempting to start Steam (Native) from "steam-native-runtime" using the specified file paths. If that fails and the required files are present, the problem may lie elsewhere. Unfortunately, I can't recreate the Vulkan issue on an Arch system with a 5700XT.
Same outcome, thank you still. Are there any issues with the GDM or GNOME settings? When I ran Arco, it automatically installed SDDM and made it the default, but I turned off SDDM and switched to GDM manually.