134
Wireless VR streaming levels up on Linux with the latest WiVRn release (www.gamingonlinux.com)
submitted 9 months ago by to c/linux_gaming@lemmy.world
6 comments fedilink hide all child comments

all 6 comments

sorted by: hot top controversial new old
[–] 17 points 9 months ago (5 children)

Nice to see WiVRn getting even better. This software is basically the only good way to stream VR on Linux.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 3 points 9 months ago (4 children)

    I’ve only tried ALVR, but last time I tried it, it was janky. Is WiVRn better?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 7 points 9 months ago (2 children)

    I've been fiddling around with ALVR for two weeks now and couldn't get it to run decent at all, with or without a cable. I'm running a Ryzen 9, 7800XT, and 64GB ram.

    I tried WiVRn yesterday and it just works. I've tested Moss, AC Evo, Competizione, Beat Saber, Dirt Rally 2.0, HL: Alyx, Air Car, all of them run smooth as butter on 150%, 120hz. Except for AC Evo, but that game is still in early access so probably not quite optimized yet.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 9 months ago (1 child)

    I’ll have to give it a go then, thanks!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 8 months ago

    Just make sure you use XRizer instead of OpenComposite for OpenVR compatibility as it's much more advanced at this point. You can also use OpenComposite as a secondary if a particular game doesn't work with XRizer.

    For clarity, OpenVR is the historical standard for VR which is still used by some modern games, although more are supporting OpenXR, which WiVRN handles directly.

    See also this compatibility list and the Linux VR Adventures wiki.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 9 months ago*

    WiVRn is so stupid easy to use. You just copy the launch command from the app into the Steam launch options and hit run. It just works. Other than occasional hiccups, it's the most stable and simple VR application for Linux I've used.

    There is also a companion app that doesn't require installing outside the Meta Quest store (although loading via APK is an option). As long as your headset runs Android, it should just work. The headset app lets you launch games directly from the headset, too.

    SteamVR also works fine if you're on Wayland and KDE. There is a SteamVR app for Quest and other Android-based headsets that works with the native SteamVR application.

  • permalink
  • fedilink
  • source
  • parent
    • 2 comments in c/linux@programming.dev view that post
    [–] 5 points 9 months ago (1 child)

    Anybody know how it compares to ALVR?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] 10 points 9 months ago* (last edited 9 months ago)

    Biggest difference is probably that ALVR works on top of SteamVR while WiVRn uses opencomposite/xrizer/vapor instead. SteamVR seems to be somewhat broken and buggy on Linux atm and just having to not use it can be a plus depending on the game. In theory this should also result in some performance gains in certain titles.

    ALVR is easier to "install" but then completly overwhelms you with its settings. WiVRn is way cleaner in regards to the user facing settings. Most of the important settings are even done within the headset .apk which is a nice QOL improvement. Installation on CachyOS took a lot more time until i figured it out though. Getting the WiVRn-server, wivrn-dashboard, lib32-wivrn, xrizer, lib32-xrizer, opencomposite etc of the AUR. That lib32 stuff is needed for certain titles like the HL2 VR mod.

    Imagequality is more or less the same. Latency is maybe a bit better on WiVRn but hard to tell between different programs. Pico Connect, Virtual Desktop, ALVR, WiVRn all provide wildly different latency readouts in my experience. 60ms seems to be the best case i can achieve with my current setup with WiVRn which feels similar to 35ms in Pico Connect or 40-50ms in VD. But WiVRn sometimes just gives me 15-30ms more latency for whatever reason. Then i need to restart the server, the app, my whole pc until it just works again as expected. In some games i just get constantly 100ms but still feel just fine. In other games 80ms feels horrible until it gets back down to 70ish ms.

    In general the WiVRN/Xrizer/lib32 combo is so far the most reliable in my case. Got almost every game working with it(Hitman VR, SW Squadrons Epic Store Version and Race Room Racing Experience are the only duds so far). ALVR/SteamVR shits the bed way more often by not picking up a VR title. Steam Link just doesnt want to establish a VR connection at all on my setup for whatever reason.

    On most days i'm pretty happy with the current state of VR on Linux. On others i ask myself if it wouldnt be quicker to just spin up a dualbooted Win LTSC install instead of troubleshooting for 2-3 hours again.

    Edit:
    https://lvra.gitlab.io/
    https://db.vronlinux.org/

    Also i forgot to mention wayVR which is awesome in combination with WiVRn. Its not perfect but i think i like it even more than VD for in VR desktop use. Atleast when everything works which it does most of the times until it doesnt.

  • permalink
  • fedilink
  • source
  • parent