FuVR

Because Apple and Meta won't talk to each other, someone had to.

Want to do VR on a Mac with a Quest? Cool. Meta doesn't support macOS. Apple doesn't support Quest. SteamVR on Mac was abandoned in 2020. Quest Link doesn't exist for macOS. Nobody did anything about it.

FuVR does something about it: takes an Apple Silicon Mac, builds a custom OpenXR runtime on top of it, encodes frames with VideoToolbox, blasts them to the Quest over USB-C or Wi-Fi, and gets head pose and controller input back in real time. All from scratch. No reverse engineering. No SteamVR dependency. No permission asked.

It works. Tested with Blender VR. Pull requests welcome.

flowchart TB
    subgraph MAC["🖥️  Apple Silicon Mac"]
        direction LR
        APP["XR App\n(Blender / Godot / Unity)"]
        RT["OpenXR Runtime\ncustom dylib"]
        ENC["VideoToolbox\nHEVC / H.264"]
        DAEMON["fuvrd daemon\nCap'n Proto RPC"]
        TRANSPORT["Rust transport"]

        APP -- "xrEndFrame" --> RT
        RT -- "encoded frames" --> ENC
        ENC -- "Annex-B" --> DAEMON
        RT -- "pose + input" --> DAEMON
        DAEMON --> TRANSPORT
    end

    TRANSPORT -- "USB-C / Wi-Fi 6" --> RX

    subgraph QUEST["🥽  Meta Quest"]
        direction LR
        RX["Transport receiver"]
        DEC["MediaCodec\nHEVC decoder"]
        COMP["OpenXR compositor\n+ ATW"]
        POSE["Pose forwarder\n1 kHz"]

        RX --> DEC
        DEC --> COMP
        RX --> POSE
    end

    POSE -- "head + controller pose" --> DAEMON

    style MAC fill:#0d1117,stroke:#334155,color:#e2e8f0
    style QUEST fill:#0d1117,stroke:#1e40af,color:#e2e8f0

The hard part isn't the code — it's that Apple and Meta have had zero incentive to ever cooperate, so every piece of this stack exists despite them, not because of them.

Plug in your Quest over USB-C, then:

./test_pipline_blender.sh

That's it. The script kills any stale processes, reloads the daemon via launchd, re-does adb reverse, restarts the Quest app, launches Blender pointed at the FuVR runtime, and auto-toggles VR Scene Inspection on. Waits 18 seconds, prints a status report.

If you want to watch what's happening:

tail -f /tmp/fuvrd.err.log                        # daemon
tail -f /tmp/blender_vr_pipeline.log              # Blender
adb logcat -s fuvr.comp fuvr.proto fuvr.drift     # Quest

Nothing exotic, but you need all of it:

# Schema → bindings for all targets
./scripts/gen-proto.sh

# macOS components (runtime, encoder, daemon)
cmake -S . -B build -G Ninja
cmake --build build
ctest --test-dir build          # 11/11 should pass

# Rust transport layer
cargo build --manifest-path transport/Cargo.toml
cargo test --workspace

# SwiftUI app
swift build --package-path mac-app
swift test --package-path mac-app

# Quest app (requires Android SDK + NDK)
cd quest-app && ./gradlew assembleDebug

Full technical detail in SPEC.md.

The things that seemed obvious but weren't — full write-ups in docs/adr/:

Device dashboard — live RTT, FPS, encode time, and packet loss while streaming to Quest 3 over USB-C.

Encoder — pick HEVC, H.264, or AV1. Dial in bitrate and refresh rate. Quest 3 native resolution (2064×2208) pre-filled.	Transport — USB via ADB reverse or Wi-Fi. One-click adb reverse tcp:9943 so you don't have to think about it.
Session — HEVC 2064×2208 @ 90 Hz, 150 Mb/s. Daemon socket, connection state, one-tap reconnect.	About — v0.4, Apache 2.0. Setup wizard re-runs any time the Quest needs re-pairing.

Read CONTRIBUTING.md before opening a PR. The patent grant in the Apache 2.0 license is intentional and non-negotiable. By contributing you agree to the Apache ICLA.

Hardware test reports, results on different headset models, and ADR proposals are more useful than anything else right now.

Accurate depiction of trying to make Apple and Meta cooperate.

Designed and built by Sipioteo.

Apache 2.0 — see LICENSE.