Gamepad are not working using experimental proton.
just updating
serejo1@serejo-PC
/\ OWOS endeavOwO
// \ MOWODEL TUF B450M-PRO GAMING
//>ω<\ KEWNEL Linuwu 7.0.12-arch1-1 x86_64
// \ \ CPUWU AMD Ryzen 5 3600 6-Cowe Processor
/ / ) ) GPUWU Advanced Micro Devices, Inc. AMD/ATI Navi 22 Radenyan RX 6700/6700 XT/6750 XT /
//__-- - MEMOWY 7721 MiB/31998 MiB
/--- WESOWUTION 2560x1440
SHEWW /bin/bash
PKGS 1919: 41 (flatpak), 13 (snap), 1865 (pacman)
UWUPTIME 2h, 50m
FSR option are not showing
There seems to be around 15-20% fps regression in experimental compared to 11.0
GPU: RTX 4090
Driver/LLVM version: nvidia 610.43.03
Kernel version: 7.1.5-arch1-1
Proton version: 11.0, experimental.
Proton 11:
Experimental:
ZZZ worked on this system on July 28, 2026. After the July 29 Version 3.1 update, the game no longer gets past the HoYoPlay launch button.
System
Reproduction
The executable is present at games/ZenlessZoneZero Game/ZenlessZoneZero.exe, and Steam reports the app as fully installed with UpdateResult 0.
driverError.log is updated on every attempt with:
[Local_Time]2026-07-29 11:41:56.792
[UTC_Time]2026-07-29 03:41:56.792
initDriver Failed: Error [4,1114,0].
The Unity player log initializes D3D11 and audio, then terminates in MHYPBase.dll.
Compatibility tools tested
No launch options were used. The original Proton Experimental prefix was also restored and reproduced the failure. Other Linux and Steam Deck users are reporting the same launch regression immediately after Version 3.1.
This looks like a Version 3.1 HoYoKProtect/MHYPBase regression rather than a missing executable or damaged Steam install.
At 12:13 (UTC+8), ZZZ launched successfully and reached account login.
Immediately beforehand, Steam downloaded the official Proton Hotfix update from build 24151874 to build 24415271. However, the successful live process is using:
SteamLinuxRuntime_4 ... /Proton - Experimental/proton waitforexitandrun .../Zenless Zone Zero/HYP.exe
The active ZZZ prefix also identifies Proton Experimental, and there is no per-game CompatToolMapping selecting Proton Hotfix. Therefore I cannot confirm that the Hotfix update caused the recovery; a server-side Version 3.1 security configuration becoming available at approximately the same time is also consistent with the evidence.
The last failed attempt updated driverError.log at 12:00 with error [4,1114,0]. The successful ZenlessZoneZero.exe process started at 12:13:37 and remains running under Proton Experimental build 24407790. No game files, anti-cheat files, DLLs, or launch options were modified.
Latest bleeding edge seems to fail launching the game(after launching the game goes fullscreen for a few seconds and quickly returns). It seems to happen whether DX12 is selected or not in the launcher.
It works fine with August 7 Experimental, It started happening with https://github.com/ValveSoftware/Proton/commit/f2dd12c3a4981ce21d5378f6ba8b5af0acea2bf8 .
Log:
steam-4162040.log
My issue was fixed with https://github.com/ValveSoftware/Proton/commit/f275a1c8bbbadca55a18f054416279d69f5780ef.
[4162040] Zenless Zone Zero - D3D12 Crash on Intel Mesa and Prefix Corruption (Fedora)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/10072.
@Abdulrahman-wada posted on 2026-08-16T22:10:22:
The game fails to launch, silently aborting before the game window can render. There are three primary symptoms observed in the terminal logs:
-force-d3d11 and PROTON_USE_DXVK=1 as launch parameters to force a DX11 fallback, the engine still probes for DX12 feature levels before dying (shader_cache_temp_dir_d3d12_64/fozpipelinesv6/steamapprun_pipeline_cache).0 compatibility prefix. The logs continuously output: Proton: Upgrading prefix from GE-Proton11-1 to GE-Proton11-3 ... Prefix has an invalid version?!gameoverlayrenderer.so preloading failures blocking the hook (wrong ELF class: ELFCLASS32).PROTON_USE_DXVK=1 %command% -force-d3d11proton experimentalx4 2026-08ge-proton11-1x1 2026-08ge-proton11-3x1 2026-08proton hotfixx2 2026-07proton 11.0x1 2026-07proton 9.0x1 2026-07PROTON_USE_DXVK=1x1 2026-08PROTON_USE_DXVK=1`x1 2026-08PROTON_USE_DXVK=1 %command% -force-d3d11x1 2026-08mhypbase.dllx1 2026-07
Compatibility Report
System Information
I confirm:
Symptoms
Rendering issues / crashes with Ray tracing / Frame Generation enabled in DX12 mode.
DX12 seems to work fine on it's own. As well as it's working fine with ONLY Super Resolution enabled - DLSS or FSR, any quality.
However the game starts to falling apart, when Ray Tracing is enabled, any quality. The same thing happens with Frame Generation - both DLSS and FSR. Any combination: RT only, FG only, or RT+FG.
Usually happens after several minutes in the game world, with various visuals: mostly 3d scene goes half or fully dark, while UI is visible or partially broken. Sometimes it looks like a generic GPU failure with the crash to desktop some time later after that.
Reproduction
Start the game in DX12 mode with the game launcher
Enable Ray Tracing and/or Frame Generation in graphics options (the exact quality doesn't matter)

Login into the game world to play
Pressing Esc back and forth into the main menu greatly speedup the issues to appear
Can't test it on Windows, so can't really tell if it's platform specific or not.
Attachments:
Screenshots.tar.gz
steam-4162040.tar.gz - Proton logs.
gamemoderunwas added in Launch Options, but it's the same without it.