• 0 Posts
  • 12 Comments
Joined 6 months ago
cake
Cake day: January 9th, 2024

help-circle



  • Over-explaining is my biggest issue. I’m entirely self taught and the trash quality of certain softwares with non-descriptive variable and function names sort of steered me towards clearly naming things (sometimes verbosely). That has the unfortunate side effect of repetition when documenting and it comes across as sarcastic or condescending when proofreading.

    Its far easier to have a machine do it than to second-guess every sentence.

    You mentioned a llamafile, is that offline? I’m using GPT-4 at the moment because my partner has a subscription. If so, I maaaay have to check it out ^^








  • Oh damn, you’re using the snap version of Steam, this is unfortunately outside of my area of experience :(

    Some key error messages I see are:

    /home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steamwebhelper.sh: line 53: /proc/sys/kernel/unprivileged_userns_clone: Permission denied
    /home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steamwebhelper.sh: line 60: /proc/sys/user/max_user_namespaces: Permission denied
    

    and

    flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13vkEnumeratePhysicalDevices failed, unable to init and enumerate GPUs with Vulkan.
    BInit - Unable to initialize Vulkan!
    

    You’ve got permission errors and a GPU driver issue somewhere, likely related to the permission errors. The flock errors stand out to me also, as they are fonts. Maybe required fonts for the game to run?


  • I don’t have any idea about your hardware issues. They’re likely unrelated if the game has already been played without issue.

    For the steam diagnosing, start with running steam from your terminal, by running steam. You may get lucky and the error is clearly identified in the console.

    If that fails, backup $HOME/.local/share/Steam/steamapps/compatdata/221100 - the 221100 is the app ID of of DayZ on the steam store. After backing it up, delete the original 221100 directory and re-launch the game. This doesn’t delete the game, but rather deletes the Proton prefix for the game.

    If the game launches, copy any save files (if any) you may have in the backed-up 221100 directory over to the new one.

    The above worked for me when I had similar issues when playing Batman: Arkham Asylum.

    To be thorough, have you tried any other games to rule out your hardware being an issue?