The game launcher starts but when I click on play, whole screen goes black and nothing happens. System becomes unresponsive and I need to hard reset it.

      • INeedMana@lemmy.worldEnglish
        1·
        10 months ago

        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

  • Renderwahn@lemmy.worldEnglish
    2·
    10 months ago

    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.

  • ShaunaTheDead@kbin.social
    1·
    10 months ago

    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.

  • krey@sh.itjust.worksEnglish
    1·
    10 months ago

    you can no longer switch to a vt?

    have you tried switching to a vt preemptively while launching it (e.g. use the sleep command to delay start or use chvt in the same input line)?

    check the syslog, if any.

    idk if it’s still a thing, but the kernel had magic sysrq key combos that would still work when a lot of stuff crashed.

    maybe try logging the game stderr and stdout to a file. maybe even with additional strace.