Repository navigation
RiftLinux is a modified Monado, specialized for full Oculus Rift CV1 support. One package runs the headset, its
Constellation sensors and its Touch controllers on Linux, in SteamVR and in OpenXR apps. No Windows, no Oculus
software, no Meta account.
This release fixes Touch controllers that froze or jumped in full view of the sensors
(#5), SteamVR blocking the driver at every start on some systems
(#3), and the IPD slider (#6).
It includes everything from the 0.1.4 pre-release and replaces 0.1.3 as the current release.
Rift Home 0.1.0, a VR desktop made for RiftLinux, comes out alongside it. How the
controller fixes work, with the measurements, is in the release post.
Fixed
- Touch controllers that froze or jumped in full view of the sensors now track
(#5). A turned or offset motion sensor is learned and corrected while
you play.riftlinux-setup controller-alignment statusshows it,offturns it off. - SteamVR Home and games start again after Steam's newest client update
(#7). Steam's new layout left out the runtime SteamVR Home's launcher
needs. RiftLinux links it back by itself when SteamVR starts, at login and when you plug the headset in, and
riftlinux-setup checkshows it. Steam's older layout is left as it is. - SteamVR no longer blocks the driver because of lsfg-vk (#3). It's
kept out of SteamVR and RiftLinux's runtime, and games still get it. Runriftlinux-setup repaironce to lift an old
block. - A controller with a dead battery, or out of radio range, holds still instead of spinning.
- The headset is found again after OpenHMD or another Rift driver held on to it.
riftlinux-setup checkshows it,
riftlinux-setup repairfixes it. - HDR video: no hard ring around bright glows, and highlights keep their colour.
- No black wedges at the bottom of each eye in Unity games and OpenVR games through xrizer, in RiftLinux's own
runtime. - RiftLinux's own runtime no longer grows in memory on NVIDIA when an app keeps opening and closing windows.
- RiftLinux's own runtime no longer crashes on the way out.
New
- Touch controllers keep up with fast punches. Each one has its own motion-sensor filter.
riftlinux-setup controller-tracking 0.1.4brings back the old tracking. - No freeze after a very fast wrist turn, faster than the motion sensor can read.
- A half-hidden controller stays tracked while it turns, seen by only two or three LEDs.
- A controller far from the sensors, seen by only three or four LEDs, is found again much sooner instead of
freezing. - A controller whose motion sensor reads a few degrees off its LEDs no longer has good camera views of it turned
away after it was out of view. - Fewer controller jumps.
- Controllers keep moving for up to a second out of view. Found again after that, they're shown where they are
at once instead of sliding back.
riftlinux-setup controller-coast 300brings back the shorter behaviour. - IPD on the same scale as Windows, followed live in SteamVR
(#6), and settable by hand in the Rift tab or with
riftlinux-setup ipd 63.5. - RiftLinux's own runtime (without SteamVR): several apps at once with Switch application, WebXR in Chromium
(guide), a Nix flake and NixOS module,
andlibmonadocalls for screenshots, switching apps and a lens test pattern.
Tested on
- Compared with Windows, on replays of two sessions recorded there: tracked left 95.5 % at night and 95.4 % by day
(Windows 92.8 and 95.2), right 97.7 and 96.5 % (96.3 and 96.2), no jumps over 5 cm. - The left controller's distance from where Windows tracked it (90th percentile): 13.8 mm at night and 19.9 mm by day,
against 17.6 and 30.5 mm before this release's tracking changes. Held still, a controller shakes a little more than
on Windows (0.1 to 0.4 mm). - A recording of fast punches: the left controller was held still 0.9 s out of 90 instead of 11.2 s.
- A recording 3.4 m from the sensors, the left controller mostly seen by 3 to 5 LEDs: held still 5.2 s out of 149
instead of 10.3 s, and found again 6 cm from where it was shown instead of 16 (median). - The controller fix (#5), with a fault added in software to real
recordings: tracked 31 % of the first session without the fix and 90 % with it (95 % with no fault). No real
faulty controller has been through it yet, so please tell us on #5 how yours tracks. - CachyOS (KDE Plasma 6.8, Wayland) with NVIDIA 615: the release packages, WebXR in Flathub's Chromium 157, and a Unity
game through Proton and xrizer. - lsfg-vk itself wasn't tested here (none of our machines has it). The crash report on #3 places the crash inside it.
- Steam's runtime for SteamVR Home: Steam's old and new layouts (with Steam's legacy runtime, with only the scout
runtime tool, and with a stub link) in a test home, for both the setup tool and the driver's own check at SteamVR's
start, and a real Steam on the old layout, which was left unchanged. The link made is the one that fixed it for the
reporter of #7. - The packages are installed and checked in clean Ubuntu 22.04, 24.04 and 26.04, Debian 12 and 13, Fedora 43 and 44,
and Arch systems. - Not tested here: AMD and Intel graphics for this release's changes.
- x86-64 computers only.
Install
Download the package for your distribution and SHA256SUMS below, check them with
sha256sum --ignore-missing -c SHA256SUMS, and install. Upgrading from an earlier version is the same command:
sudo apt install ./riftlinux_0.1.5_amd64.deb # Debian, Ubuntu, Linux Mint, Pop!_OS
sudo pacman -U riftlinux-0.1.5-1-x86_64.pkg.tar.zst # Arch, CachyOS, EndeavourOS, Manjaro
sudo dnf install ./riftlinux-0.1.5-1.x86_64.rpm # Fedora
tar xf riftlinux-0.1.5-x86_64.tar.gz && sudo ./riftlinux-0.1.5-x86_64/install.sh # any other distributionThen restart Steam once (Steam, Exit, and start it again). Steam loads the part that starts SteamVR when it starts, so
it only picks up the new version after a restart. The user guide
walks you through the first start, and the settings guide
lists every setting.
Known issues
- A VR game started from Steam while SteamVR isn't running opens on the monitor, because Steam on Linux doesn't start
SteamVR for it. Put the headset on first (SteamVR then starts), or start SteamVR from Steam and then the game. - Steam's client can crash when a flat (non-VR) game opens a window while SteamVR is running. That's a Valve bug, not
this driver (SteamVR for Linux #963 is the same
crash, reported for the Desktop tab). - SteamVR's compositor can crash as SteamVR quits, after the session is over. It's harmless, and the exit code is
SteamVR's own (SteamVR for Linux #990 is the same
crash with Valve's own streaming driver). - SteamVR's compositor sometimes doesn't start on the first try (a freeze in SteamVR's own startup). SteamVR tries
again, and SteamVR Home shows up later than usual. Once SteamVR quits, RiftLinux ends the leftover copy of SteamVR's
server from the failed try, so the next start isn't blocked. - Steam asks some questions before a game's first start on the monitor, not in the headset. If a game doesn't start
from inside VR, take the headset off and answer them there. - SteamVR's Desktop tab is empty on Linux
(SteamVR for Linux #693). WayVR shows the desktop
as an overlay. - With NVIDIA on Wayland and a VRR monitor, the headset's picture can tear unless VRR is hidden from the driver
(NVIDIA's bug, open-gpu-kernel-modules #992). Run
riftlinux-setup nvidia-vrr conceal. - NVIDIA's 615 driver keeps a little memory each time a program sends work to the graphics card and never gives it
back, in every OpenGL and Vulkan program. You notice it in programs that run for a long time. The
troubleshooting page names the workaround
from NVIDIA's forum (an undocumented driver setting). RiftLinux doesn't set it for you. - With HDR on, GNOME can leave the desktop's colours washed out when the headset connects or disconnects. Switching
HDR off and on again in GNOME's settings fixes it (likely
mutter #5083, fixed for GNOME 51).
The README's Known issues section has the full list, including app issues under Proton.
Reporting a problem
Open an issue with the bug form and add the output of riftlinux-setup --json check, SteamVR's log
(~/.local/share/Steam/logs/vrserver.txt) and the driver's own log (~/.steam/steam/logs/vrstartup-linux.txt). Say
which GPU and driver you have.
For a tracking problem, record a session. Run riftlinux-setup record on, start SteamVR and do whatever shows the
problem, then attach the recording from ~/.cache/riftlinux and SteamVR's startup log
(~/.steam/steam/logs/vrstartup-linux.txt). Turn it off afterwards with riftlinux-setup record off. For a
controller problem, also add the output of riftlinux-setup controller-alignment status.