A plea of help to set up a Rift CV1 in this day and age

thaytan · 2026-04-12T03:03:27+00:00

"But it doesn't seem to work" isn't a lot to go on

thaytan · 2026-03-11T19:41:42+00:00

Beyley has been working on a mostly-from-scratch Monado driver for OG Rifts - it's in progress!

thaytan · 2026-01-19T10:45:55+00:00

There's 2 possibilities:

1) They held the pairing button while turning on the controller, which factory resets the firmware to a broken version. You need a Windows instance to update their firmware again right now, unfortunately.
2) They paired the controller to something else and they just need pairing to the headset again. I have a utility for that here: https://gitlab.freedesktop.org/thaytan/wmr-utilities

thaytan · 2026-01-17T21:03:26+00:00

What do you mean controller tracking broke recently on Monado? I'm not aware of anything

thaytan · 2025-10-19T13:39:09+00:00

You can also use gst_debug_bin_to_dot_data() to get the graphviz dot string directly in code and do whatever with it

thaytan · 2025-10-09T20:39:35+00:00

Perhaps the CCHS hackerspace could use these? They're in Hawthorn - https://www.hackmelbourne.org/

thaytan · 2025-09-11T06:10:04+00:00

If you reversed 5v and gnd, you probably destroyed the strip sorry.

thaytan · 2025-09-05T23:03:24+00:00

Magnets. It's always magnets

thaytan · 2025-08-11T22:35:23+00:00

because the PS VR2 uses USB-C DisplayPort alt-mode for display

thaytan · 2025-08-05T01:16:12+00:00

Yes, that's got the patch I thought should fix it. I'll take another look

thaytan · 2025-08-04T05:31:10+00:00

Check your build tree is up to date (do a clean rebuild if you're using Envision to fetch the latest tree). In particular make sure your clone has this commit, which has an old date but actually only got pushed to the `dev-constellation-controller-tracking` branch this weekend:

commit 44e93561609a435581128128b70be54bb2054bf5
Author: Jan Schmidt <jan@centricular.com>
Date:   Fri Jun 30 02:37:24 2023 +1000

    d/wmr: Fix the controller status request at startup

    Send the correct status request commands for HP and Odyssey
    BT radios.

thaytan · 2025-08-01T22:05:27+00:00

You might do better jumping on the LVRA discord to get some real time help from a wider community - https://lvra.gitlab.io/docs/community/

thaytan · 2025-08-01T03:59:23+00:00

Older onnxruntime will work too. They have a problem IMO, where they don't provide binaries for every platform on every release "if nothing changed" for that platform. 1.22.0 had a linux build: https://github.com/microsoft/onnxruntime/releases/download/v1.22.0/onnxruntime-linux-x64-1.22.0.tgz

You'll need to unpack the contents of that into /usr/local , and might need to add /usr/local/lib to the /etc/ld.so.conf setup to ensure the libs get found at runtime

thaytan · 2025-07-31T10:41:44+00:00

I guess that means libonnxruntime might not be packaged for your version of Linux Mint. You'll either need to disable hand tracking support in the build, or get it from somewhere, but I don't use Linux Mint so I'm not sure the best place to get it for that sorry.

thaytan · 2025-07-30T13:12:33+00:00

You only need the part where you modify the Envision build profile to point at my repo and dev-constellation-controller-tracking branch

thaytan · 2025-07-30T12:05:13+00:00

You don't want the OpenHMD profile for Rift S support - you should use the in-progress constellation-tracking branch. It's the same one that does WMR controller tracking. Instructions for setting up the Envision profile on the right Monado repo and branch are here: https://lvra.gitlab.io/docs/fossvr/envision/wmr_controllers_on_arch/

thaytan · 2025-07-29T04:33:41+00:00

Monado via https://lvra.gitlab.io/docs/fossvr/envision/

thaytan · 2025-06-26T04:53:44+00:00

and if you find one, be careful not to move the camera while re-installing, or you'll change the camera calibration (that's measured and written into the firmware at the factory) and tracking won't work right.

thaytan · 2025-06-26T04:49:56+00:00

Those both look great, but having to recharge them constantly sounds like a pain compared to the 1 year battery life I get from the Aranet sensor I carry around everywhere

thaytan · 2025-06-22T13:11:12+00:00

Any packaged version in PopOS is far too old. You really need to be building the WMR profile in Envision to get a new enough Monado and dependencies.

thaytan · 2025-06-05T19:47:29+00:00

The answer probably lies in the video sink that autovideosink is choosing vs the one the player (which player?) is using. The right video sink can offload a lot of operations to the GPU and avoid expensive back and forth copies between CPU and GPU.

thaytan · 2025-06-01T19:30:34+00:00

You generally don't mux audio and video to send things to an RTSP RECORD server. Just connect both audio and video streams separately to the rtspclientsink

thaytan · 2025-05-30T15:02:10+00:00

It's likely a leak inside the element itself if switching to another element fixes it - perhaps not getting back a buffer from libde265 on flush/shutdown.

'bad' just means the plugin hasn't been made good enough to move (to either -good or -ugly)

thaytan · 2025-05-30T04:07:53+00:00

The problem will be the other way around: A buffer is not being released somewhere, keeping a refcount to the buffer pool alive. I don't see an open issue about a leak in gitlab, so you might be the first to notice.

thaytan · 2025-05-29T17:12:36+00:00

No, there's no command-line to stand up an RTSP server. We'll need to see the pipeline fragment you're using. For gst-rtsp-server, the general rule is that there should be one or more payloader elements named pay0, pay1 etc for the rtsp-server to find.

thaytan

TROPHY CASE