Hello @Snikker24, this reads more like a system config issue with missing Vulkan drivers than a Proton issue. Please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
Also, please double check that you have the mesa-vulkan-intel and mesa-vulkan-intel-32bit system packages installed.
So, by launching Steam using the following:
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/intel_hasvk_icd.i686.json:/usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json:/usr/share/vulkan/icd.d/intel_icd.i686.json:/usr/share/vulkan/icd.d/intel_icd.x86_64.json steam
I was able to get rid of all but two errors, those being the initial ones from Wine reporting the driver loading failure:
326.405:0020:00cc:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
326.405:0020:00cc:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
Still the games refuse to launch even on a fresh OS install. I will try debugging Proton's Wine binaries to see if I get anything from that. One thing I need to mention is that system's version of Wine works without any flaws.
Maybe it's having a hard time picking between the iGPU and dGPU. I'd test setting a game's launch options to DRI_PRIME=1 %command% or DRI_PRIME=0 %command% to try to prioritize between the different Intel GPUs.
"This seems to work, it creates the game window but it's just a black screen that eventually times out, and the force quit menu appears."
Doesn't work after reboot.
FIXED: Proton failed because both the dGPU and the iGPU share the same i915 driver. The fix was disabling integrated graphics in the BIOS . Still manual configuration is needed for every game. Older games require using the PROTON_USE_WINED3D=1 command else the window launches and then freezes after a few seconds while others work out of the box. Other games straight out crash on the main menu (DOOM 2016 with 162 errors in the Proton log).
proton 5.13-6x1 2025-03proton 6.3-8x1 2025-03proton 7.0-6x1 2025-03proton 8.0-5x1 2025-03proton 9.0-4x1 2025-03proton experimentalx1 2025-03proton hotfixx1 2025-03PROTON_USE_WINED3D=1x1 2025-03DRI_PRIME=0 %command%x1 2025-03DRI_PRIME=1 %command%x1 2025-03winevulkan.dllx1 2025-03
Description
Upon trying to launch any game without native support, Proton fails to start it.
Versions tested
Proton Hotfix, Proton Experimental, Proton 9.0-4, Proton 8.0-5, Proton 7.0-6, Proton 6.3-8, Proton 5.13-6
Games Tested
Assassin's Creed
Assassin's Creed 2
Assassin's Creed Revelation
Doom (2016)
Dishonored
Dishonored 2
Grand Theft Auto IV: The Complete Edition
Grid 2
Wreckfest
Possible cause
Proton's Wine component may fail loading drivers correctly
In a proton log generated for Assassin's Creed 2 (game chosen as testing environment) the following errors may appear (Vulkan errors not always present):
0.000:0108:010c:err:module:hacks_init HACK: Simulating sched quantum in fsync.342.603:0108:010c:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems342.605:0108:010c:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problemsFull log available here.
SysInfo
GPU: Sparkle Intel ARC A770 Titan OC
CPU: Intel Core i7-9700K
Memory: 32GiB DDR4
Full system info here.
Attached as requested Steam Runtime Diagnostics report
All necessary packages regarding X.org, Mesa/Vulkan, and Intel are installed as indicated by the Void Wiki.
Using the i915 kernel driver and X.org modesetting user-space driver.