protonscr

Proton doesn't support displaying UE4 Crash reporter.

protonclosed
ValveSoftware/Proton#6306 · opened 2022-11-09 by PoorPocketsMcNewHold · updated 2025-02-09 · 0 comments · github
PPoorPocketsMcNewHold 2022-11-09 github

Replicated on Proton 7-0.4 and previous stable release versions throughout the years.

Hi there,
When crashing any UE4-based games, via actual game crashes, the UE4 game crash prompt doesn't display making any users or in my case, QA testers, wonder the reason of the crash, but effectively the nature of it.
To be able to still be able to check the reason of the crash, one have to find the corresponding crash log in the game own prefix compatdata folder, to search for Epic UE4 own App Data folder or the set game one for crash logs.
This is even more annoying for simple users, who, very likely, won't take the effort to effectively search for the crash log, to at least have a reason to investigate their crash if they at least still report it to us.
This has happened to multiple games, but I believe this is just inherent to the game engine in itself.
#4138 POSTAL 4: No Regerts (707030) (One game that i particularly often voluntarily crash as a QA tester).
#2391 Tower Unite (394690)
#5985 Ready or Not (1144200)
#731 Crash Bandicoot N.Sane Trilogy (731490)

Expected behavior

Shows the UE4 Crash reporter.
image
This is not my image, nor took from Wine/Proton. This is just a visual example of the UE4 default crash reporter screen.

Actual behavior

Just fail silently and close the game process.

Nothing extracted yet.