mirror of
https://gitlab.com/lvra/lvra.gitlab.io.git
synced 2024-11-14 20:30:25 +01:00
96 lines
No EOL
3.8 KiB
Markdown
96 lines
No EOL
3.8 KiB
Markdown
---
|
|
weight: 50
|
|
title: WiVRn
|
|
---
|
|
|
|
# WiVRn
|
|
|
|
- [WiVRn GitHub repository](https://github.com/WiVRn/WiVRn)
|
|
|
|
|
|
|
|
> WiVRn lets you run OpenXR applications on a computer and display them on a standalone headset.
|
|
|
|
It's very similar in purpose to [Monado](/docs/fossvr/monado/), but for standalone VR headsets.
|
|
|
|
Should you utilize [Envision](/docs/fossvr/envision/) for WiVRn setup, please ensure your APK and WiVRn server match as closely as possible. Check the WiVRn github [actions](https://github.com/WiVRn/WiVRn/actions) for an APK matching your server build to install to your headset.
|
|
|
|
## Wired WiVRn
|
|
|
|
Use WiVRn with a cable instead of Wifi. Use a 5Gbps cable & port at the very least.
|
|
|
|
WiVRn version: 0.19+
|
|
|
|
Using Envision:
|
|
- Connect the headset via USB
|
|
- Click the `Start WiVRn Client (Wired)` button in Envision.
|
|
- If it's not there, an Envision update might be necessary.
|
|
|
|
Manual steps:
|
|
- Connect the headset via USB
|
|
- 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:
|
|
```bash
|
|
adb reverse tcp:9757 tcp:9757
|
|
adb shell am start -a android.intent.action.VIEW -d "wivrn+tcp://127.0.0.1" org.meumeu.wivrn
|
|
```
|
|
|
|
## WiVRn + Lighthouse driver
|
|
|
|
This section covers using WiVRn with any lighthouse-tracked device: Index/Vive controllers, Vive/Tundra trackers, etc.
|
|
|
|
WiVRn version: 0.19+
|
|
|
|
Have SteamVR installed (no need to run it).
|
|
|
|
In Envision, set WiVRn Profile as such:
|
|
- XR Service CMake Flags:
|
|
- `WIVRN_FEATURE_STEAMVR_LIGHTHOUSE=ON`
|
|
- Environment Variables:
|
|
- `WIVRN_USE_STEAMVR_LH=1`
|
|
- `LH_DISCOVER_WAIT_MS=6000`
|
|
|
|
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`.
|
|
|
|
[Motoc](/docs/fossvr/motoc/) will be used 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!**
|
|
|
|
Once a device is discovered, it may be powered off and then back on later.
|
|
|
|
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:
|
|
- 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.
|
|
|
|
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).
|
|
|
|
## [Experimental] WiVRn + SlimeVR trackers
|
|
|
|
This section covers using WiVRn with SlimeVR trackers (not via OSC). Tracking fidelity is reported to be similar to what's achievable with the SteamVR-native solution.
|
|
|
|
Current state: Fully usable, but with quirks.
|
|
|
|
Use WiVRn APK version: 0.19.1 (exact)
|
|
|
|
In Envision, set WiVRn Profile as such:
|
|
- XR Service Repo:
|
|
- `https://github.com/galister/wivrn.git`
|
|
- XR Service Branch:
|
|
- `solarxr`
|
|
- XR Service CMake Flags:
|
|
- `WIVRN_FEATURE_SOLARXR=ON`
|
|
|
|
Perform a **Clean Build** after changing these!
|
|
|
|
- Always start SlimeVR server before starting WiVRn.
|
|
- Do not quit SlimeVR server mid-session; trackers will not work until WiVRn is restarted.
|
|
- _Full Reset_ is sensitive to direction.
|
|
- There is a direction that one needs to face towards for the full reset to work properly.
|
|
- It will take some trial and error to find this direction.
|
|
- Upstream issue: [SlimeVR-Server#1159](https://github.com/SlimeVR/SlimeVR-Server/issues/1159) |