It seems to mostly happen to 3D games, very rarely for 2D ones.

Normally, this wouldn’t be much of an issue for me since I install everything to secondary SSDs anyways, but the one piece of software that is driving me up a wall is Steam VR, since its installation folder can’t be moved.

I could find plenty of fixes when it came to the opposite problem (launching games from another drive) but nothing for my situation.

Any solutions or even just point me in the right direction where to start when it comes to troubleshooting something like this?

OS: Endeavour OS

GPU: RTX 2070 (latest Nvidia drivers)

CPU: Ryzen 2700X

Happens on both X11 and Wayland environments and everything is up-to-date

Edit: also this seems to happen with every version of Proton

  • Max-P@lemmy.max-p.me
    link
    fedilink
    English
    arrow-up
    10
    ·
    11 months ago

    First step there would be to get some logs. Launch steam from a terminal and output to a file:

    steam 2>&1 | tee steam.log
    

    Launch a game and watch the terminal to see what happens.

    If you moved games after launching them, clearing their Proton containers can help. I had some games set to extremely old Proton versions that couldn’t launch because the version jump was too big. I’ve also seen vanilla wine prefixes break when moved due to some symlinks.

    But those are guesses, the logs will tell you. Sometimes it even actually tells you how to fix it!

    • RevolverUnit@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      11 months ago

      Thank you, actually having a log to go through was very useful! Kinda. I managed to suss out that vkBasalt was having a config issue, which I eventually fixed. Now all my OS drive games seem to launch fine, except SteamVR (still).

      I was able to do a little more research with info from the log and I found out running SteamVR the usual way was broken. Launching Steam from /usr/lib/steam/ makes it…sorta work.

      Yeah, turns out it happened to be a separate issue from my initial problem, but with the same symptoms.