Repository navigation
Loadout (208090) #10166
Description
Compatibility Report
- Name of the game with compatibility issues: Loadout
- Steam AppID of the game:
208090
System Information
- GPU: NVIDIA / AMD / Intel
- Video driver version: Any
- Kernel version: Linux 6.x
- Proton version: Proton >= 11.0 (Broken) / Proton <= 10.0-4 (Working)
I confirm:
- That I haven't found an existing issue for this game in the issue tracker (or that my issue is a newly introduced regression in Proton 11).
- That I have checked whether there are updates for my system available.
Symptoms
Starting Loadout under Proton 11 or newer results in an immediate crash during early initialization (shortly after the splash screen appears, before the main menu loads). The game launcher terminates with an Access Violation (0xC0000005) and spawns SubmitReport.exe.
- Proton 10.0-4: Works out of the box.
- Proton 11.0: Crashes during RenderSystem init.
Reproduction Steps
- Install Loadout (Steam AppID
208090). - Force Compatibility tool to Proton 11.0 or newer.
- Launch the game -> Game closes within 2–5 seconds with crash reporter window popping up.
- Switch Compatibility tool to Proton 10.0-4 -> Game boots successfully to server connection screen.
Relevant Log Excerpt
Game crash report shows:
...
Loadout.exe has encountered an unrecoverable error:
Error Type: Access violation
...
Activity
[-]Loadout (208090) - Startup crash (regression in Proton 11) due to 32-bit Large Address Aware memory handling in ntdll.so[/-][+]Loadout (208090)[/+]kisak-valve commentedon Sep 22, 2026
Hello @voltflake, this is a lot of noise for what could have been written as: "The game needs
PROTON_FORCE_LARGE_ADDRESS_AWARE=0 %command%to start with Proton 11."Please add
PROTON_LOG=1 %command%to the game's launch options, reproduce the crash, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)voltflake commentedon Sep 22, 2026
@kisak-valve thanks for suggestion but unfortunately that doesn't fix anything. Attached proton log and game crash report.
loadout_proton11_crash_report.zip
steam-208090.log
voltflake commentedon Sep 24, 2026
@kisak-valve sorry for providing my early investigation details, they were flawed. I did my "homework" now and i managed to make a minimal fix locally. Regression was caused by new compiler standards introduced in GCC 14.2 which is shipped by SteamRT 4 (Medic) SDK, previous environment used GCC 10. Starting from GCC 12,
-ftree-vectorizeoptimization became included into-O2flag. This optimization caused something in user32.dll to misbehave in a way that made game crash with access violation. Adding-fno-tree-vectorizewhen compiling user32.dll causes game under resulting proton build to no longer crash. Should i open an issue about that in proton-wine or leave my investigations here? I'd really like to speedup fix development and i don't really know what is the best way to do it here...kisak-valve commentedon Sep 24, 2026
In general, we're using one issue report per game title. This is the right place for all feedback related to this game.