Uploaded April 2026 | Updated November 2026, 6 hours ago
Is Foveated Streaming finally the "killer app" for PC VR on the Apple Vision Pro? With the release of visionOS 26.4, we finally have access to low-level foveated streaming APIs that could change everything for high-fidelity gaming.
In this video, I’m running a head-to-head comparison in Kayak VR: Mirage. We’ll look at the current gold standard—ALVR (Standard Streaming)—and put it up against a New Beta Software (KRVR) that utilizes the native visionOS foveated rendering.
What’s the Difference?
Standard Streaming (ALVR): High-bitrate, foveated encoding. It looks good, but it pushes your network and hardware to the limit.
Foveated Streaming (visionOS 26.4): Uses eye-tracking to concentrate all the detail exactly where you’re looking. This allows for higher perceived resolution with less network strain.
Timestamps:
0:00 Intro
3:15 AVP View Getting into ALVR
4:06 ALVR Fixed Foveated Encoding Gameplay
6:34 KRVR Foveated Streaming Gameplay
7:21 Direct Comparison of Key Metrics
7:56 Closing Thoughts
8:55 Prologue (let me tell you about my app)
Untabbed for iOS: apps.apple.com/app/apple-store/id6760938655?pt=128686420&ct=himelstech&mt=8
Follow me on the socials:
instagram.com/himelstech
tiktok.com/@himeltech
https://x.com/himelstech
Hardware Used:
Apple Vision Pro M2 (visionOS 26.4)
Gaming PC:
AMD Ryzen 7 7800X3D (4.2GHz) Processor
Gigabyte B850 Gaming WiFi6 Motherboard
32GB DDR5-6000 RAM
NVIDIA GeForce RTX 5070
Router: Eero 6+, Gaming PC connected via ethernet
Resolution/Streaming Details:
ALVR:
Transcoding 3000x3200
Headset 3660x3200
Bitrate 200Mbps
KRVR (CloudXR): Uses two resolution numbers:
5200 = render resolution (unwarped). The game renders at this high resolution.
2080 = stream resolution (warped). The actual encoded/streamed resolution after foveated compression.
So effectively:
ALVR at 2864x2720: uniform quality everywhere, ~2.9K per eye
KRVR at 5200/2080: centre quality equivalent to ~5K, periphery compressed, streamed at ~2K
The center of your vision in KRVR is significantly sharper than ALVR because the foveation concentrates more pixels where you're actually looking. The total bandwidth is similar but the perceived quality is higher because of the eye-tracked redistribution.
CloudXR doesn't use a fixed bitrate like the SteamVR driver does (200Mbps CBR). It uses adaptive bitrate — the CloudXR runtime dynamically adjusts based on:
1. Network conditions — if packet loss increases, it drops bitrate to reduce congestion
2. Frame complexity — action scenes get more bits, static scenes get fewer
3. Foveation — the warped frame is already smaller (2080 wide), so the encoder naturally uses fewer bits for the compressed periphery
The actual bitrate varies frame-to-frame. CloudXR's encoder is VBR (variable bitrate) internally — it targets a quality level rather than a fixed bitrate number. The cloudxr-runtime.yaml doesn't have a bitrate setting because CloudXR manages it automatically.
The foveation is the big win — by warping the image before encoding, the periphery has fewer pixels which means fewer bits needed. The centre keeps full detail. So even at a lower total bitrate than ALVR at 200Mbps uniform, CloudXR delivers better perceived quality because the bits go where your eyes are.
Download KRVR Here: kross82.github.io/KRVR-releases
@KRVR_AVP
Is Foveated Streaming finally the "killer app" for PC VR on the Apple Vision Pro? With the release of visionOS 26.4, we finally have access to low-level foveated streaming APIs that could change everything for high-fidelity gaming.
In this video, I’m running a head-to-head comparison in Kayak VR: Mirage. We’ll look at the current gold standard—ALVR (Standard Streaming)—and put it up against a New Beta Software (KRVR) that utilizes the native visionOS foveated rendering.
What’s the Difference?
Standard Streaming (ALVR): High-bitrate, foveated encoding. It looks good, but it pushes your network and hardware to the limit.
Foveated Streaming (visionOS 26.4): Uses eye-tracking to concentrate all the detail exactly where you’re looking. This allows for higher perceived resolution with less network strain.
Timestamps:
0:00 Intro
3:15 AVP View Getting into ALVR
4:06 ALVR Fixed Foveated Encoding Gameplay
6:34 KRVR Foveated Streaming Gameplay
7:21 Direct Comparison of Key Metrics
7:56 Closing Thoughts
8:55 Prologue (let me tell you about my app)
Untabbed for iOS: apps.apple.com/app/apple-store/id6760938655?pt=128686420&ct=himelstech&mt=8
Follow me on the socials:
instagram.com/himelstech
tiktok.com/@himeltech
https://x.com/himelstech
Hardware Used:
Apple Vision Pro M2 (visionOS 26.4)
Gaming PC:
AMD Ryzen 7 7800X3D (4.2GHz) Processor
Gigabyte B850 Gaming WiFi6 Motherboard
32GB DDR5-6000 RAM
NVIDIA GeForce RTX 5070
Router: Eero 6+, Gaming PC connected via ethernet
Resolution/Streaming Details:
ALVR:
Transcoding 3000x3200
Headset 3660x3200
Bitrate 200Mbps
KRVR (CloudXR): Uses two resolution numbers:
5200 = render resolution (unwarped). The game renders at this high resolution.
2080 = stream resolution (warped). The actual encoded/streamed resolution after foveated compression.
So effectively:
ALVR at 2864x2720: uniform quality everywhere, ~2.9K per eye
KRVR at 5200/2080: centre quality equivalent to ~5K, periphery compressed, streamed at ~2K
The center of your vision in KRVR is significantly sharper than ALVR because the foveation concentrates more pixels where you're actually looking. The total bandwidth is similar but the perceived quality is higher because of the eye-tracked redistribution.
CloudXR doesn't use a fixed bitrate like the SteamVR driver does (200Mbps CBR). It uses adaptive bitrate — the CloudXR runtime dynamically adjusts based on:
1. Network conditions — if packet loss increases, it drops bitrate to reduce congestion
2. Frame complexity — action scenes get more bits, static scenes get fewer
3. Foveation — the warped frame is already smaller (2080 wide), so the encoder naturally uses fewer bits for the compressed periphery
The actual bitrate varies frame-to-frame. CloudXR's encoder is VBR (variable bitrate) internally — it targets a quality level rather than a fixed bitrate number. The cloudxr-runtime.yaml doesn't have a bitrate setting because CloudXR manages it automatically.
The foveation is the big win — by warping the image before encoding, the periphery has fewer pixels which means fewer bits needed. The centre keeps full detail. So even at a lower total bitrate than ALVR at 200Mbps uniform, CloudXR delivers better perceived quality because the bits go where your eyes are.
Download KRVR Here: kross82.github.io/KRVR-releases
@KRVR_AVP










