AH with the 16D chess amiright? Just cannot play without a crash…I mean…I enjoyed some of the offbeat bugs like getting yeeted off the board when stepping over an atomoton, or the first bombardment missions from the DS where it was pure bedlam hell… But this? Chefs kiss…the bug of all bugs! An unplayable game! THINK of the MEMES!
You must log in or # to comment.
I was having crashing issues like crazy on steam os but I deleted the game then deleted the game guard file and re installed then reset my pc ands that stopped the crashes for me. Really annoying that you have to do that though and that was my case it may not work for you. I waited a bit to touch that supply FRV and the first time I load it I crash xD
Haven’t played in a year or so. I should really put on a cloak again
As someone who has played since release, the bugs and technical issues would have driven me off if it wasn’t for the fantastic writing and Starship Troopers inspired setting. Not to mention the hilarious communitt choices like overwhelmingly saving orphans over anti tank mines multiple times in a row.
The Malevalon Creek Memorial & Interrogation Center for Human Rights needs our support!
Yeah…buuuut. How can I support if I cannot participate? i literally get 1 maybe 2 minutes on a planet and it crashes…I’m playing in unmodded on a steam machine and it sucks.
I*
You shouldn’t be surprised the Linux version isnt stable. I haven’t even gotten Gnomoria to run perfectly stable yet and it’s significantly less of a game.
As someone who had been playing on Linux without issues, don’t blame Linux here. The game used to run just fine about half a year ago. I don’t know how it runs now, I stopped playing when I got fed up with the developers throwing in difficulty for the sake of difficulty.
I’m only “blaming” Linux in that devs rarely ever spend as much time on that version vs the Windows version.
It’s not necessarily Linux’s fault. OP could have a driver that isn’t playing nice for all we know.
It has been stable since release for me on Bazzite.
I think I had 1 CTD ever. My friends on windows are the ones that have in the past had such large problems that we had to stop playing it for a while together because their games were crashing so much lol.
Actually I am a bit surprised, I played on the steam deck just about since launch and then switched over…I don’t get everything on it that regular PC have and I get that but I should be at least able to play it
I can try suggesting some env vars to run the game with when I’m on my PC.
It has been running fine for months for me but I keep reading around that it’s specifically a problem with Linux, so I suspect my excessive tinkering accidentally got the game working
wall of text
It turns out I don’t have many env vars:
# idk if this does anything, I haven't been using mangohud for a bit MANGOHUD=0 # I don't even know where I found this, but I limit my games' framerates whenever I can so I use it DXVK_FRAME_RATE=60 # This does/did actually fix an issue, where the game would stutter after a while IF YOU DON'T USE THE STEAM INTEGRATION (which is true by default if you use gamescope) LD_PRELOAD=""However, there’s a whole bunch of things my launcher script does.
For one, every time it runs, I hardcoded a 1/16 chance to delete some caches - a friend of mine (on Windows) told me that deleting his shader cache fixed frequent crashes on several occasions.
Those caches are:
$your_steam_library/steamapps/common/Helldivers\ 2/vkd3d-proton.cache
$your_steam_library/steamapps/common/Helldivers\ 2/vkd3d-proton.cache.write
$your_steam_library/steamapps/compatdata/553850/pfx/drive_c/users/steamuser/AppData/Roaming/Arrowhead/Helldivers2/shader_cache(you can just nuke the entire directory)I also run HD2 in Hyprland (not that I would expect anyone to base their WM/DE choice entirely on a single game);
finally, I run it with gamescope, more specifically:
gamescope --backend wayland -F nearest -w 1920 -h 1080 -f -r 60 -o 30 -- $cmd # ... where `$cmd` is the array of arguments provided by Steam when you specify launch options as such: `/path/to/my-launcher.zsh %command%` # (this is Zsh syntax, no quotes are needed around `$cmd` for the array to expand properly)
