Jasima/lvra.gitlab.io
1
0
Fork 0
mirror of https://gitlab.com/lvra/lvra.gitlab.io.git synced 2025-02-22 18:43:58 +01:00
Code Issues Projects Releases Packages Wiki Activity

WiVRn: Add Steam Flatpak instructions

Browse source 
Co-authored-by: Tabitha Moon <123581598+tabithamoon@users.noreply.github.com>
This commit is contained in:
hypevhs 2025-02-13 15:08:10 -06:00
parent 4042104f3b
commit 606910ecc6
1 changed files with 29 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
content/docs/fossvr/wivrn/_index.md
View file

@ -17,7 +17,7 @@ WiVRn is based on [Monado](/docs/fossvr/monado/) and can be used with [OpenCompo
We recommend using [Envision](/docs/fossvr/envision/) to install and launch WiVRn & OpenComposite. Envision will handle all configuration seamlessly and avoids many of the pitfalls of a manual setup. We recommend using [Envision](/docs/fossvr/envision/) to install and launch WiVRn & OpenComposite. Envision will handle all configuration seamlessly and avoids many of the pitfalls of a manual setup.
Alternatively, you can use the [WiVRn Flatpak](https://flathub.org/apps/io.github.wivrn.wivrn) which includes OpenComposite as part of it. Processes in flatpak cannot take advantage of setcap, and so your performance may suffer when compared to Envision. Alternatively, you can use the [WiVRn Flatpak](https://flathub.org/apps/io.github.wivrn.wivrn) which includes OpenComposite as part of it. Processes in Flatpak cannot take advantage of setcap, and so your performance may suffer when compared to Envision.
## General WiVRn Notes ## General WiVRn Notes
@ -33,19 +33,34 @@ If using Nvidia proprietary drivers, have [Monado Vulkan Layers](https://gitlab.
For audio in WiVRn, you will need to assign applications, or the system as a whole, to output audio to the virtual output "WiVRn" which is created upon connection between the server and the headset. For audio in WiVRn, you will need to assign applications, or the system as a whole, to output audio to the virtual output "WiVRn" which is created upon connection between the server and the headset.
It is possible to use WiVRn Flatpak with Steam Flatpak, though Steam Flatpak isn't generally recommended for VR. If you are using Steam Flatpak, you just need to grant it access to the relevant paths:
```bash
flatpak override --user --filesystem=xdg-config/openxr:ro com.valvesoftware.Steam
flatpak override --user --filesystem=xdg-config/openvr:ro com.valvesoftware.Steam
flatpak override --user --filesystem=xdg-run/wivrn com.valvesoftware.Steam
flatpak override --user --filesystem=/var/lib/flatpak/app/io.github.wivrn.wivrn:ro com.valvesoftware.Steam
```
As an added bonus to the above, this command will save you the effort of having to set launch options for every single VR game in your Steam library:
```bash
flatpak override --user --env=PRESSURE_VESSEL_FILESYSTEMS_RW=/run/user/1000/wivrn/comp_ipc:/var/lib/flatpak/app/io.github.wivrn.wivrn com.valvesoftware.Steam
```
## Wired WiVRn ## Wired WiVRn
Use WiVRn with a cable instead of Wifi. Use a 5Gbps cable & port at the very least. You can use WiVRn with a cable instead of Wi-Fi. Use a 5Gbps cable & port at the very least.
WiVRn version: 0.19+ WiVRn version: 0.19+
Using Envision: Using Envision:
- Connect the headset via USB - Connect the headset via USB.
- Click the `Start WiVRn Client (Wired)` button in Envision. - In Envision, click the `Start WiVRn Client (Wired)` button.
- If it's not there, an Envision update might be necessary. - If it's not there, you may need to update Envision.
Manual steps: Manual steps:
- Connect the headset via USB - Connect the headset via USB.
- If WiVRn is running on the headset, close it now. - If WiVRn is running on the headset, close it now.
- While in the system lobby of the headset, run the following `adb` commands on the PC: - While in the system lobby of the headset, run the following `adb` commands on the PC:
```bash ```bash
@ -55,11 +70,11 @@ Manual steps:
## WiVRn + Lighthouse driver ## WiVRn + Lighthouse driver
This section covers using WiVRn with any lighthouse-tracked device: Index/Vive controllers, Vive/Tundra trackers, etc. This section covers using WiVRn with any Lighthouse-tracked device: Index/Vive controllers, Vive/Tundra trackers, etc.
WiVRn version: 0.19+ WiVRn version: 0.19+
Have SteamVR installed (no need to run it). You must have SteamVR installed (no need to run it).
In Envision, set WiVRn Profile as such: In Envision, set WiVRn Profile as such:
- XR Service CMake Flags: - XR Service CMake Flags:
@ -70,20 +85,20 @@ In Envision, set WiVRn Profile as such:
Perform a **Clean Build** after changing the CMake flags! Perform a **Clean Build** after changing the CMake flags!
If not using Envision, simply pass `-DWIVRN_FEATURE_STEAMVR_LIGHTHOUSE=ON` to cmake and export the env variables before starting `wivrn-server`. If not using Envision, simply pass `-DWIVRN_FEATURE_STEAMVR_LIGHTHOUSE=ON` to CMake and export the above environment variables before starting `wivrn-server`.
[Motoc](/docs/fossvr/motoc/) will be used to calibrate the two tracking technologies to work together. You can use [Motoc](/docs/fossvr/motoc/) to calibrate the two tracking technologies to work together.
Discovery happens only on first connection, so be sure to **have all lighthouse devices powered on and in line of sight of base stations before connecting the headset!** Discovery happens only on first connection, so be sure to **have all Lighthouse devices powered on and in line-of-sight of your base stations before connecting the headset!**
Once a device is discovered, it may be powered off and then back on later. Once a device is discovered, you may power it off and on at-will.
Once video appears in the headset, check `motoc monitor` to make sure your devices all show up. Once video appears in the headset, check `motoc monitor` to make sure your devices all show up.
If one or more devices are missing, try: If one or more devices are missing, try:
- Spread the devices out more; lighthouse devices get discovered quicker if they're not piled up on each other. Simply strapping them on is good, too. - Spread the devices out more; Lighthouse devices get discovered quicker if they're not piled up on each other. Simply strapping them on is good, too.
- Increase `LH_DISCOVER_WAIT_MS`, though this delays the client on first connection. - Increase `LH_DISCOVER_WAIT_MS`, though this delays the client on first connection.
To re-discover devices, restart WiVRn server. To re-discover devices, restart WiVRn server.
At this point, your lighthouse devices will be randomly floating about somewhere. To calibrate them, follow the guide in the [Motoc README](https://github.com/galister/motoc/blob/main/README.md). At this point, your Lighthouse devices will be randomly floating about somewhere. To calibrate them, follow the guide in the [Motoc README](https://github.com/galister/motoc/blob/main/README.md).