From what I can find it seems that it is only available on Steam. And a lot were able to run it without problems
this post was submitted on 11 Sep 2023
9 points (84.6% liked)
Linux Gaming
15275 readers
157 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
Yeah that's what's baffling me. I'm even thinking of switching to Mint or Fedora lol
I don't think that's a solution, unless one of these installs out of the box some other version of a driver or module. And all three are rather using older versions. Maybe Mint could be a little bit more up to date.
I would propose: execute steam with PRESSURE_VESSEL_SHELL=instead (PRESSURE_VESSEL_SHELL=instead steam in a terminal or launcher where you type what to execute) and once you have xterm run the game with "$@" > $HOME/tmp/sniper.log 2>&1. That will redirect the output from the process to the file which you can use after reboot to search what is the problem you are having. If there's not much inside, retry with export WINEDEBUG=+all; "$@" > > $HOME/tmp/sniper.log 2>&1. The latter will run very, very slowly but should print debug of everything that happens in proton
I just tried starting it, works without issue with proton experimental. opensuse tumbleweed, Kernel: 6.4.12-1-default x86_64, Device-1: v: 4.6 Mesa 23.1.6 renderer: AMD Radeon RX 7900 XTX (gfx1100 LLVM 16.0.6 DRM 3.52 6.4.12-1-default)
As for debugging try sshing into your box and check dmesg or check the system journal.
Add PROTON_DUMP_DEBUG_COMMANDS=1 %command% to the Launch Options in the Properties menu of the game. Launch the game once and then check in /tmp/proton_(your username). There should be bash scripts for running the game in there. Close the game in Steam and launch the game using the ./run command and see what errors come up.