<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>aiix · Aditya Mehra · #rift-home</title>
  <subtitle>Posts by Aditya Mehra tagged rift-home.</subtitle>
  <link href="https://aiix.space/tags/rift-home/atom.xml" rel="self" type="application/atom+xml"/>
  <link href="https://aiix.space/tags/rift-home/" rel="alternate" type="text/html"/>
  <id>https://aiix.space/tags/rift-home/</id>
  <updated>2026-11-13T14:50:00.000Z</updated>
  <author><name>Aditya Mehra</name><uri>https://aiix.space/</uri></author>
  <icon>https://aiix.space/icon-512.png</icon>
  <logo>https://aiix.space/og.png</logo>
  <entry>
    <title>RiftLinux 0.1.5: Touch Controllers That Froze Now Track, and Rift Home</title>
    <link href="https://aiix.space/blog/riftlinux-0-1-5/" rel="alternate" type="text/html"/>
    <id>https://aiix.space/blog/riftlinux-0-1-5/</id>
    <published>2026-11-13T14:50:00.000Z</published>
    <updated>2026-11-13T14:50:00.000Z</updated>
    <summary>RiftLinux 0.1.5 for the Rift CV1 on Linux: why some Touch controllers froze in full view, what fast punches showed, and Rift Home, a VR desktop made for RiftLinux.</summary>
    <content type="html">&lt;p&gt;&lt;a href=&quot;https://aiix.space/blog/riftlinux-0-1-3-stability-release/&quot;&gt;RiftLinux 0.1.3&lt;/a&gt; was about SteamVR starting when you put the headset on.
