Launching with wivrn://address will directly connect to given address, bypassing mDNS service discovery
WiVRn
OpenXR streaming application
WiVRn lets you run OpenXR applications on a computer and display them on a standalone headset.
Installation
Server (PC)
Dependencies
WiVRn requires ffmpeg (for AMD/Intel), cuda (Nvidia), x264 (software) for video encoding. Other dependencies include avahi-client, eigen3, libpulse, nlohmann_json.
Note that some distributions don't ship h264/h265 support in their mesa builds. On Fedora this can be solved by replacing mesa:
dnf swap mesa-va-drivers mesa-va-drivers-freeworld
Compilation
From your checkout directory
cmake -B build-server . -GNinja -DWIVRN_BUILD_CLIENT=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo
cmake --build build-server
# Set WiVRn as the active OpenXR runtime, delete ~/.config/openxr/1/active_runtime.json after you are done using WiVRn
mkdir -p ~/.config/openxr/1/
ln --relative --symbolic --force build-server/openxr_wivrn-dev.json ~/.config/openxr/1/active_runtime.json
Client (headset)
At this early stage of development, we do not have stable releases. Download apk from Releases. Install with adb (headset connected to PC), developer mode must be activated on Quest.
adb install WiVRn.apk
Usage
On the computer, run wivrn-server, from checkout directory
build-server/server/wivrn-server
Then, on headset, launch WiVRn from the App Library, in "unknown sources" section.
You will briefly have a "Waiting for connection" screen, followed by "Waiting for video stream". Now on your computer you can run an OpenXR application, and it will show on your headset, enjoy!
TODO
- Sound support (recording)
- Improve sound playback latency
- SteamVR support with OpenComposite
- Latency improvement
- Application launcher
- Support more headsets
Credits
WiVRn uses the following software: