Hello @electricOzone, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Additionally, please switch to Proton 3.7-5 beta, add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
@kisak-valve Warhammer 40K Dawn of War: Soulstorm is labeled as Whitelisted on the announcement. Why is it "unofficial" here?
https://steamcommunity.com/games/221410/announcements/detail/1696055855739350561
Thanks @SteveHeist, label fixed.
After switching to Proton 3.7-5 beta, the issue no longer appears. I'll leave logging turned on in case this occurs again.
I'm also having this issue in proton 3.7-6
system: https://gist.github.com/Makreig/84be2bbf24ebf1fa43047518e51e501a
for me, it's happened twice, both times after defeating the eldar HQ playing as Necrons, while other eldar locations still exist.
Issue was persisting on the newest proton, however it turns out this crash is a windows crash caused by the game running out of memory. I used the windows application large address aware in wine and patched the exe, this fixed the crash for me.
Hello @jackarsnel, newer Proton should not need a modified executable because it has PROTON_FORCE_LARGE_ADDRESS_AWARE.
For anyone seeing this issue, does adding PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% to the game's launch options and overriding the Proton version to 3.16 (or newer) in the game's settings have an effect?
I can confirm that adding PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% to the game's launch options, with Proton 4.11-6, seems to fix the issue.
proton 4.11-6x1 2019-10proton 3.7-6x1 2018-09proton 3.7-5x2 2018-09PROTON_FORCE_LARGE_ADDRESS_AWARE=1x2 2019-10PROTON_FORCE_LARGE_ADDRESS_AWAREx1 2019-07PROTON_LOG=1x1 2018-09
Playing the campaign, after a battle is finished, the game will frequently crash to the desktop. I can provide logs as needed, just let me know what is needed.