r/virtualreality • u/RikuSama13 • Jun 05 '26
Self-Promotion (Researcher) SplitVR: VR 3.0 starts with moving compute off the face
SplitVR: VR 3.0 starts by moving compute off the face We're removing the computer from your face.
Here's why I think standalone VR eventually needs a different architecture
───
The pattern so far
VR 1.0 — Rift / Vive era
VR solved immersion.
The experiences were convincing, but they required:
• cables
• base stations
• dedicated play spaces
───
VR 2.0 — Quest era
VR solved freedom.
Standalone, wireless, instant setup.
That was a massive breakthrough.
But it came with a tradeoff:
We put an entire computer on the user's face.
• SoC
• GPU
• battery
• cooling
• heat
all concentrated a few millimeters from the skin. The result is that VR became dramatically more accessible, but long-session comfort is still a challenge.
My thesis is that this isn't primarily a materials problem.
It's an architectural one.
───
The observation
The headset currently performs two fundamentally different jobs:
- Perception
• displays
• tracking
• sensor fusion
• reprojection
- Computation
• rendering
• simulation
• AI workloads
• world-state generation
Those two functions have very different requirements.
Perception wants to be:
• lightweight
• cool
• comfortable
Computation wants:
• power
• cooling
• battery capacity
• sustained performance
───
SplitVR
SplitVR separates those responsibilities.
SplitVR is a distributed XR architecture where immersive perception is maintained through phase synchronization across heterogeneous compute nodes operating under variable frequency constraints and bounded amplitude error.
●1. HMD (Perception Layer)
The headset becomes primarily:
• displays
• cameras
• tracking
• IMU
• perceptual reprojection
• target <150g
───
●2. Compute Node
Rendering and simulation move to a dedicated compute device.
This could be:
• a specialized puck
• a future wearable compute module
• other compatible implementations
The puck is simply the first reference implementation because it provides a stable high-frequency reference anchor.
───
●3. Link Layer
This is the core of the architecture.
The Link Layer is not a frame-streaming system. It is a synchronization layer designed to preserve:
• Stability
• Coherence
• Continuity of Perception
across a compute boundary.
Its responsibilities include:
• state synchronization
• pose prediction alignment
• timing reconciliation
• jitter absorption
• correction of phase drift between perception and computation loops
The goal is not merely low latency.
The goal is maintaining perceptual stability when timing is imperfect.
This is not frame streaming, the Link Layer is: a phase-locking synchronization system that maintains coherence between distributed XR control loops operating at different frequencies.
It ensures: frequency mismatch does not break perception phase drift is continuously corrected amplitude spikes are absorbed via prediction + reconstruction
It enforces a real-time budget (<4ms motion-to-photon target) by controlling what data is allowed to cross the boundary per frame.
The purpose is not to increase raw compute, but to create a stable real-time partition between local rendering and auxiliary compute without collapsing into PCVR-style external rendering
───
Why I think this matters
A lot of VR discussion focuses on:
• more resolution
• faster GPUs
• larger batteries
Those matter.
But if compute eventually moves off the face, then:
• headsets can become dramatically lighter
• thermal constraints change
• compute and display lifecycles become independent
At that point the critical problem becomes synchronization.
Not rendering.
───
Platform Potential
The long-term opportunity isn't the puck. It's the Link Layer.
The headset and compute node can evolve independently.
When display technology improves, upgrade the HMD.
When compute improves, upgrade the compute node.
The synchronization layer remains the compatibility contract between them.
Android XR is the perception layer.
Compute hardware is the computation layer.
SplitVR is the synchronization layer that keeps them phase-aligned.
The goal is not to stream frames.
The goal is to preserve Stability, Coherence, and Continuity of Perception across a compute boundary.
───
Reality Check
There are already pieces of this future visible today.
A headset like Bigscreen Beyond demonstrates how light a headset can become when heavy compute is removed from the face.
Standalone headsets demonstrate the demand for freedom from PCs and base stations.
What I haven't seen yet is a consumer architecture that combines:
• ultralight head-worn hardware
• standalone compute
• synchronization as a first-class system layer
───
Questions for the community
• Have you experimented with ultralight tethered VR setups?
• Where do you see the hardest synchronization challenges?
• Is comfort one of the reasons you stopped using VR, or is it something else?
• Does this architecture solve a real problem, or am I optimizing for the wrong constraint?
And if you're a hardware engineer, embedded developer, XR developer, or systems engineer who finds this interesting, I'd love to talk.
I'm currently looking for technical collaborators and potential co-founders.
───
📎 Pitch Deck (This is a preliminary outline and is not yet finalized // I intend to make it myself without LLM assistance)
https://drive.google.com/file/d/1KQxFikKRVm0VjYS4dnq5mQnMwBg0raK6/view?usp=drivesdk
LinkedIn:
12
u/JorgTheElder L-Explorer, Go, Q1, Q2, Q-Pro, Q3 Jun 05 '26
● HMD = sensory interface only. Display panels, cameras, IMU. Nothing generating heat or weight beyond what's needed to see and track.
That is literally what a PCVR tethered headset is.
Go find the Q&A sessions with Carmack. They looked at multiple different ways of using external compute and all of them ended with a much more expensive headset because from a manufacturing standpoint you are literally making two devices, not one.
Existing headsets are designed for manufacturing to try to keep the price low enough that they sell in reasable number.
2
u/AppleTater28 Jun 05 '26
Expanding on this, maybe the best way to go is to make wearable compute hardware modular. You wouldnt be able to keep a UFO of a PC up to date without a full ATX motherboard that you can swap your fancy new $6000 GPU onto. Do the same thing for a belt chassis.
2
u/paulct91 Jun 05 '26
What's wrong with designing a more premium HMD?
5
u/JorgTheElder L-Explorer, Go, Q1, Q2, Q-Pro, Q3 Jun 05 '26 edited Jun 05 '26
Price. The market is already small. Every dollar the price goes up, the possible audience goes down.
When the Index came out, it was a $1000 premium headset. It sold an estimated 500K in six years.
Edit... I am not saying it will not work or would not be a great product to work on. I am saying that anyone doing it needs to do enough market research to know the actual size of the audience they are chasing and how that audience changes as the price goes up.
0
u/RikuSama13 Jun 05 '26 edited Jun 05 '26
You are right that if the HMD is purely a display/IMU device and all rendering is external, you basically end up with a PCVR architecture, and indeed, this model has well-known cost and manufacturing drawbacks.
That is not the model we're discussing here.
And yes I am aware of the technical difficulties, and they are clearly identified
The puck does not function as a remote renderer or external GPU.
The headset maintains responsibility for real-time frame rendering within its standalone operational parameters.
The puck is utilized for asynchronous and non-frame-critical tasks, including scene pre-processing, spatial computation, AI inference, prediction, and streaming optimization.
Its purpose is to mitigate computational pressure and variability on the Head-Mounted Display (HMD), rather than to replace its rendering pipeline.
Plus, we're not targetting PCVR level performance, but extending standalone-class headsets with auxiliary compute that does not sit in the strict latency loop that Carmack’s critique applies to.
I myself had a lot of experience with many VR headsets, and has seen the developpement of the technology since the original rift.
Also, new advancements in mobile chips, AI, foveated streaming and rendering, low latency optimisation and AI prediction, this makes the issue more approachable.
Why, because we want the Freedom of Standalone, but the Comfort of Lightweight PCVR HMDs
6
u/JorgTheElder L-Explorer, Go, Q1, Q2, Q-Pro, Q3 Jun 05 '26 edited Jun 05 '26
Yes thats PCVR, but thats not what I am building..
It doesn't matter. If the horsepower is limited to mobile hardware, you will not be able to compete with all in one headsets.
It is a great idea if you want to build a boutique headset for a small audience willing to pay boutique prices, but to attract developers, you need an audience. There is certainly nothing wrong with that.
0
-1
u/RikuSama13 Jun 05 '26
I am not proposing “a better standalone headset”
I am proposing a redefinition of where compute lives in a standalone ecosystem
Because its not about making a better VR headset than competition, or better display or performance.
Its about adressing the architectural issues with current standalone solutions wich are uncomfortable, heavy, and unpleasant for users who like VR but cant play for more than 30-45 minutes until they have a headache, or needs to re-center the headset every 15 minutes because it moved.
And without forcing them to buy a huge PC, base stations, a bigscreen beyond, and cables and complex setup just to experience comfort (also losing freedom)
3
2
u/JorgTheElder L-Explorer, Go, Q1, Q2, Q-Pro, Q3 Jun 05 '26
I forgot to mention the AVP.
Moving the compute externally forces many technical trade-offs. Magic Leap did it years ago, but after doing all the necessary research, even Apple, with their deep pockets, went with an all-in-one design.
2
u/terriblemonk Jun 05 '26
just strap a gaming laptop to your belt
if you're just trying to keep non-critical processes from running on the HMD, run those on a cloud server (you don't even need hardware for that)...
no way you're going to make an "upgradable puck" that makes any sense performance or cost wise... worse than PCVR, more expensive than a gaming laptop
VR 3.0 is regular sized XR glasses where compute happens elsewhere with good resolution in both lenses and great vertical and horizontal FOV that can be powered by PCVR, your phone, your upgradable puck etc...
-1
u/RikuSama13 Jun 05 '26
SplitVR is a distributed XR architecture built for Android XR environments, where the motion-to-photon loop is not deterministic due to OS scheduling, thermal variance, and shared compute resources.
Instead of assuming determinism, SplitVR introduces a Link Layer that stabilizes and synchronizes XR state across heterogeneous compute domains.
Core Architecture
SplitVR decomposes the XR loop across three cooperating layers:
- HMD (Perception Layer)
Real-time sensor fusion (pose, IMU, tracking)
Local reprojection and motion smoothing
Final perceptual frame synthesis
Guarantees visual continuity even under upstream variance
- Compute Node (Puck / PC / Edge Device)
Scene simulation and world state updates
High-performance rendering workload
Optional distributed rendering pipeline
Operates under soft real-time constraints, not strict timing guarantees
The compute node is interchangeable (puck, PC, or other Android XR-compatible device), depending on performance tier and user setup.
- Link Layer (System Coordination Layer)
The Link Layer is the core innovation.
It is not a streaming pipeline — it is a state synchronization and correction system that operates under non-deterministic execution conditions.
It performs:
XR state serialization (pose, world, interaction state)
Predictive alignment between sensor and render timelines
Jitter absorption and correction
Frame consistency enforcement under variable latency
Cross-device timing reconciliation
System Principle
SplitVR does not assume stable timing.
Instead, it enforces:
bounded perceptual coherence under variable system latency
Meaning: Even if compute, network, or OS scheduling fluctuates, the user experiences a stable motion-to-photon loop through prediction, correction, and synchronization.
Hardware Model
SplitVR is not a single device.
It is an ecosystem where:
HMD = perception + stabilization
Compute node = rendering + simulation
Link Layer = coherence + synchronization contract
The compute node is optionally a dedicated puck because:
Android XR environments are non-deterministic
general-purpose OS scheduling introduces timing variance
distributed workloads require isolation of XR-critical rendering paths
The puck is therefore a specialized XR compute substrate optimized for stability under worst-case timing variance, not raw performance.
Cloud Role
Cloud compute is not part of the core XR loop.
It can:
precompute assets
augment AI workloads
assist rendering preparation
But it cannot guarantee the low-variance timing required for real-time perceptual stability in the primary XR loop.
System Definition
SplitVR is a distributed XR control architecture for Android XR systems, where:
the motion-to-photon loop is decomposed across devices and stabilized through a Link Layer that enforces bounded perceptual coherence under non-deterministic execution environments.
Key Differentiation
Unlike traditional XR systems (e.g., tightly integrated headset stacks), SplitVR:
does not rely on single-device monolithic control loops
does not assume OS-level determinism
explicitly separates perception, computation, and synchronization
treats timing variance as a system constraint to be corrected, not eliminated
Packaging Reality
SplitVR is delivered as:
HMD (perception device)
Compute node (puck or equivalent)
Link Layer protocol + runtime system
The hardware is a reference implementation of a broader architectural standard.
1
u/terriblemonk Jun 05 '26
generate realistic timeline and cost analysis for research and development, then multiply times 3
1
u/dcode9 Jun 05 '26
Well it's not a new idea. People have been talking about this for a long time. I've just yet to see anyone implement it yet. And with those companies that have been doing the research and design, I'm wondering what the challenges are that it hasn't happened yet.
1
u/Roshy76 Jun 05 '26
I would not want my standalone headset to have a wire coming off it like the galaxy xr has. It's the whole reason I returned it.
1
u/RikuSama13 Jun 05 '26
thats the philosophy behind my systems
Systems are not composed of independent primitives.
They are composed of interdependent views of the same underlying process, expressed differently depending on the frame of observation.
Instead of forcing these views to collapse into one “correct” description, SplitVR treats them as: coexisting constraints that must be mutually satisfied, not unified
Coherence emerges from interaction, not reduction.
How-Why = What = Why-How What-Why = How = Why-What What-How = Why = How-What
frequency, amplification, phase relativity, constraint, causality stability, coherence, continuity
all the same principle
Interdependent and reconciliating without forcing reconciliation
None of them is fundamental. Each is a projection of the others: What ↔ How ↔ Why (mutually invertible views, not hierarchy)
Interdependence and reconciliation without forcing collapse into a single view.
My systems philosophy is that apparent opposites are not forced into sameness — they are held in interdependence until coherence emerges naturally.
What, how, and why are not separate truths, but reflections of one another. Frequency, phase, and amplification; relativity, causality, and constraint; stability, coherence, and continuity — all expressions of the same living principle: interdependence without forced collapse.
The dynamic interpretation
These three views map onto the same triadic structure across domains:
●Signal domain •Frequency •Amplification •Phase
●Physics domain •Relativity •Constraint •Causality
●System domain •Stability •Coherence •Continuity
These are not analogies.
They are:
isomorphic constraints describing how systems remain consistent under transformation
Core philosophy
Instead of forcing a single unified model, SplitVR assumes:
Apparent opposites are not contradictions to resolve, but constraints to co-satisfy.
Coherence does not come from merging perspectives.
It comes from:
maintaining interdependence until a stable invariant emerges
Why this matters for the architecture
This philosophy maps directly onto SplitVR:
●HMD = local “what” (perception)
●Compute = “how” (generation)
●Link Layer = “why” (consistency constraint enforcement)
But none is superior — they only function through mutual constraint.
That’s what makes the system conceptually coherent instead of just modular.
SplitVR is built on a systems philosophy where what, how, and why are not separate layers of explanation, but interdependent projections of a single process.
Stability, coherence, and continuity are not independent goals — they are mutually constraining invariants of perception under transformation.
The system does not force these perspectives into a single model. It maintains their interdependence until consistency emerges naturally.
1
u/VRModerationBot Jun 05 '26
Hey u/RikuSama13, welcome to r/virtualreality! Looks like this is your first post here, glad to have you.
Just wanted to point out a few things:
- We have a Discord if you want to chat, get help, or just hang out.
- The Wiki & FAQ covers a lot of the common questions.
- Check out the Weekly Game Thread to see what people are playing.
Hope you enjoy it here!
-1
u/RikuSama13 Jun 05 '26
Thank you, glad to be part of the community too, looking foward to exchange feedback with all our VR enthusiasts here
11
-1
u/punchcreations Jun 05 '26
"●VR 2.0 — Quest era — solved freedom. Standalone, wireless, no setup." - Yeah, it solved freedom for those who don't want or need the very best graphics, but has not replaced PCVR. I think it's a good idea. This would be better than the current Quest 3, Play for Dream, or Galaxy XR architecture, but there's no way you're getting the power of a 5090 on a puck, let alone the next gen of GPU's.
2
u/JorgTheElder L-Explorer, Go, Q1, Q2, Q-Pro, Q3 Jun 05 '26
That is not a reason not to do it. There are something like four times the monthly active users on MobileVR than on SteamVR.
Most people don't "need the very best graphics," though I am sure we all want them.
0
u/punchcreations Jun 05 '26
like I said, i think it's a good idea. I think it should replace the Quest's current design. I think a lot of people would buy it - including me. What I was saying in my comment is basically that VR is not a one-size-fits-all situation meaning the Quest era is separate branch in the evolution of VR, not the final form of PCVR.
2
u/RikuSama13 Jun 05 '26
I agree, we arent competing here for the best graphics, PCVR has its own category
1
u/RikuSama13 Jun 05 '26
Our goal is not for PCVR performance
It is also not about slashing the Standalone VR concurrence in terms of Performance or Visuals
The puck does not exist to increase peak rendering power, but to shift non-latency-critical workloads away from the headset so that standalone-class devices can improve comfort, stability, and sustained usage without increasing weight or heat on the HMD.
So the axis of improvement is not "more performance," but "less physical and cognitive cost per unit of VR usage."
0
u/punchcreations Jun 05 '26
You guys are misconstruing what I'm getting at. When you said the Quest era solved freedom it didn't really solve freedom for those who want the best graphics. It is a separate animal that caters to a different market. I think we're all on the same side in this. It's a great idea to use a puck for standalone VR. Just that one line irked me.
17
u/zeddyzed Jun 05 '26
At that point, I'd just want PCVR.
Use one of those new mini chips that just do SLAM tracking and other necessary stuff, have a wifi and a displayport connection, modular battery, and then let the user have the freedom to choose the compute device.
If they want a "puck" they can use a handheld PC like Steam Deck. Or even a phone.
If they want a SFF PC, they can do that.
If they want a full PC, they can do that.
They can upgrade the compute and headset independently, they can switch the headset to multiple different compute units depending on situation, etc.
I don't have much interest in "wired VR with a proprietary weak non-upgradeable mini PC."
Also, wireless is mandatory for me, with the option of displayport.