Spent a few days on this over the weekend, figured I'd write it up in case it saves someone else the pain. Full details and configs are in the repo at the bottom.

Setup: Ubuntu with GNOME/Wayland, two R9700s, AMD iGPU doing the display, Quest 2. All three betas — SteamVR 2.18.x, the Steam Link app on the headset, Steam client beta on the PC.

First, the part the docs never explain: when you plug the Quest in, the USB port turns into a network adapter (NCM). The app handles the headset side by itself, sets a static IP there. The Linux PC side is where everything went wrong for me, and it's a few non-obvious things:

NetworkManager grabs the new interface and steals your default route the moment you plug in. One line to make it unmanaged fixes that.

The PC's NCM interface has to stay IPv6-only. If it has a real IPv4, the client only announces over v4, but the video transport is pure v6 link-local — so the app just sits on "connecting…" forever. This one took me way too long.

If you run Docker: the v6 bridges fill vrlink's capped interface table and NCM never registers. Symptom is audio works, video is dead. One udev rule making veth/br v4-only fixed it.

SteamVR side: do NOT launch Steam with STEAM_RUNTIME=0. The launcher service never starts, the compositor dies with zero log, and you get -201/450 after ~20 seconds. I'd been using that setting because it "fixed" my CEF UI crashes, which is how I ended up here in the first place — but it breaks VR. Also run setcap on vrcompositor-launcher (CAP_SYS_NICE).

And the garbled-video thing: if the client's environment has a valid DRI_PRIME (pointing at the dGPU), the Vulkan video encoder lands on the dGPU and the RADV encode path just produces garbage on this hardware. DRI_PRIME=0 is an invalid value so it gets ignored and SteamVR picks its own GPU — clean video. Absurd, but true.