Since then, most of what people told me was about one thing: the Touch controllers. One of them would freeze or jump
around in full view of the sensors, every session, while the other one was perfectly fine. That’s
&lt;a href=&quot;https://github.com/AIIX/RiftLinux/issues/5&quot;&gt;issue #5&lt;/a&gt;, and most of &lt;strong&gt;RiftLinux 0.1.5&lt;/strong&gt; went into it, and into
everything I found along the way.&lt;/p&gt;
&lt;p&gt;It also comes with something I’ve been building on the side: &lt;a href=&quot;#rift-home-a-vr-desktop-made-for-riftlinux&quot;&gt;Rift Home&lt;/a&gt;,
a VR desktop made for RiftLinux.&lt;/p&gt;
&lt;h2 id=&quot;whats-new-in-015&quot;&gt;What’s new in 0.1.5&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Controllers that froze or jumped in full view now track.&lt;/strong&gt; RiftLinux learns how each controller’s motion sensor
sits while you play, and corrects it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Controllers keep up with fast punches&lt;/strong&gt;, and no longer freeze after a wrist turn faster than their gyro can read.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fewer jumps&lt;/strong&gt;, and a controller keeps moving for a moment when your hand leaves the sensors’ view.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A controller with a dead battery holds still&lt;/strong&gt; instead of spinning.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The IPD slider&lt;/strong&gt; uses the same scale as on Windows, SteamVR follows it live, and you can set it by hand.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SteamVR Home and games start again&lt;/strong&gt; after Steam’s newest client update
(&lt;a href=&quot;https://github.com/AIIX/RiftLinux/issues/7&quot;&gt;#7&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SteamVR blocking the driver at every start&lt;/strong&gt; (&lt;a href=&quot;https://github.com/AIIX/RiftLinux/issues/3&quot;&gt;#3&lt;/a&gt;) turned out to be
lsfg-vk, which RiftLinux now keeps out of SteamVR.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Without SteamVR&lt;/strong&gt;, RiftLinux’s own runtime switches between apps and runs WebXR in Chromium.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Rift Home 0.1.0&lt;/strong&gt;, a VR desktop for your Linux apps.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;the-controller-that-froze-in-full-view&quot;&gt;The controller that froze in full view&lt;/h2&gt;
&lt;p&gt;This one was strange. Both controllers sit in plain view of the sensors, both have their LEDs lit, and one of them
tracks perfectly while the other freezes, jumps, or flips around all session long.&lt;/p&gt;
&lt;p&gt;To understand why, you need to know one check the tracker does. Each Touch controller has a ring of infrared LEDs that
the sensors see, and a motion sensor inside. RiftLinux works out where the controller is and how it’s turned from the
LEDs, then checks that against the motion sensor’s idea of which way is down. If the two disagree, the pose gets
thrown away, because most of the time that means the LEDs were matched wrong and the pose is upside down.&lt;/p&gt;
&lt;p&gt;The logs people sent on issue #5 all showed the same thing: on the bad controller, nearly every pose was thrown away
by that check. The poses were fine. The motion sensor wasn’t where the check thought it was. In some controllers it sits
turned by a few degrees, or its accelerometer reads a little off, and then every good pose disagrees with it.&lt;/p&gt;
&lt;p&gt;So 0.1.5 learns how each controller’s motion sensor sits. While you play, it compares what the sensors see with what
the motion sensor reads. When you turn the controller, both should turn the same way, and when you hold it still, both
should agree on which way is down. Once it has seen enough of that, it knows how far the sensor is turned and how far
the accelerometer is off, and corrects both before the check. It keeps what it learned for that controller. A
controller that’s only a few degrees off, as healthy ones can be, just gets the check allowing for that.&lt;/p&gt;
&lt;p&gt;Neither of my controllers has this fault, so I couldn’t just try it. Instead I took recordings of real sessions and
put the fault into one controller’s motion sensor in software: turned by 10 degrees, the accelerometer off by
1.5 m/s², or both. Then I replayed each one without the fix, with the fix, and with no fault at all:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://aiix.space/images/blog/riftlinux/controller-fix-tracked.png&quot; alt=&quot;Share of the first session a controller with a fault in its motion sensor was tracked: turned and offset 31.1 % without the fix, 89.8 % with it, 95.0 % without the fault; turned about another axis 78.5, 93.9 and 95.1 %; turned 90.2, 94.2 and 95.1 %; offset 93.7, 95.0 and 95.2 %; turned on a second recording 64.2, 87.3 and 88.6 %&quot;&gt;&lt;/p&gt;
&lt;p&gt;That’s the very first session, before anything is learned. From the next session on, the controller with both faults
was tracked 95.19 to 95.30 % of the time, against 95.16 % with no fault at all. And on the two sessions I
recorded on Windows, controllers without a fault track the same with the fix on or off.&lt;/p&gt;
&lt;p&gt;What I can’t tell you yet is how it does on a real faulty controller, because none has been through it. If one of yours
froze or jumped, please try 0.1.5 and tell me on &lt;a href=&quot;https://github.com/AIIX/RiftLinux/issues/5&quot;&gt;issue #5&lt;/a&gt; how it tracks
now. &lt;code&gt;riftlinux-setup controller-alignment status&lt;/code&gt; shows what it learned.&lt;/p&gt;
&lt;h2 id=&quot;fast-punches&quot;&gt;Fast punches&lt;/h2&gt;
&lt;p&gt;With that fixed, I put the headset on and threw some fast punches. The left controller kept sticking for a moment after
them.&lt;/p&gt;
&lt;p&gt;The recording showed what happened. Between camera frames, the tracker predicts where the controller should be, and it
uses that prediction to check each new pose. After a fast punch, the prediction fell behind the hand by 10 cm or more,
turned up to 35 degrees the wrong way. So the next poses, which were right, looked wrong, and got thrown away until the
tracker gave up waiting and took them.&lt;/p&gt;
&lt;p&gt;What helps is a small filter per controller that carries it from one camera frame to the next on its motion sensor,
the way it’s done on Windows. 0.1.5 adds that, and two more things the punches asked for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Its own motion-sensor filter per controller.&lt;/strong&gt; The prediction now keeps up with the hand.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Three views that agree win.&lt;/strong&gt; When the prediction is off anyway, three clear views of the controller that agree
with each other correct it right away, instead of waiting for 0.3 s.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The accelerometer is trusted less in a punch.&lt;/strong&gt; At 100 m/s², even a tiny error in the accelerometer’s scale adds
up to metres per second squared, and following it carried the controller off.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I replayed the same punch recording through each step:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://aiix.space/images/blog/riftlinux/punches-held-still.png&quot; alt=&quot;How long the left controller was held still during 90 seconds of fast punches: 11.2 s before, 2.7 s with its own motion-sensor filter, 1.8 s when three agreeing views correct it, 1.0 s with the accelerometer trusted less in a punch&quot;&gt;&lt;/p&gt;
&lt;p&gt;From 11.2 seconds of sticking down to 1.0, and never more than 0.2 s at a time. With the last fix below it’s 0.9.&lt;/p&gt;
&lt;h2 id=&quot;a-turn-faster-than-the-gyro-can-read&quot;&gt;A turn faster than the gyro can read&lt;/h2&gt;
&lt;p&gt;One freeze in that recording didn’t fit. The right controller stopped for almost 3 seconds in full view of both
sensors, right after a fast wrist turn, and none of the fixes above touched it.&lt;/p&gt;
&lt;p&gt;The answer was in the gyro. A Touch controller’s gyro can read turns up to 2000 degrees a second, and my wrist turn
went past that. For 22 milliseconds the gyro was pinned at its limit, so the turn it reported was shorter than the turn
my hand made. The motion sensor’s idea of which way is down came out of that turn about 10 degrees off. The check
throws away poses more than 8 degrees off, so it threw them all away:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://aiix.space/images/blog/riftlinux/gyro-clip-frozen.png&quot; alt=&quot;Around the fast turn: the gyro pinned at 2000 degrees a second, then every camera pose 9 to 13 degrees off the motion sensor&amp;#x27;s down and thrown away, until the controller was found again almost 3 seconds later&quot;&gt;&lt;/p&gt;
&lt;p&gt;Before the turn, the poses agree with the motion sensor to within a couple of degrees. After it, they’re all over 8,
and the controller sits frozen until the motion sensor slowly corrects itself.&lt;/p&gt;
&lt;p&gt;Now, when the gyro hits its limit, the check allows for what the gyro couldn’t read, until a clear view of the
controller sets its sense of down right again. On the same recording that freeze went from 3.03 s to 0.34 s. Sessions
without such a turn track exactly as before.&lt;/p&gt;
&lt;h2 id=&quot;three-leds-three-and-a-half-metres-away&quot;&gt;Three LEDs, three and a half metres away&lt;/h2&gt;
&lt;p&gt;The last fix came from my own left controller, on release day. I tested at the back of my room, about 3.4 m
from the sensors, and the left controller kept stopping and then sliding back into place. The right one was fine.&lt;/p&gt;
&lt;p&gt;The recording showed why. At that distance the left controller was often seen by only three or four of its LEDs, and
they sit just 3 to 4 pixels apart in the sensor’s picture. The tracker matched each LED to its nearest blob, and when
two blobs were about as near, it gave up. Lost for half a second, the controller was held still, and when it was found
again it slid up to half a metre to where my hand really was.&lt;/p&gt;
&lt;p&gt;Three things changed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Every way of reading the LEDs is tried. With the motion sensor’s orientation known, the tracker tries every way
the three or four blobs could be the controller’s LEDs, and keeps the one that fits clearly better than all the others.&lt;/li&gt;
&lt;li&gt;A few degrees off is no longer a reason to throw a view away. Both of my controllers read 4 to 5 degrees between
their motion sensor’s down and their LEDs. The check that throws away views more than 8 degrees off now allows for
each controller’s own offset.&lt;/li&gt;
&lt;li&gt;Found again, it’s shown where it is, the way Windows does it, instead of sliding there from where it was held.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On that recording the left controller was held still 5.2 seconds out of 149 instead of 10.3, and when it was found
again it was 6 cm from where it was shown instead of 16 (median). For about 3 of those 5.2 seconds it was really out
of view, where Windows holds a controller still too.&lt;/p&gt;
&lt;h2 id=&quot;how-it-compares-with-windows&quot;&gt;How it compares with Windows&lt;/h2&gt;
&lt;p&gt;I keep two sessions I recorded on Windows: the sensors’ camera frames, and where Windows tracked each controller.
RiftLinux replays the same camera frames, so both see exactly the same thing. This is how much of each session each
controller was tracked, counting the second a controller keeps moving after it leaves the sensors’ view, the same way
Windows counts it:&lt;/p&gt;






























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Windows&lt;/th&gt;&lt;th&gt;RiftLinux 0.1.5&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Left controller, evening session&lt;/td&gt;&lt;td&gt;92.8 %&lt;/td&gt;&lt;td&gt;95.5 %&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Right controller, evening session&lt;/td&gt;&lt;td&gt;96.3 %&lt;/td&gt;&lt;td&gt;97.7 %&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Left controller, daytime session&lt;/td&gt;&lt;td&gt;95.2 %&lt;/td&gt;&lt;td&gt;95.4 %&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Right controller, daytime session&lt;/td&gt;&lt;td&gt;96.2 %&lt;/td&gt;&lt;td&gt;96.5 %&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Neither controller jumped more than 5 cm between two frames in either session, same as on Windows.&lt;/p&gt;
&lt;h2 id=&quot;what-didnt-work&quot;&gt;What didn’t work&lt;/h2&gt;
&lt;p&gt;A controller you hold perfectly still shakes a bit more than on Windows, under half a millimetre at the
median. I tried three ways to calm it: blending each camera correction in more slowly, doing that only while the
controller is still, and trusting each camera frame less. Every one of them made the shake smaller by moving the
controller further from where it really is, compared with where Windows put it. That’s not a trade I want
to make for you, so 0.1.5 doesn’t. Windows gets both, which tells me its raw poses are cleaner before any
smoothing, so that’s where I’m looking next.&lt;/p&gt;
&lt;h2 id=&quot;rift-home-a-vr-desktop-made-for-riftlinux&quot;&gt;Rift Home: a VR desktop made for RiftLinux&lt;/h2&gt;
&lt;p&gt;Rift Home started as a test bench. I needed a way to check that HDR video looked right in the headset, so I put a
video window in VR. Then I wanted a second window next to it, then a way to move them around, then a keyboard, and
bit by bit it grew into a full VR desktop. I built it for RiftLinux, and it runs on RiftLinux’s own OpenXR runtime.
Its first version, 0.1.0, comes out together with this release.&lt;/p&gt;
&lt;p&gt;It puts your normal Linux apps around you as windows, Wayland apps and X11 apps through XWayland, and you use them
with the Touch controllers: point, click, right-click and scroll.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://aiix.space/images/blog/riftlinux/rift-home-view.png&quot; alt=&quot;Rift Home in the headset: a browser window in the middle with the virtual keyboard open under it, a terminal to the left, Steam&amp;#x27;s library to the right, and the dock at the bottom&quot;&gt;&lt;/p&gt;
&lt;p&gt;What you can do with it in 0.1.0:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Grab a window to move it, pull it closer or push it away, resize it, tilt it or curve it.&lt;/li&gt;
&lt;li&gt;Pin a window where it is, or let it follow you. Rift Home remembers where every window was.&lt;/li&gt;
&lt;li&gt;Open apps from the Home launcher, with search and a card for every app that’s running.&lt;/li&gt;
&lt;li&gt;Use the dock for the keyboard, notifications, volume, the time and the network.&lt;/li&gt;
&lt;li&gt;Type on a virtual keyboard that opens right under the text field you clicked.&lt;/li&gt;
&lt;li&gt;Get your apps’ notifications in the headset, with their action buttons.&lt;/li&gt;
&lt;li&gt;Watch HDR video (HDR10 and HLG) in any Firefox or mpv window, and in Stremio through mpv.&lt;/li&gt;
&lt;li&gt;Turn a window into a big screen in cinema mode, with the room dimmed around it.&lt;/li&gt;
&lt;li&gt;Play Steam and Proton games in windows, with game mode turning the Touch controllers into a gamepad.&lt;/li&gt;
&lt;li&gt;Lie back in bed or on the sofa: hold grip and press B, or use the dock’s Recline button, and the windows turn to
where you’re looking, even above you.&lt;/li&gt;
&lt;li&gt;Pick a room: three HDR panoramas (Twilight lake, Mountain sunset, Night sky), your own panoramas and photos, or your
desktop wallpapers.&lt;/li&gt;
&lt;li&gt;Fit the headset with the lens test from the Rift’s own setup, a fine cross in each eye.&lt;/li&gt;
&lt;li&gt;Change Wi-Fi, wired network, Bluetooth, sound, date and time, power and the room’s look without taking the headset
off.&lt;/li&gt;
&lt;li&gt;Put any action on any button, or on two buttons pressed together.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&quot;https://aiix.space/images/blog/riftlinux/rift-home-settings-rooms.png&quot; alt=&quot;Rift Home&amp;#x27;s room picker: no room, or one of three HDR panoramas, your own pictures or your desktop wallpapers&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://aiix.space/images/blog/riftlinux/rift-home-settings-controllers.png&quot; alt=&quot;Rift Home&amp;#x27;s controller settings: each action with its default buttons and your own&quot;&gt;&lt;/p&gt;
&lt;p&gt;You can start it two ways. Pick “Rift Home” on the login screen and it runs as its own Wayland session, with nothing
else underneath. Or start it from your desktop’s app menu and it runs on top of your desktop. Close SteamVR first,
since only one VR program can have the headset at a time. It needs RiftLinux 0.1.5 or later, and it’s for the Rift
CV1 with Touch controllers.&lt;/p&gt;
&lt;p&gt;So far I’ve only run it on CachyOS with NVIDIA’s 615 driver. The Fedora and Ubuntu packages install fine on clean
systems, but nobody has tried them with a headset yet, and AMD and Intel graphics are untested. The virtual keyboard
only has the US layout for now (a real keyboard uses your system’s layout). You can get it from
&lt;a href=&quot;https://github.com/AIIX/RiftHome/releases/tag/v0.1.0&quot;&gt;github.com/AIIX/RiftHome&lt;/a&gt;:&lt;/p&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-dimmed&quot; style=&quot;background-color:#fff;color:#24292e;&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6F42C1;&quot;&gt;sudo&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; pacman&lt;/span&gt;&lt;span style=&quot;color:#005CC5;&quot;&gt; -U&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; rift-home-0.1.0-1-x86_64.pkg.tar.zst&lt;/span&gt;&lt;span style=&quot;color:#6A737D;&quot;&gt;     # Arch, CachyOS&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6F42C1;&quot;&gt;sudo&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; dnf&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; install&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; ./rift-home-0.1.0-1.fc44.x86_64.rpm&lt;/span&gt;&lt;span style=&quot;color:#6A737D;&quot;&gt;    # Fedora 44&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6F42C1;&quot;&gt;sudo&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; apt&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; install&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; ./rift-home_0.1.0-1_amd64.deb&lt;/span&gt;&lt;span style=&quot;color:#6A737D;&quot;&gt;          # Ubuntu 26.10&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;On other distributions you can build it from source. The
&lt;a href=&quot;https://github.com/AIIX/RiftHome#readme&quot;&gt;README&lt;/a&gt; explains how, and the
&lt;a href=&quot;https://github.com/AIIX/RiftHome/blob/main/docs/getting-started.md&quot;&gt;getting started guide&lt;/a&gt; walks you through the
first start.&lt;/p&gt;
&lt;h2 id=&quot;the-smaller-things&quot;&gt;The smaller things&lt;/h2&gt;
&lt;h3 id=&quot;the-ipd-slider-that-didnt-move&quot;&gt;The IPD slider that didn’t move&lt;/h3&gt;
&lt;p&gt;The CV1 reports where its IPD slider is, and RiftLinux used to turn that into millimetres on a scale of its own. It now
uses the same scale as Windows, and SteamVR follows the slider as you move it, where before it only read it
once at startup. The headset shows the distance as it changes, “IPD 63.5 mm”.&lt;/p&gt;
&lt;p&gt;Then &lt;a href=&quot;https://github.com/AIIX/RiftLinux/issues/6&quot;&gt;#6&lt;/a&gt; showed something I didn’t expect: on some headsets the slider
doesn’t report at all. The lenses move, the number stays at 57.5 mm, and Windows shows the same.
For those, you can now set your IPD by hand in the Rift tab’s new IPD row or with &lt;code&gt;riftlinux-setup ipd 63.5&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;steams-update-that-hid-steamvr-home&quot;&gt;Steam’s update that hid SteamVR Home&lt;/h3&gt;
&lt;p&gt;This one came in just before the release, in &lt;a href=&quot;https://github.com/AIIX/RiftLinux/issues/7&quot;&gt;#7&lt;/a&gt;, and the report did most
of the work. After Steam’s newest client update, the headset worked fine, but SteamVR Home never showed up and games
wouldn’t start. SteamVR was starting Home over and over, about five times a second.&lt;/p&gt;
&lt;p&gt;The new Steam client moves its files around: &lt;code&gt;~/.steam/bin&lt;/code&gt; now leads to a folder called &lt;code&gt;steamrt32&lt;/code&gt;, and that folder
has no &lt;code&gt;steam-runtime&lt;/code&gt; in it. SteamVR Home’s launcher still looks for &lt;code&gt;~/.steam/bin/steam-runtime/run.sh&lt;/code&gt;, doesn’t find
it, and quits straight away. The reporter found that a link to Steam’s legacy runtime brings Home back, and also that
linking the copy in Steam’s old folder doesn’t, because that one is only a stub.&lt;/p&gt;
&lt;p&gt;RiftLinux now makes that link by itself, every time SteamVR starts, at login and when you plug the headset in, and only
when it’s missing, so Steam’s older layout is left exactly as it is. &lt;code&gt;riftlinux-setup check&lt;/code&gt; shows it, and &lt;code&gt;riftlinux-setup repair&lt;/code&gt; fixes it
straight away.&lt;/p&gt;
&lt;h3 id=&quot;why-steamvr-kept-blocking-the-driver&quot;&gt;Why SteamVR kept blocking the driver&lt;/h3&gt;
&lt;p&gt;Some of you had SteamVR block the RiftLinux driver at every start, and my fix in 0.1.4 didn’t help. The crash report
showed why. It wasn’t the driver at all: lsfg-vk, Lossless Scaling’s frame generation for Linux, loads itself into
every Vulkan program once it’s installed, and it crashed inside SteamVR’s server just as RiftLinux’s display was
starting. SteamVR then blocks whichever driver was starting, which was mine. RiftLinux now keeps lsfg-vk out of
SteamVR’s server, its own helper and its own runtime. Your games still get it.&lt;/p&gt;
&lt;h3 id=&quot;and-the-rest&quot;&gt;And the rest&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A controller whose battery died, or that went out of radio range, used to keep spinning in SteamVR for as long as it
was gone. Now its orientation holds, and it counts as not tracked once the radio stops hearing from it.&lt;/li&gt;
&lt;li&gt;A pose from only three LEDs barely pins down the distance. In one recording, three LEDs put a controller 42 cm closer
than five LEDs had a moment before. Now such a pose gets thrown away when it lands more than 20 cm from a strong pose
just before, and on that recording the left controller’s jumps went from 11 to 0.&lt;/li&gt;
&lt;li&gt;When your hand goes behind your back, the controller keeps moving on its own motion sensor for up to a second, then
stays put, still turning with your hand, and is shown where it is when the sensors find it again.&lt;/li&gt;
&lt;li&gt;If OpenHMD or another Rift driver held on to the headset, &lt;code&gt;riftlinux-setup check&lt;/code&gt; now says so, and
&lt;code&gt;riftlinux-setup repair&lt;/code&gt; gets it back.&lt;/li&gt;
&lt;li&gt;HDR video no longer has a hard ring around bright glows.&lt;/li&gt;
&lt;li&gt;Without SteamVR, when the app you’re in closes, the one before it comes back, and the Rift panel has a Switch
application button. WebXR works in Chromium (the &lt;a href=&quot;https://riftlinux.com/guide/openxr-without-steamvr/&quot;&gt;guide&lt;/a&gt; shows
how), Unity games no longer show black wedges at the bottom of each eye, and there’s a Nix flake and a NixOS module.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;pick-the-settings-for-your-setup&quot;&gt;Pick the settings for your setup&lt;/h2&gt;
&lt;p&gt;Every setting is one &lt;code&gt;riftlinux-setup&lt;/code&gt; command, and every old behaviour is still there if you want it back. The
&lt;a href=&quot;https://riftlinux.com/guide/settings/&quot;&gt;Settings page&lt;/a&gt; lists them all.&lt;/p&gt;
&lt;h3 id=&quot;a-controller-froze-or-jumped-before&quot;&gt;A controller froze or jumped before&lt;/h3&gt;
&lt;p&gt;Nothing to do, it’s learned while you play. If you repaired or swapped a controller,
&lt;code&gt;riftlinux-setup controller-alignment forget&lt;/code&gt; (with SteamVR closed) starts it from scratch.&lt;/p&gt;
&lt;h3 id=&quot;a-controller-tracks-worse-than-with-014&quot;&gt;A controller tracks worse than with 0.1.4&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;riftlinux-setup controller-alignment off&lt;/code&gt; tracks every controller the way it did before the fix, and
&lt;code&gt;riftlinux-setup controller-tracking 0.1.4&lt;/code&gt; brings back the controller tracking from 0.1.4. If you need either, please
tell me on &lt;a href=&quot;https://github.com/AIIX/RiftLinux/issues/5&quot;&gt;issue #5&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&quot;your-hands-often-leave-the-sensors-view&quot;&gt;Your hands often leave the sensors’ view&lt;/h3&gt;
&lt;p&gt;If a controller drifts off while it’s out of view, &lt;code&gt;riftlinux-setup controller-coast 300&lt;/code&gt; goes back to the shorter
behaviour from before. For longer, use a higher value, up to &lt;code&gt;2000&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;the-ipd-number-doesnt-change-when-you-move-the-slider&quot;&gt;The IPD number doesn’t change when you move the slider&lt;/h3&gt;
&lt;p&gt;Measure your IPD and set it in the Rift tab’s IPD row, or with &lt;code&gt;riftlinux-setup ipd&lt;/code&gt; and your number.
&lt;code&gt;riftlinux-setup ipd test&lt;/code&gt; shows what the slider reads while you move it, and &lt;code&gt;riftlinux-setup ipd auto&lt;/code&gt; follows the
slider again.&lt;/p&gt;
&lt;h3 id=&quot;you-have-lsfg-vk-installed&quot;&gt;You have lsfg-vk installed&lt;/h3&gt;
&lt;p&gt;Nothing to do. If SteamVR blocked the driver before, run &lt;code&gt;riftlinux-setup repair&lt;/code&gt; once to lift the block.&lt;/p&gt;
&lt;h3 id=&quot;thick-face-pads-a-face-shield-or-a-covered-wear-sensor&quot;&gt;Thick face pads, a face shield, or a covered wear sensor&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;riftlinux-setup wear-sensor test&lt;/code&gt; shows what the sensor between the lenses reads, and the
&lt;a href=&quot;https://riftlinux.com/guide/settings/&quot;&gt;Settings page&lt;/a&gt; explains what to do with it.&lt;/p&gt;
&lt;h3 id=&quot;nvidias-615-driver-and-long-sessions&quot;&gt;NVIDIA’s 615 driver and long sessions&lt;/h3&gt;
&lt;p&gt;NVIDIA’s 615 driver holds on to a little memory every time a program sends work to the graphics card. You notice it
when something runs for a long time, like a VR desktop.
&lt;a href=&quot;https://riftlinux.com/guide/troubleshooting/&quot;&gt;Troubleshooting&lt;/a&gt; has the workaround from NVIDIA’s forum.&lt;/p&gt;
&lt;h2 id=&quot;try-it&quot;&gt;Try it&lt;/h2&gt;
&lt;pre class=&quot;astro-code astro-code-themes github-light github-dark-dimmed&quot; style=&quot;background-color:#fff;color:#24292e;&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6F42C1;&quot;&gt;sudo&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; apt&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; install&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; ./riftlinux_0.1.5_amd64.deb&lt;/span&gt;&lt;span style=&quot;color:#6A737D;&quot;&gt;                  # Debian, Ubuntu, Linux Mint, Pop!_OS&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6F42C1;&quot;&gt;sudo&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; pacman&lt;/span&gt;&lt;span style=&quot;color:#005CC5;&quot;&gt; -U&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; riftlinux-0.1.5-1-x86_64.pkg.tar.zst&lt;/span&gt;&lt;span style=&quot;color:#6A737D;&quot;&gt;           # Arch, CachyOS, EndeavourOS, Manjaro&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6F42C1;&quot;&gt;sudo&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; dnf&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; install&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; ./riftlinux-0.1.5-1.x86_64.rpm&lt;/span&gt;&lt;span style=&quot;color:#6A737D;&quot;&gt;               # Fedora&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6F42C1;&quot;&gt;tar&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; xf&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; riftlinux-0.1.5-x86_64.tar.gz&lt;/span&gt;&lt;span style=&quot;color:#24292E;&quot;&gt; &amp;#x26;&amp;#x26; &lt;/span&gt;&lt;span style=&quot;color:#6F42C1;&quot;&gt;sudo&lt;/span&gt;&lt;span style=&quot;color:#032F62;&quot;&gt; ./riftlinux-0.1.5-x86_64/install.sh&lt;/span&gt;&lt;span style=&quot;color:#6A737D;&quot;&gt;   # any other distribution&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then restart Steam once.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Download: &lt;a href=&quot;https://github.com/AIIX/RiftLinux/releases/tag/v0.1.5&quot;&gt;RiftLinux 0.1.5&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Getting started: &lt;a href=&quot;https://riftlinux.com/guide/getting-started/&quot;&gt;riftlinux.com&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Source code and issues: &lt;a href=&quot;https://github.com/AIIX/RiftLinux&quot;&gt;github.com/AIIX/RiftLinux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Everything here was tested on NVIDIA. I don’t have AMD or Intel hardware, so if you try it on either, please let me
know how it goes. The logs people sent on issue #5 are what found the controller problem.&lt;/p&gt;</content>
    <category term="linux"/>
    <category term="vr"/>
    <category term="oculus-rift"/>
    <category term="steamvr"/>
    <category term="openxr"/>
    <category term="gaming"/>
    <category term="riftlinux"/>
    <category term="rift-home"/>
    <category term="open-source"/>
    <link rel="enclosure" href="https://aiix.space/images/blog/riftlinux/controller-fix-tracked.png" type="image/png" length="52587"/>
  </entry>
</feed>
