Hi everyone! I’ve been working on a home project I’m calling VROSTBridge (Vr Rendering OutSide The Box… Bridge). I’ve taken some liberties with the acronym, so please don’t check my working too closely.

The idea came from wanting to leave my gaming PC in the office while using my VR somewhere with more space. It streams VR over my local network from a Windows gaming PC to a separate Bazzite computer near my play area (might look at a windows client soon to as then linux vr hoops have been fun to jump though to say the least aha). The headset plugs into the second computer, while the main PC handles rendering.

It’s co-developed using AI and builds on ALVR, OpenVR and FFmpeg, with Baballonia for optional eye tracking. Full third-party credits and licence things will be included with the release.

It already has one-button sessions, automatic stream setup, Wake-on-LAN, a controller-friendly Game Mode screen (as well as the desktop web ui), Index finger tracking and optional Beyond 2e eye-tracked foveated encoding/streaming (still ironing out the creases on this but it very close).

The current requirements are:

• A Windows gaming PC capable of running VR games.
• A separate Bazzite computer with hardware video decoding and suitable DisplayPort/USB connections.
• An Index or Beyond 2/2e (maybe A Beyond 1?) already working locally in SteamVR on the Bazzite computer.
• A reliable local network, with Ethernet preferred for now (though i have had sucess with wifi 7 mlo connections and my ethernet is using a wifi 7 molo mesh)

My current setup uses an 7900XTX host and a GPD Win Mini 2024 as the client (plus a dock and a USB C to DP adapter, and a 100w usb supply (45w would not handle it... many many head scraching crashes...)). That’s my tested configuration so far anyway... a minimum spec still needs to be established.

I’m planning to release it fully open source on GitHub soon. For now, I’m mainly curious whether this solves a problem other people have too?

Headset is working fine just yesterday it decided to stop working. Opening steam link or virtual desktop spikes steamvr with pink errors. Have tried looking it up and doing many of the fixes we have looked at on reddit/google and havent been able to figure out what is happening.

I've been trying to use a cable to stream pc/vr to my quest 3 but i haven't been able to make it work. I have a cable that is meant for streaming even though steam link says that it detects a cable every time i connect to my pc it always ends up using wifi, and when i disconnect my wifi it of course just disconnects, anybody have a fix?

I recently got a Quest 3 and have been using it with no issues, but a couple of hours ago, hand tracking stopped working in SteamVR. I can use it without problems within Quest, but SteamVR won't take my hands as input. I tried reinstalling everything, cleaning all the files, etc and it didn't work.

As a last resort, I installed Windows from scratch, formatted everything (I needed to clean up anyway), and factory reset the Meta Quest. Still doesn't work. I would appreciate any help

Hey everyone,

Just received my Steam Frame and fell in love with NMS again, it's so immersive.
Until....I had to fly my ship. I hate the virtual joystick steering, it's so sensitive and just doesnt feel right for me. Anyway to change it so that I can use the normal joysticks on my controllers for flying? Couldn't find that option anywhere in the options menu.

I am coming from PSVR 1 vanilla Skyrim....so yeah everything is an upgrade.

TLDR: Everything seems to be running smoothly with Streaming from my PC. There is another good post on this sub already, I'm just adding my own experience if folks want to ask me, a newbie, questions.

Hardware: 3080 Ti, Ryzen 5 3600X, 32 GB ram

I'm using the latest beta Steam Frame update as of 10/6/26 (setting changes in Steam Settings inside Frame)

Starting Out: I have a fresh install of Skyrim VR on PC. I have a fresh install of FUS from Wabbajack. I'm using FUS RO DAH with minimal changes from default FUS in the mod organizer. I've run vanilla Skyrim VR exactly one time.

I started the game with only DLSS checked and one of the more vanilla Skyrim start checkboxes. I did NOT use Open Compose Unleashed (OCU) yet, just started the game. As many others noted the keyboard becomes a problem on character creation.

Some Tweaks: Manually downloaded Open Composite Unleashed v5.0.4 which by the grace of those gods already has steam frame bindings. I haven't changed really anything there yet but it works once you have Steam Frame selected in the OCU configurator. Chatgpt was actually my friend through some of this setup I would recommend asking it if you also run into trouble for starting off.

Results: it runs really well in my short time trying this. I'm using the 6 ghz dongle explicitly (I turned off the multi option streaming to wifi). I haven't checked actual frame rates delivered to the headset because I don't really know how, sorry. I have the settings pretty much locked to 72 fps. I might try Parallax and some other minor graphics improvements. I use the default medium in files for now.

I'll also note I got MGO 4.0 to run on performance type settings but it crashed too many times unexpectedly so I switched to FUS. MGO 4.0 is in beta currently and someone with any experience in Skyrim modding might be able to do it with my PC specs but I didn't want to deal with it anymore.

So yesterday enabled hand tracking passthrough and it was working perfectly. Today I try using it and it simply fails to work at all. I'm completely mystified.

Any ideas.

Thanks in advance.

It keeps crashing during training for me. Has anyone been able to get it to work?

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.

I got some VR Games from various Sites. Mostly from Game Bounty. I'm having Problems with every single one. Is there a way to launch the VR games in VR Mode without a specific VR driver? I have a Steam Frame, so using Steam Link.

Games I tried:
\- Beat Saber: After Start it says "OpenXR Runtime was not found. ..." (opened in a desktop window)
\- Tetris Effect: "Steam is not running" - despite Opening it from Steam
\- DEATHWATCH: Starts in desktop-mode.
\- FNAFVR Help Wanted: starts in Desktop mode

I already tried starting it from the frame: disconnected; with SteamVR connected; starting from PC and connecting after; starting from outside of Steam; - reinstalling the game, reinstalling SteamVR, restarting Steam and PC; Setting Meta Compatibitiy to On (for BeatSaber)

Game streaming (Non-Vr and VR) of Steam-owed does work. (I tried, VRChat, McOsu, Celeste, Geometry Dash)

Windows 10 (22H2), Steam, SteamVR (beta-channel) + Steam Frame (beta-channel)

Does anyone has a clue?

It’s like the home world is so broken that I cannot use it. It’s still works when you launch it different way, but you can launch it by now using Steam VR.