In this article, we will untangle who actually invented virtual reality, how the tech works at a nuts and bolts level, and what modern makers can learn when building their own rigs. We will cover the first headsets, key patents, the commercial missteps of the 1990s, and the practical design choices behind today’s systems.
To create this guide, we verified the early devices and patents associated with Morton Heilig, Ivan Sutherland, and Jaron Lanier, then cross checked modern specs from the first wave of consumer VR in 2014 to 2016. We examined patent filings, technical papers, and product announcements to pin down dates, design principles, and failure modes. Our focus was extracting usable lessons about optics, tracking, latency, cost, and IP strategy that you can apply in your workshop.
Let’s start with the basic problem VR set out to solve.
Key facts
- Invention name: Virtual Reality. A system that presents computer generated stereoscopic imagery with head tracking to create a sense of presence.
- Inventors: No single inventor. Documented foundations include Morton Heilig’s head mounted Telesphere Mask (U.S. Patent 2,955,156. 1960) and Sensorama simulator (U.S. Patent 3,050,870. 1962). Ivan Sutherland and colleagues built the first computer tracked head mounted display in 1968. Jaron Lanier popularized the term “virtual reality” in the 1980s and commercialized input devices through VPL Research.
- Key patents: Heilig’s 2,955,156 and 3,050,870. Later design and tracking patents span many companies. One visible modern example is Oculus’s design patent USD701206 S1 granted in 2014.
- Commercialization year: Early commercial attempts appeared in arcades and labs in the late 1980s and 1990s. Broad consumer adoption began around 2016 with PC and console headsets such as HTC Vive, Oculus Rift, and PlayStation VR.
- Problem solved: Present a convincing 3D world that updates with your motion at low latency. The user should feel present in a virtual space.
- Original prototype cost: Not publicly documented for Heilig or Sutherland’s builds. Contemporary accounts point to significant lab budgets and custom hardware.
- Modern DIY build cost: About $15 to $40 for a phone based viewer. Around $150 to $300 to assemble a hobby headset with commodity displays, Fresnel lenses, and a 6-axis IMU. A full PC VR setup ranges widely depending on PC.
- Primary failure mode: Discomfort from latency and tracking errors that cause VR sickness. Secondary issues include limited field of view, poor optics that produce god rays or chromatic aberration, and content that moves the camera without matching user motion.
- Key quantifiable metrics: Frame rate 90 Hz or higher for comfort. Motion to photon latency ideally ≤20 ms. Typical field of view around 100° to 110°. Room scale systems often recommend at least 2 m × 1.5 m, with 3.5 m × 3.5 m providing better movement.
Why the old way broke presence, and what VR fixed
The core problem was mismatch between what your eyes see and what your inner ear feels. A regular screen only responds when you move a mouse or joystick. Your head turns, but the image does not. That mismatch breaks immersion.
VR fixes this with head tracking and stereoscopic rendering that update in lockstep with your motion. Presence emerges when the world responds within a few milliseconds. Once latency creeps above comfort thresholds, users report nausea and eyestrain. Designers learned the hard way that even beautiful visuals cannot overcome a laggy pipeline.
Why this matters to you. If your prototype cannot hit stable frame timing and low latency, no amount of art polish will save it. Prioritize the motion loop first.
How a headset actually works
A VR headset is a compact optical system coupled to fast tracking and a rendering pipeline.
- Optics: Most consumer headsets use Fresnel or hybrid Fresnel lenses to keep weight low. The lens magnifies a small display to fill a wide field of view. Expect visible artifacts at lens ridges unless you tune distortion correction. Alignment tolerances around ±0.5 mm on lens spacing can noticeably affect clarity and eye strain.
- Displays: OLED or fast LCD panels run at 90 Hz to 120 Hz or higher. Low persistence eliminates smear by illuminating pixels for a short duty cycle each frame. That single change helped reduce nausea in modern headsets.
- Tracking: Outside in systems like early Lighthouse setups use base stations that sweep infrared patterns across the room. Photodiodes on the headset record timing to compute 6-DoF pose. Inside out systems place cameras on the headset and run SLAM algorithms to track feature points in your room. Either way, the system fuses IMU data at 1000 Hz or more and corrects drift with vision data.
- Latency budget: Your pipeline needs to hold motion to photon under about 20 ms. That includes sensor readout, pose prediction, rendering, timewarp, and display scanout. Miss that budget and users feel it immediately.
For makers. Measure end to end latency with a simple LED test rig and a high speed camera. You do not need lab equipment to find the spikes that cause discomfort.
From film tricks to wireframes to room scale: the development journey
VR’s roots are eclectic. Heilig’s Sensorama aimed to stimulate multiple senses with 3D film, scents, and airflow. Sutherland’s 1968 system connected to a computer and drew wireframe rooms that moved as you moved. In the 1980s, VPL sold the DataGlove and EyePhone to labs and studios. The 1990s saw a consumer flirtation with arcade pods and early consoles that could not deliver acceptable latency or resolution.
The second wave around 2013 to 2016 finally hit the technical bar. Displays jumped to 90 Hz. IMUs became cheap and precise. Tracking could cover a 2 m × 1.5 m space at millimeter scale. That is when room scale interactions, natural hand input, and reliable presence came together.
The lesson. Progress came from steady improvement in sensors, optics, and software timing, not a single breakthrough. Expect to iterate on comfort and tracking long after your first demo works.
The unit economics that shaped design
VR hardware is a balancing act between cost, comfort, and performance.
- Displays and optics: Bigger field of view and higher resolution demand larger lenses and panels. That increases weight and cost. Makers often pick 2.8 to 3.5 inch panels at 1440p to 2160p per eye, then target about 100° to 110° FOV as a good trade.
- Tracking bill of materials: Outside in needs external beacons or cameras. Inside out needs multiple on-board cameras and a capable processor. Either approach adds sensors and compute cost.
- Comfort features: Head strap design, interpupillary distance adjustment, and lens inserts matter. Small changes, like adding a rear battery pack, can fix front heaviness and improve perceived comfort more than a higher resolution panel.
If you are budgeting a build. Expect $150 to $300 for a hobby headset using commodity displays, Fresnel lenses, an IMU, and a 3D printed housing. Add a gaming PC if you want high fidelity rendering. Phone based viewers run about $15 to $40 and are great for optical experiments and UX tests.
The patent story makers should know
There is no single patent that “owns” VR. Instead, there are clusters.
- Display and viewing: Morton Heilig’s 2,955,156 covered a stereoscopic head mounted apparatus in 1960. His 3,050,870 documented the multi sensory Sensorama simulator in 1962. Many later patents extend or reinterpret head mounted viewing and optics.
- Input and tracking: The 1980s to 1990s produced patents around data gloves, position tracking, and programmable virtual environments. After VPL’s bankruptcy in the 1990s, Sun Microsystems purchased a block of those VR patents.
- Modern design and tuning: Companies continue to file design patents on industrial design and utility patents on tracking, reprojection, lens design, and ergonomics. For example, Oculus received a U.S. headset design patent in 2014.
Takeaway for inventors. Patent around your unique mechanism or process, not the broad idea of VR. If your value is an optical arrangement that reduces glare at large pupil swim, or a tracking method that tolerates low light, write claims that protect the measurable improvement. Keep anything in your manufacturing recipe that cannot be reverse engineered as a trade secret.
The failure modes that make people rip off the headset
If your prototype fails, it usually fails here.
- Latency spikes: Users can tolerate occasional frame drops in a flat game. In VR, a single stutter can trigger nausea. Aim for stable 90 Hz and motion to photon ≤20 ms. Add late stage reprojection to mask rare misses.
- Optical discomfort: Poor lens choice produces god rays and chromatic aberration near edges. Misaligned lenses or fixed IPD cause headaches within minutes. Design around adjustable IPD and eye relief.
- Tracking loss: When the system loses tracking, the world drifts. Outside in systems struggle with occlusion. Inside out can struggle in featureless rooms. Provide enough visual features or add markers during testing.
- Locomotion mismatch: Moving the camera without matching body cues is a classic way to induce VR sickness. Prefer teleportation or arm swing to smooth joystick motion during early testing.
Quantify your fixes. Log frame times. Measure your reprojection rate. Record play area size and trackable volume. Small data keeps you honest.
Beyond the inventor. The deep history and the real discovery
It helps to separate concept from actionable engineering.
- Ancestors: Stereoscopic viewers date to the nineteenth century. Multi sensory theaters tried to extend cinema with scent and wind. Heilig embodied both ideas in patents that read like a blueprint for future headsets and arcades.
- From concept to principle: Sutherland’s 1968 system established the measurable principle that presence requires real time head tracked rendering. That is the hinge from idea to engineering discipline.
- Commercial framing: The 1980s supplied language and products. The 2010s supplied timing budgets, optics, and tracking that met human perception thresholds on consumer hardware.
The lesson. Ideas are common. The “real discovery” was a set of tolerances. Hit frame time. Hit latency. Hit ergonomics. Once those are reliable, content and markets appear.
Building your own. A modern maker approach
Two practical paths you can start this month.
Path 1. Proof of concept headset. $25 to $200
- Goal: Validate optics, tracking loop, and comfort.
- Materials: Phone based viewer or a 3D printed shell, 2 Fresnel lenses, a smartphone or small LCD module, an IMU like the MPU-6050, and elastic straps. Optional foam interface and IPD spacers.
- Tools: 3D printer, calipers, hot glue or epoxy, open source VR test apps.
- Time investment: 8 to 20 hours across a weekend.
- Success metric: Stable 60 to 90 Hz rendering from a simple demo, acceptable clarity across the center 60% of the field, and no nausea during a 10 minute session.
Path 2. PC tethered prototype with tracked space. $300+
- Goal: Demonstrate room scale interaction and ergonomics close to a commercial unit.
- Materials: Dual small LCDs or OLEDs at 1440p class, Fresnel or pancake optics, an IMU, a microcontroller for sensor fusion, and either inside out cameras or a pair of external beacons. Use a lightweight head strap and counterweight the rear to improve balance.
- Tools: 3D printer, basic machining for brackets, a gaming PC with a recent GPU.
- Time investment: 20 to 60 hours over a few weeks.
- Success metric: Sustained 90 Hz rendering with motion to photon ≤20 ms, reliable tracking across at least 2 m × 1.5 m, and 20 minute sessions with no user discomfort.
Three quick validation tests
- Latency smoke test: Tape an LED to the headset. Record head yaw with a high speed phone camera while toggling the LED at a known time. Count frames from LED change to display response. Pass if median delay ≤20 ms.
- Optics clarity sweep: Print a radial resolution chart. Display it in VR and rate line pairs resolved at center, 50% radius, and 80% radius. Pass if center is crisp and 50% radius is readable without eye strain.
- Tracking robustness drill: Scatter occluders like a cardboard tube and a lamp in your space. Walk a square path of 1.5 m sides ten times. Pass if drift remains under 2 cm and the system recovers within 1 s after deliberate occlusion.
IP strategy pointers for this category
- Provisional patent: File if you have a specific optical arrangement, lens stack, or tracking method with measurable improvement. Include bench data on latency, FOV, glare, or pupil swim.
- Design patent: Useful if your headset or controller has a distinctive industrial design that buyers recognize.
- Trade secrets: Keep calibration routines, distortion coefficients, or sensor fusion weights private if they are hard to reverse engineer.
- Prior art search: Focus on head mounted optics, display stacks, reprojection, and tracking in the 2010 to present window. Expect dense prior art on gloves and generic HMD shapes.
Maker friendly specs you can steal
- Display target: 90 Hz minimum. 120 Hz is even better for comfort.
- Field of view: Around 100° to 110° diagonal feels expansive without extreme lens sizes.
- Play area: Start with at least 2 m × 1.5 m. If you can clear 3.5 m × 3.5 m, interactions open up.
- Optical tolerances: Keep lens to panel distance within ±0.5 mm and inter lens symmetry within ±0.25 mm to reduce eye strain.
- Comfort weight: Aim for under 600 g on head. Counterbalance if the front is heavy.
FAQ
What is the minimum PC spec to test a tethered build?
As a baseline, target a GPU that can sustain 90 fps in a simple demo scene at 2160 × 1200. Midrange gaming cards from the last few years are fine for tests. Measure frame times rather than trusting a spec sheet.
Can I prototype with a phone and still learn useful things?
Yes. A $15 to $40 viewer is great for optics, UX flows, and early content tests. You will not learn room scale tracking or true low persistence behavior, but you can validate basics without big spend.
How do I choose lenses?
Start with off the shelf Fresnel lenses designed for VR. Measure glare and edge clarity. If you need better edge performance, try hybrid or pancake optics, but expect a tighter build tolerance and higher cost.
What causes VR sickness in a good looking demo?
Usually latency spikes or camera motion that does not match the user’s body. Lock the camera to the head. Keep frame timing stable. Offer teleport or short dashes instead of long joystick motion early on.
Is it legal to sell a DIY headset built from commodity parts?
Yes, but check for safety, labeling, and any patents your design might read on. A distinctive industrial design or a specific optical stack can be protected by others. File a provisional for your improvements if you plan to commercialize.
Closing takeaway
VR’s history says the winners are the teams who respect human perception numbers. This week, pick a path. Build the proof of concept and run the three tests above, or sketch a provisional claim around your unique optical or tracking idea. Log your frame times, latency, and comfort notes. You are gathering evidence, not just building a demo.
