protonscr

Stronghold Crusader: Definitive Edition

protonopen appid 3024040Game compatibility - Unofficial
ValveSoftware/Proton#9105 · opened 2025-10-16 by prof-frosty · updated 2026-08-29 · 7 comments · github · game page · search this game
Pprof-frosty 2025-10-16 github

Compatibility Report

  • Name of the game with compatibility issues: Stronghold Crusader: Definitive Edition
  • Steam AppID of the game: 3024040

System Information

I confirm:

  • [ X] that I haven't found an existing compatibility report for this game.
  • [ X] that I have checked whether there are updates for my system available.

steam-3024040.log

Symptoms

Game crashes on starting at Firefly logo after it worked the first time.

Image

Reinstalling does not solve this.

Reproduction

  1. Start game
  2. First time everything works flawless (can play skirmish etc)
  3. Stop game
  4. Start game
  5. crash at Firefly logo
Aaaclarker 2025-10-18 github

Same here. Played a long session one day and crashes at the logo screen on day 2.

Possibly related for me was that the v2.0 Autum Update came out on my day 2 so it may be related.

Pprof-frosty 2025-10-19 github

I think the Autumn update is not the reason for that. At least the problem was already in v1.4 on my side.

Ssimifor 2025-10-20 github

Do you have to play for a long time for the issue to manifest? does wiping the game's prefix allow the game to start again?
I tried starting a classic trial, letting the game run for a few seconds, then closing and reopening the game and there's no issue with either proton 9 or experimental, so I'm curious if those affected can get the game to crash with just that

Pprof-frosty 2025-10-20 github

I think I have found the problem.

I tried deleting the prefix and setting different proton version but that didn't help.

After that I deleted the settings.cfg

rm ~/.local/share/Steam/steamapps/compatdata/3024040/pfx/drive_c/users/steamuser/AppData/LocalLow/Firefly\ Studios/Stronghold\ Crusader\ Definitive\ Edition/settings.cfg

and I could start the game again. After that I checked the difference in the newly created settings.cfg.

Here I found that my old settings.cfg looked like this:

# OLD
...
WinWidth:2880
WinHeight:1800
FullWidth:1920
FullHeight:1080
...

and the new one like this:

# NEW
...
WinWidth:-1
WinHeight:-1
FullWidth:2293
FullHeight:960

Maybe that occured because I played on 2 different devices (notebook & pc) with cross saves.

Aaaclarker 2025-10-23 github

@prof-frosty can I ask what Proton version you're running? I've tried deleting the settings.cfg as well as the entire 3024040/ path without any luck - same Unity crash at the splash screen. I did adjust some settings that first time I played (cursor, resolution size) so I wonder if there's an incompatible setting that is persisting.

Pprof-frosty 2025-10-25 github

@aaclarker currently I am using Proton 10.0-2 (beta) but I also have Steam Overlay disabled. Maybe you could post settings.cfg then I could check if it also crashes on my side.

Deleting the prefix did not help in my case because steam synchronized it back from the cloud.

Vvanytsvetkov 2026-08-29 github

I can reproduce a related in-game crash with Proton Experimental 11, while Proton 9.0-4 did not reproduce it in a longer test.

System:

  • Game version: V2.8.2, Steam build 24816905
  • OS: Debian 13, GNOME Wayland
  • Kernel: 6.12.105+deb13-amd64
  • GPU: AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)
  • Mesa: 25.0.7
  • Proton Experimental: experimental-11.0-20260826-x86_64
  • Proton 9.0: proton-9.0-4f

Results:

  • Proton Experimental: launched at 21:55:19 and the game process crashed at 22:02:07, after 6 minutes 48 seconds.
  • Steam logged:
    Trying to close low level socket support, but we still have sockets open!
    Failed writing minidump, nothing to upload.
  • Unity Player.log ended abruptly without the normal shutdown memory statistics.
  • Proton 9.0-4f: launched at 22:11:45, played for 1 hour 11 minutes, and exited normally at 23:22:53. Player.log contains the normal shutdown memory statistics.
  • No OOM, kernel segfault, GPU reset, or amdgpu error was logged.
  • I did not reinstall the game or delete the prefix; I only changed the Proton version.

This is an in-game crash rather than the startup crash originally reported. One successful 71-minute run is not conclusive, but switching from Experimental to 9.0-4 appears to be an effective workaround so far.

Proton versions