Lesson 2.1 · The Technology
How It Works: Tracking & Display
How a headset holds an entire computed room perfectly still around your moving head - by knowing exactly where you are and redrawing the whole world dozens of times a second before you notice the lag
Put on a headset and a room appears that stays perfectly still as you walk through it. That stillness is an illusion the machine rebuilds dozens of times a second - and understanding how is the difference between using the tool well and being fooled by it.
The first time you put on a good headset, the striking thing is not the graphics - it is the stillness. You turn your head and the computed room stays exactly where it was, as solidly anchored as the real room you just left. You crouch and the ceiling rises above you; you step forward and the far wall comes closer at the right rate. Nothing wobbles, nothing lags, nothing swims. It feels less like watching a screen and more like the digital world simply *being there* around you. That felt solidity is the whole point of spatial computing, and it is completely manufactured.
Behind that calm illusion, two machines are running flat out and in step. One machine is constantly answering the question 'where is your head, and which way is it pointing, right now?' - this is positional tracking. The other machine takes that answer and draws the two images your two eyes should see from exactly that viewpoint, then throws them onto the displays and does it all again a fraction of a second later - this is display. Get both right and the world holds still and solid. Get either wrong - tracking that drifts, images that arrive late - and the spell breaks, often unpleasantly. This lesson opens the machine and shows you, at the level of principle rather than spec sheet, how tracking and display conspire to put a stable, three-dimensional world in front of your eyes.
Sense (track) -> render two eyes -> display -> repeat, ~90x a second. Low latency + high frame rate = comfort. A convincing reconstruction from estimates - never a ruler.
Positional tracking - how the device knows where you are
For the computed world to stay anchored, the device must know, continuously and precisely, where your head is in space and which way it is facing. Engineers describe this as tracking six degrees of freedom (6DoF): three for position (moving left-right, up-down, forward-back) and three for rotation (tilting your head, turning it, nodding it). A device that tracks only rotation - you can look around but not walk - is 3DoF, and it feels flat and disappointing by comparison, because your body expects the world to respond when you lean and step, not only when you turn.
Modern headsets achieve 6DoF with inside-out tracking: small cameras and sensors mounted on the headset itself look outward at the surrounding room. Frame by frame, the software picks out stable visual features - the corner of a window, the edge of a table, the texture of a wall - and watches how they shift between frames as you move. From that flow of features it computes how the headset must have moved to produce that shift. Because it is simultaneously building a rough map of those feature points *and* working out its own position within that map, this technique is called SLAM (simultaneous localization and mapping). Fast motion sensors (accelerometers and gyroscopes) fill in the gaps between camera frames, so the estimate stays smooth. The older alternative, outside-in tracking, placed sensors or beacons on the walls and had them watch the headset; inside-out won because it needs no room setup - you put the device on anywhere and it finds itself.
The same machinery, pointed at your hands, tracks them too: cameras recognise the shape and joints of your fingers, or watch the lights on hand-held controllers. This is what lets you reach out and the virtual object be exactly where your hand is.
It is worth being honest about the limits from the start. Tracking is an estimate, not a measurement. In a blank white room, a dark room, or one full of moving people or reflective glass, the features get scarce or unstable and the tracking can drift or jump. Good hardware hides this well, but the world it shows you is a confident reconstruction of where things are - never a survey. Read a dimension off it and you are trusting an illusion; binding measurement stays with instruments and drawings.
Cameras on the headset watch room features -> software works out how the head must have moved -> your viewpoint, 6DoF, updated. Blank/dark rooms starve the features and it drifts.
Stereoscopic, perspective-correct display - drawing what each eye should see
Knowing where your head is only matters because of what the device does with that knowledge: it draws the world from your exact viewpoint and shows it to your eyes so convincingly that they read it as solid space. The foundation is stereoscopy. Your two eyes sit a few centimetres apart, so in real life each sees the world from a slightly different angle; your brain fuses the two views and extracts depth from the differences. A headset reproduces this by rendering two separate images, one computed for the position of your left eye and one for your right, and presenting each to the correct eye through a lens. The brain does what it always does and fuses them into a single scene with genuine depth - objects that feel near are near, far walls feel far.
Stereo alone is not enough; the images must be perspective-correct and constantly updated. As your head moves even slightly, the correct view changes: nearer objects shift across your field of view faster than distant ones - the everyday cue called motion parallax. So the device does not draw one fixed picture; it redraws both eye images for your new head position on every single frame. Because the tracking machine is feeding it your live pose, the drawn world moves exactly as a real scene would, which is precisely why it stays anchored: lean left and you see a little more around the near column, exactly as you would in the real room.
The lenses matter as much as the pixels. They sit close to your eyes and magnify small, dense displays to fill much of your vision, and let your eyes focus on something that is physically only centimetres away. Getting the optics, the two viewpoints and the head-tracked update all correct together is what produces the uncanny sense of solid things standing at real positions and true size.
The honest caveat mirrors the last section. This is a masterful reconstruction of how a scene *would* look, not a window onto verified reality. Colours, brightness and material finish are approximations; the depth is convincing but computed. For a designer, that is exactly enough to judge whether a corridor feels tight or a ceiling feels low - a felt, spatial judgement - and not enough to certify a dimension or a specification, which stay with the model and the drawings.
Left-eye image + right-eye image, each perspective-correct, fused by the brain into solid depth. Head moves -> both redraw -> motion parallax -> the world stays anchored.
Latency and frame rate - why they must be low and high
Two numbers decide whether a headset feels like a stable world or a nauseating one: how *fast* the whole loop runs (frame rate) and how *little delay* there is between your head moving and the matching image reaching your eyes (motion-to-photon latency). These are the comfort numbers, and they matter more than resolution or graphics quality.
Consider what your body expects. When you turn your head in the real world, the scene sweeps across your vision instantly and perfectly in time with the motion your inner ear feels. Your vestibular system (the balance organs in your inner ear) and your eyes agree, as they have all your life. In a headset, if the displayed world arrives even a few tens of milliseconds late, your inner ear reports that you moved but your eyes briefly report a world that has not caught up. That disagreement between felt motion and seen motion is the leading trigger of virtual reality sickness (cybersickness): disorientation, nausea, cold sweat, headache. It is not a rare glitch - it is the single biggest comfort problem in VR, and it comes straight from latency.
So the engineering target is brutally simple: keep motion-to-photon latency very low (roughly the low tens of milliseconds or less) and keep the frame rate high - commonly 72, 90 or 120 frames per second, so a fresh, correct image lands every eleven to fourteen milliseconds or sooner. A higher frame rate means each image is more nearly right for where your head actually is by the time you see it. Devices also cheat cleverly to hide latency: they predict where your head will be a few milliseconds ahead and render for that predicted pose, and they reproject (warp) the last rendered frame to match a last-instant head reading if the full render is not ready. These tricks buy comfort, but they are patches over a hard real-time problem.
For a designer the practical lesson is that comfort is a hardware-and-software achievement, not a given. A poorly performing setup - an underpowered computer, a heavy scene that drops frames - does not just look worse; it can make people ill within minutes. When immersion is worth using, it is worth doing on hardware that holds its frame rate, and worth keeping sessions short.
Head moves -> track -> render two eyes -> display. Total delay = motion-to-photon latency. Low latency + high frame rate = comfort. Late image = inner-ear vs eyes mismatch = sickness.
The whole loop - a convincing illusion, never a source of truth
Put the pieces together and spatial computing is one tight real-time loop, running perhaps ninety times a second, every waking moment you wear the device. It goes: sense your head and hand pose (tracking); render the two perspective-correct eye images for that pose; warp and display them onto the screens through the lenses; then immediately repeat, with your very next movement already feeding the next cycle. Nothing about the stable, solid world you perceive is stored as a finished picture; it is being reconstructed continuously, faster than your perception can catch the seams. When every stage keeps up, the illusion is seamless and the digital room simply *is there*. When any stage stumbles - tracking loses features, the computer drops frames, latency creeps up - the seams show as juddering, swimming or drift, and the body notices immediately.
Understanding the loop changes how you use the tool. It explains why a blank or crowded room can wreck tracking, why an underpowered machine causes sickness rather than merely looking rough, why hands sometimes lag or jitter, and why the experience is so sensitive to getting the whole pipeline right. It also explains the ceiling on today's comfort, which the last lesson of this module examines in full.
Most importantly, the loop makes vivid why XR is a tool for seeing, understanding and communicating, and never a source of truth. Everything you experience is a real-time reconstruction assembled from estimated positions and approximated images - astonishingly useful for judging how a space feels at true scale, and structurally unsuited to certifying anything. You do not read a dimension off a reconstruction; you do not set out a building from it; you do not decide a structural question inside it. Those binding results stay where they belong: with the verified BIM model and drawings, measured survey data, qualified engineers and licensed surveyors, and the governing codes including the National Building Code of India. The headset shows you the space with uncanny presence so your spatial judgement can do its work - then you take the questions that need certainty back to the instruments and the specialists. Hold that line and the technology is a powerful ally; forget it and the very convincingness that makes it useful becomes a trap.
6DoF tracking
What the device must know
Six degrees of freedom = position (3) plus rotation (3). Full 6DoF lets you walk and lean, not just look around (3DoF). Achieved by inside-out cameras plus motion sensors. Principle, not a spec to certify.
SLAM / inside-out
How position is estimated
The headset watches room features and simultaneously maps them and locates itself within the map. It is an estimate that can drift in blank, dark or reflective spaces - never a survey. Lesson 2.1; hardware limits in 2.4.
Motion-to-photon latency
Why comfort depends on speed
The delay from head movement to the matching image reaching the eyes must stay very low, with high frame rate (72/90/120 Hz), or the inner-ear vs eyes mismatch causes cybersickness. Comfort is a hardware achievement.
A tool, not a source of truth
What the view may decide
The stereoscopic, head-tracked view is a real-time reconstruction for seeing and communicating. Binding dimensions, setting-out and technical decisions stay with the verified BIM/drawings, engineers, surveyors and the NBC India.
Workshop — feel the loop, and find where it would break
You can understand tracking and display far better by paying attention to your own perception than by memorising numbers. This workshop uses a short immersive experience (or, if you have no headset, careful reasoning and observation of your own vision) to make the mechanism concrete and to locate its failure points - the conditions under which the illusion would wobble.
Optional: any borrowed headset or a free phone-AR app. Otherwise nothing but your own eyes, a room and a notebook - the perceptual demonstrations work without any device.
Goal: connect the mechanism (tracking, display, latency) to what you can actually perceive and reason about Inputs: any headset if available (a borrowed consumer VR/MR device or even a phone-AR app), OR just your own eyes and a notebook Time: ~40 minutes
- 1Prove stereo to yourself: hold a finger up close and look past it, then close one eye and the other. Note how much the finger jumps against the background - that difference between the two eyes is the depth signal a headset recreates by drawing two images.
- 2Prove motion parallax: move your head side to side while looking across a room. Watch near objects sweep faster than far ones. This is the cue the display must reproduce on every frame by redrawing for your new head position.
- 3If you have a headset: enter a simple scene, then deliberately test the tracking's limits - move to a blank wall, dim the lights, or move fast - and note when the world starts to drift, judder or lag. Record what conditions hurt it.
- 4If you have no headset: reason it through instead - list three conditions (blank room, poor light, underpowered computer, fast motion) that would starve tracking or drop frames, and predict the symptom (drift, jitter, lag, sickness) each would cause.
- 5Write a short note: in your own words, describe the sense-render-display-repeat loop, name the two comfort-critical numbers (latency and frame rate), and state one binding result you would NOT take from the headset view and where it must come from instead.
You’ll walk away with
A one-page account of the tracking-and-display loop in your own words, the perceptual cues (stereo depth, motion parallax) it recreates, the conditions that would make it fail, and a clear line on what the reconstruction may judge (spatial feel) versus what stays with the verified model, survey and specialists (binding dimensions and decisions).
Three altitudes on the same idea
Read the band that fits you — or all three.
You do not need to build tracking systems, but understanding the loop - sense, render, display, repeat - tells you exactly where an immersive review will succeed or fail. It explains why you should run reviews in a room with good visual features and steady light (so inside-out tracking stays locked), why you must drive a heavy coordinated model on hardware that can hold ninety frames a second (so no one gets sick), and why a laggy, stuttering session is not just unpleasant but actively counterproductive in front of a client. It also grounds the discipline you will carry through the course: the world in the headset is a continuously reconstructed illusion from estimated poses and approximated images - superb for judging whether a space feels right at true scale, useless as a ruler. Keep binding dimensions, setting-out and technical decisions with the verified BIM/drawings, engineers and surveyors. Judge the tool by its comfort and stability, not its graphics, and specify hardware accordingly.
Knowing how the illusion is made helps you run a smooth client walkthrough and set honest expectations. The reason a client can look around their future kitchen and instantly understand it is stereoscopic, head-tracked display - two perspective-correct images redrawn as they move, giving real depth and true scale. The reason a session can make someone queasy is latency and dropped frames, so use capable hardware and keep the experience short and comfortable, seating nervous clients if needed. And because colour, brightness and finish are approximations reconstructed in real time, be candid that the immersive view shows *layout, scale and spatial feel* faithfully but is not a colour-accurate proof of a material - final finishes are still confirmed with real samples and the specification. Used this way, the technology does exactly what you need: it lets a non-designer stand inside the space and understand it, while you stay clear about what it can and cannot certify.
This is the mechanism behind the magic, and it is worth knowing precisely. Two machines run together: positional tracking (inside-out cameras plus SLAM working out where your head and hands are in 6DoF) and display (a stereoscopic, perspective-correct image redrawn for each eye on every frame, so the world stays anchored as you move). The whole loop - sense, render, display, repeat - runs dozens of times a second, and its two comfort-critical numbers are low motion-to-photon latency and high frame rate; get them wrong and the mismatch between your inner ear and your eyes causes cybersickness. Carry two ideas forward: first, the experience is sensitive to the whole pipeline being right, which is why cheap or underpowered setups disappoint or nauseate; second, and most important, everything you see is a real-time reconstruction from estimates - a tool for seeing and understanding, never a source of truth. That single distinction will keep your judgement sharp for the rest of the course.
“The image in a headset is basically a very good video or photograph of the design - so if it looks solid and real, I can trust what I see, including measuring or judging exact sizes from inside it.”
Do it yourself
No headset required for most of this - reason from your own perception.
- 1Explain what positional tracking does and why 6DoF (walk and lean) feels so different from 3DoF (look only).
- 2In one sentence each, say what inside-out tracking and SLAM mean, and one condition under which they drift.
- 3Why does a headset draw two different images, and why must it redraw them on every frame as your head moves?
- 4Explain, in terms of the inner ear and the eyes, why high latency and low frame rate cause motion sickness.
- 5Describe the sense-render-display-repeat loop, then state why the resulting view is a tool for seeing, not a source of truth.
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Positional tracking — Wikipedia — Positional tracking, 2026.
- 02Simultaneous localization and mapping — Wikipedia — Simultaneous localization and mapping, 2026.
- 03Inside-out tracking — Wikipedia — Inside-out tracking, 2026.
- 04Stereoscopy — Wikipedia — Stereoscopy, 2026.
- 05Latency (engineering) — Wikipedia — Latency (engineering), 2026.
Now that you know how any headset holds a world steady, the obvious next question is which headsets and devices exist and how they differ - tethered and standalone VR, passthrough MR, high-end spatial computers, and plain phone and tablet AR. Next we map the device families and their trade-offs, honestly and without recommending any of them.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →