No Man's Sky

cmace42

Platform: Nobara Linux 42, Kernel 6.16.4-201.nobara.fc42.x86_64
Headset: Quest 2
CPU: 12th Gen Intel(R) Core(TM) i9-12900H
GPU: NVIDIA GeForce RTX 3070 Ti Laptop GPU, Driver Version 580.82.07
OpenXR: openxr-libs-1.1.50-1.fc42.x86_64
Vulkan:

• NVIDIA: driverVersion = 580.82.7.0, deviceName = NVIDIA GeForce RTX 3070 Ti Laptop GPU
• Intel: driverVersion = 25.2.1, deviceName = Intel(R) Iris(R) Xe Graphics (ADL GT2)
  Steam / Proton: Proton GE 10.25
  When launching No Man’s Sky VR via SteamVR with ALVR, the game shows a black screen for a few seconds and then closes automatically.

vh45f

I managed to get the game to start using Proton 9.0-4 but it would start in non-vr mode even when forced to within steam's settings.
The VR headset is stuck in the Next up... screen while the game's audio gets correctly routed to it.
Mesa: 25.2.6
DE: GNOME 49.1
Kernel: Linux 6.17.7-300.fc43.x86_64
CPU: AMD Ryzen 7 9800X3D (16) @ 5.27 GHz
GPU: AMD Radeon RX 6800 XT [Discrete]
Memory: 30.89 GiB

SimFarmer

WiVRn with xrizer: All I had to do was set the headset resolution down to about 85% and then tweak some in game graphical settings and it looks and plays fantastic. Proton GE 10-10 WiVRn on envision with xrizer. The one problem I do see is that the inputs do not display properly. They just show a yellow exclamation mark triangle. playing with wivrn without xrizer resulted in buttons not working at all.
overall it is a fantastic experience on WiVRN
ALVR: I do not know what it is with ALVR on this game but I ticked the resolution and graphics down to the same as WiVRn however it just runs so much slower. I am sure with a bit more tinkering on my end I can get it there, but I feel it might be at some graphical costs.

clumsynick

WiVRn need OpenVR compatibility layer 'xrizer'

victor-borges

Used Envision with WiVRn and the experimental2 branch of RinLovesYou/xrizer, there is the ⚠️ glyph issue and another one is that changing FSR scaling options crashes xrizer with a frame out of order error, the setting gets saved and works afterwards, playable.
Tried using the default Envision profile for WiVRn with OpenComposite, but got the issue of the controller turning way too fast, unplayable.

Strawb3rry-Milk2

(report made March 16 2025) i was having some serious issues with controller turning (just either didnt work, or was WAY too fast) but i fixed it by switching my compatibility layer, i installed xrizer with AUR, then set the launch option to VR_OVERRIDE=/opt/xrizer, and it worked! hope this helps others

Mon-Ouie

System Information:

• Linux arch-laptop 6.13.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 22 Feb 2025 00:37:05 +0000 x86_64 GNU/Linux
• GPU: AMD RX 7900 GRE (driver: Mesa 24.3.4)
• CPU: AMD Ryzen 5900X
• SteamVR 2.9.6
• Proton 9.0-4

alpnist

Works perfectly with ALVR.
WiVRn mostly works but when entering a ship, cannot grab the throttle with the left hand or use the left hand exit. Right hand works to grab the stick and door. Left hand works outside of the ship, pressing the grip curls the fingers and toggles the scanner as it is supposed to. This is a game breaking bug because you can't really play if you can't fly ships. Tried with both WiVRn 0.19 and 0.23 - same issue.

PoorPocketsMcNewHold

No controller glyphs issues with the Valve Index despite previous reports, at least for me. The game does suffer from degraded performance, but it can just be addressed via the graphic settings.

makulski

Works out of the box - seems to perform really well on my setup via WiVRn.

TakinaLisa

SteamVR - works perfectly, there used to be a lot of bugs on Linux in general but as of February 2025 I don't see any issues (except usual SteamVR shenanigans)
Monado/OpenComposite - controller prompts are replaced with a warning sign but still work, on Vive Wands you're forced to use the default controller bindings, and trackpads don't work so I'm unable to turn around.

Deytron

Works by using latest WiVrn with Xrizer, and Envision for all the setup
Controllers did not work previously with OpenComposite, but work now
Only issue : the controller prompts are replaced with ⚠️ but do work