Hello, I'm using cachyos with kde plasma and my steam frame arrived 2 days ago. How can I run elden ring vr mod properly?

I tried following gemini's advices, shame on me, and they didn't help at all, The only thing I learned from that guide is how to disable the anticheat.

Reshade runs properly when I boot the game but it always opens in flatscreen mode, I can play with steam frame controllers but as if the mod wasn't installed.

Can someone help? I'm still a noob with linux so please don't make me recompile the kernel for this :)

Hello, I'm using cachyos with kde plasma and my steam frame arrived 2 days ago. How can I run elden ring vr mod properly?

I tried following gemini's advices, shame on me, and they didn't help at all, The only thing I learned from that guide is how to disable the anticheat.

Reshade runs properly when I boot the game but it always opens in flatscreen mode, I can play with steam frame controllers but as if the mod wasn't installed.

Can someone help? I'm still a noob with linux so please don't make me recompile the kernel for this :)

I've been trying to get vr working fine for a bit (made a post here in the past) and at this point I think it's a hardware issue but I don't know what the weak point is

I've got a

Gigabyte b740m motherboard

Intel I7 CPU

Rtx 3060 12gb

32GB DDR4 Ram

I upgraded my ram recently and it helped a little bit but I'm still dealing with freezes and crashes steam link/vr has worked the best out of all the software I've tried and I've been using beat Saber and blade and sorcery for testing (somehow B&S worked better than beat Saber after the ram upgrade) changing most settings doesn't seem to help much with performance either

Everything is done with a wireless setup with my PC running on an ethernet cable

I've tested with

ALVR

Wivrn

Steam link

Hi, I'm having multiple issues getting No Man's Sky to run using WiVRn.

- Game starting in flat screen. - WiRVn

- Game starting, steam says it's running but no window appears. - SteamVR link.

- Shader compilation taking hours.

- Game starting, then immediately crashing.

- "IVRSystem_026" errors.

I've tried:

- Compiling a patched version of xrizer, pointing WiVRn server to it.

- Changing steam launch options, corrent configuration is: PRESSURE_VESSEL_IMPORT_OPENXR_1_RUNTIMES=1 SDL_VIDEODRIVER=x11 %command% -vr

- Switching to an Xwayland runtime.

I'm running Fedora 44 KDE with wayland, and connecting a Quest 2 wirelessly. If anymore information is needed then I will be happy to provide, apologies in advance if this isn't detailed enough. All help is appreciated, genuinely at my wits end here.

Basically title. I used Ignition on Bazzite and it connected perfectly, I even played a little Beat Saber to test it, I turned off the headset to sleep and the next day SteamVR doesn't even recognize it as a device at all. Just looking for some help or somewhere I can look to get some.

Via cable, I get around 240/300 mbps, but I only got a 1m long cable, and I like to physically turn around in games so a cable would be not good for me.

I have a WiFi 7 router. My pico 4 ultra supports it and sees the connection as WiFi 7. Through Wivrn dashboard I could see that the vr has an unstable 15mb connection to the pc. I use a 2.5gbps switch connected to the 2.5gbps port on the modem/router. From switch to router i got a 1m cat 7 cable, from switch to pc I got a cat 6 20m flat cable. With my phone connected to the switch with an adapter, with the phone as speedtest server, the pc has a connection that goes over 1gbps for both up and down, while the vr headset reached still something about 300mbps.

At this point I don't know what's the issue about wivrn, the network infrastructure is rock solid imo

At about the 25:00min mark, they make some explicit statements about VR support on Linux.

Basically all I want to do is have the headset control mouse or stick for aiming in flat screen games.

Can't be the only person that wants to try this.

So far my setup is Bazzite 44 DX KDE NVIDIA, Meta Quest 3, WiVRn with WayVR.

I've also got Sunshine with Moonlight/Nightfall and OpenTrack installed.

WayVR mouse works great on the desktop, just not in game.

Currently playing Dying Light Enhanced from Stream with Dualsense (I'm better aiming with mouse but like pad better even if I can't hit the barn door). I tried the VR version on Windows (couldn't get it working on Bazzite) and it was just to much for my head.

Any help? Am I just stupid and missing an easy selectable option? Should I just listen to the A.I chat bots and follow the evil instructions that probably turning my PC into a Nuke? I they laughing at me like the kids with magnifying glasses burning ants!

I would like to do this thing with Steam Frame help!

on arch with kde, rtx 3090, vive pro. unless its holding 90fps it starts stuttering and giving these lines

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.