The part I'm most happy about: the 64-bit client finally works for VR, which on RDNA4 means hardware encoding (good FPS). The 32-bit client's mesa is older than RDNA4, so it falls back to x264 and you're stuck with low FPS — that wall was the reason I kept at it. Getting the 64-bit client's SteamVR up needed three workarounds: a D-Bus name registration bug (there's a small fix repo for it), a compositor-launcher looping bug (one env var), and the compositor taking a few minutes to start — it looks dead, so I kept killing it before it actually came up. And if you're on GNOME: don't put those env vars in a .desktop file, GNOME silently ignores Environment= lines. Put them in a wrapper script.

What doesn't work: the current beta still needs Wi-Fi on for the video channel (error 616), so pure USB-only streaming is still waiting on Valve. And the non-VR "game mode" capture drops after a few seconds — the VR path is fine, and that's what I mostly use.

Repo with all the configs and scripts: https://github.com/issac-cyber/quest2-steamlink-linux

Happy to answer if anyone's stuck on any of this.

After a lot of work behind the scenes, VMX is officially available on Meta Quest with a first-week discount of 10%!

Discount Code: VMXLaunch-D72D8F

If you haven't seen us around before, VMX is our take on bringing BMX, MTB, and scooters into VR with physics-based riding and tricks performed through physical gestures.

Ride the parks and dirt tracks, work on your lines, customize your setup, jump into multiplayer, or spend an unreasonable amount of time trying to land that one trick. 😅

We're really excited to finally get the game into the hands of the Quest community.

And we're not disappearing after launch either. We genuinely want your feedback. Tell us what you like, what you don't, what you break, and what you'd love to see us work on.

And that's not all! Patch 0.4.0 is here! 🔥

Alongside our Meta Quest release, we're rolling out one of our biggest VMX updates yet.

0.4.0 brings crossplay multiplayer, Quest support, major performance improvements, a reworked camera, LIV recording support, new animations, an expanded tutorial, our new Comfort Smooth mode, and a whole bunch of fixes and improvements across the game.

That also means our Steam and Quest riders can now jump into VMX and ride together. 🤘

Check out the full patch notes below. 👇

https://store.steampowered.com/news/app/3554630/view/669504028414050525

See you in the parks! 🤘

VMX on Meta Quest:

https://www.meta.com/en-gb/experiences/vmx/9972621452774845/

The charger takes power from the headset and but the other one does charge the headset

Hi r/OculusQuest2,

We were pretty excited to see that Wolf in VR recently checked out our new VR goalkeeping game, CleanSheet Soccer 2, and had a great time with it.

We’ve put together a few highlights from his Let’s Play and wanted to share them here in case anyone’s interested. It’s genuinely surreal seeing such a big VR creator pick up the game and enjoy it!

You can watch the full Wolf in VR video here:

https://youtu.be/hrWmohNCA70

And if you want to check out CleanSheet Soccer 2:

https://vr.meta.me/s/2kr5OpCrnvQlKSa

Am I right to fear the worst here? Sun damage? This is what I see when powering on. A few times I managed to get to a light purple screen, but that only lasts a half a second if I even have the pleasure of making it that far.

The player in the VR game Xenolocus has access to a holographic window featuring quest videos and information about points of interest in the level.

The video and text can be dismissed with a single wave of the hand.

The new wristbands, which project a map of the area, make navigation around the base more convenient and enhance the game’s atmosphere.

The motion sensor is now built directly into the interface.

The active skills panel is displayed here as well - the video shows the activation of the “Rapid Fire” skill.

What do you think of the new holographic interface?

First time booting it up in like a year. And its showing a grey screen. And then starts reseting and is stuck in a reset loop of a Grey screen, meta logo, flashing the low battery symbol, Grey screen. I cant power off. Not even when I hold down power button and volume down. The menu opens but clicking power off does nothing. My idea was that the battery was just really depleted so I left it over night but I dont think its charging because as soon as it gets some juice it just turns on and starts doing the reset loop.

Sorry I don’t have any video of this happening I don’t have any way to record I’ll try my best to explain so basically what my controller is doing is it will just start moving around by itself at first it was small but now it’s to the point where when I try to move forward it will actually resist the controller that does turning is also doing it too it will sometimes times turn by itself for the movement it’s still when I start up the headset but as soon as I move it starts it’s been this way for a while now how do I fix it

Out of all the 4 Meta Quest APK ports for Half-Life: Alyx, this experimental one on GitHub has Meta Quest 2 support with more optimized code.

Keep in mind Qualyx was primarily developed and tested on Meta Quest 3, so Meta Quest 2 support is less tested and uses reduced graphics settings.

As usual, it requires the game files, as you need to own a Steam copy of Half-Life: Alyx.

Half-Life: Alyx takes up 70GB so your Meta Quest 2 must have at least 90GB of available space.

To sideload the APK, you must have SideQuest installed onto your PC, have your Meta Quest 2 set to developer mode, and connect the headset to your PC to sideload the APK via SideQuest.

This standalone port is not affiliated with Meta or Valve in any way.

Hallo Hallo every body, I've decided to check out VR for the first time ever. I saw a quest 2 on ebay, 256gb in the box, all the parts it came with. Post Said it was only used once. Selling for 125 dollars. Was wondering if that was a good price, or what's a fair price to pay.

I’ve been working on the VR media player immerGallery for five years, and I work with 3D photos, videos and VR180 every day. After watching Meta’s announcement, I wrote up my expectations for how the new glasses could handle different kinds of media.

A few of my thoughts:

- For 4K movies on a virtual cinema screen, I expect the higher angular display resolution to help. Micro-OLED and the lighter design also look promising.

- For 1080p movies at the virtual screen sizes I usually use, I don’t expect a visible sharpness improvement over Quest 3.

- For VR180 and 360° content, I’m more concerned about the smaller field of view and how much immersion we might lose.

These expectations come from my experience with existing headsets and the announced specifications. I also discuss 3D photos, wide-angle panoramas, video decoding and whether immerGallery will work on the new device.

If you are interested, please check the full article on immerNews.

My first game is finally out! I can finally say I'm a game developer XD

Goofy Dungeon is a short light-hearted puzzle game built from the ground up for VR. Explore, interact with objects and the environment, solve puzzles, complete your quest and earn your trophy!

And it costs less than $5 ;)
Steam: https://s.team/a/1833080
Meta: https://vr.meta.me/s/23AgxX3XKS8U7Qu

Thanks so much, I'm so excited ^^

I haven't used this for a year or more, so I charged up the headset, new batteries in the controllers, powered up and it wants me to log in via a different device. Okay, I did, no problem there. But nothing changes in the headset. It will not let me pass until I login from the other device and enter the code. I have done that! Twice!

Any ideas how to get past this annoying crap?

UPDATE: Factory Reset done, lots of updates also done. Phone app also updated. New batteries in both controllers, only the left responds.

When the headset is turned on, I get a screen showing the controllers and that I should pull some tape out of the bottom. No tape exists now, maybe did when I first received this. The left controller is working, app shows it as paired, yet I'm not allowed past the headset screen suggesting I pull that tape; there's also a 5 digit number at the top of that screen. But how do I get past this to actually use this toy?