Between Two Realities: Testing AR / MR
summary
A QA team ported large CAD turbine models into Microsoft HoloLens and evaluated real-world limitations: the HoloLens scans reliably only to about 3 m, fails on glass/mirrors, overheats with highly detailed scans, and has inconsistent gesture controls across users; they also observed that adding more than five holograms causes interaction failures. Concrete recommendations include a visible scan-progress UI, enforcing ~2 m placement of content, admin streaming/log capture for debugging, and stability rules so holograms don’t fall through surfaces; the team frames deployment decisions around whether these constraints are acceptable.
AI-written summary · about
chapters (8)
- 0:00AR/MR introduction
- 6:35Mixed reality and HoloLens
- 10:11Factory project goals
- 14:23Space scanning quality
- 23:05Hologram gestures
- 31:24Testing and debugging
- 34:12Conclusions and outlook
- 40:03Q&A
related talks
51mThere's a Hologram in my UI!
53mA Thorough Look into Spatial Mapping with HoloLens
10mMixed Reality check
01h 05mChasing holograms - the future of HoloLens development
20mChallenges in Mixed Reality
46mHoloLens 301: Advanced Mixed Reality Development and Best Practices
50mDeveloping for Mixed Reality with HoloLens
18mMicrosoft HoloLens for the Enterprise