• 467 Posts
  • 1.75K Comments
Joined 3 years ago
cake
Cake day: July 19th, 2023

help-circle



  • Switching to flatpak steam will often fix these weird steam problems.

    For actually troubleshooting it, I’m guessing you have an issue with your steam runtime for Linux games. Try running steam with the console command:

    STEAM_RUNTIME=0 steam

    and see if your games work. Basically by default Steam bundles it’s own runtime packages to run Linux games with. Setting steam runtime to 0 as part of the launch will disable this functionality, and use your systems packages instead.

    Another thing you could try, you can open game properties and go to the compatibility section. There you can check “force compatibility layer” and try different steam Linux runtimes (if you have them installed).



















  • Basically it can play lower power games directly, or display higher power games from your PC.

    Both the Quest and the Steam Frame use ARM hardware, this is the same type of hardware used in phones. This hardware is noteworthy because it’s more power efficient that x86 type hardware, which is what traditional PCs use. Many VR games are made to run directly on the Quest and should be hardware compatible with the Steam Frame too since they both use ARM.

    The Steam Frame can also run x86 games thanks to an emulation layer called FEX that valve has been working on. This is something the Quest cannot do, but many PC games will likely be too demanding to run this way. VR games are naturally performance demanding since the game needs to be rendered twice for both eye perspectives, and needs decent resolution. Valve has said that it will be slightly weaker than the current Steam Deck in performance, and that’s probably before we consider the extra performance requirements of VR and the performance overhead of FEX.

    So based on that, I would assume NMS would not run well directly on the Frame itself, and you would instead need to run it on your PC and display it on the Frame.