Near-Eye Display Optical Architecture Selection
Select a near-eye architecture by field, resolution, eyebox, eye relief, efficiency, color, focus cues, package, weight, prescription support, occlusion, manufacturability, and calibration. Birdbath, freeform, pancake, waveguide, and direct-retinal concepts distribute these tradeoffs differently; no architecture maximizes all of them.
Why this decision matters
This choice affects more than nominal optical performance. It changes package volume, tolerance sensitivity, supplier options, alignment effort, calibration, test equipment, production yield, and the evidence required before release. The correct answer therefore comes from the complete operating condition and acceptance method, not from a single catalog value.
Key engineering decisions
- Rank user and product constraints before choosing topology.
- Track étendue from display to eyebox.
- Include eye, face, frame, and calibration geometry.
These decisions should be captured in a requirement or trade study before the team commits long-lead components. Where requirements conflict, rank the product priorities explicitly so optimization does not hide a business decision.
Specification checklist
- Field and angular resolution
- Eyebox and eye relief
- Display size and brightness
- Package and weight
- Color, distortion, and focus
Every value should state the condition where it applies and how it will be measured. A specification without a defined test condition is not yet an acceptance requirement.
Common failure mode
A topology is chosen for compact appearance while efficiency, eye-box uniformity, prescription variation, or assembly tolerances prevent a usable product.
The practical remedy is to compare the nominal model, tolerance prediction, mechanical interfaces, and measured configuration together. Treating the symptom as an isolated lens or component problem often produces another build with the same system-level limitation.
Verification approach
Build an architecture scorecard, model nominal and tolerance performance, and test representative eyes, displays, prescriptions, poses, and environmental states.
Record the hardware revision, source or scene, wavelength, aperture, field point, focus or alignment state, environmental condition, processing, and measurement uncertainty. This makes the result useful for design iteration and supplier transfer rather than only for a one-time demonstration.
What to send PAO
Send use case, field, resolution, eye relief, eyebox, display data, package, weight, brightness, prescription range, and prototype images.
PAO applies this framework through automotive LiDAR and HUD optics, from requirements and architecture through detailed design, prototype evidence, and manufacturing transfer.