VR Testing - The Testing Trinity
summary
Explains concrete test failures: prototypes in Unity + Oculus Rift show nausea once frame rate dips below about 46 FPS; recommends automated frame‑rate logs, synthetic motion tests, and a motion sickness rating plus heart‑rate and gaze recording. Lists what to test end‑to‑end: headset tracking jitter, controller latency, strap ergonomics, cloud asset sync, and standalone battery/thermal limits, with examples of tools and a simple survey that found a nontrivial portion of users report symptoms after minutes.
AI-written summary · about
chapters (7)
- 0:00VR testing challenges
- 5:55Hardware and software landscape
- 11:43VR prototyping tools
- 18:12Real-world VR testing
- 25:00Motion sickness and UX
- 31:58Performance and usability testing
- 38:16Closing remarks and Q&A
related talks
33mTesting in VR world
50mVR Best Practices
52mMastering Unity VR Rendering
43mFrom 0 to 90: achieving peak performance in multiplatform VR development
48mTalking VR Turkey
31mHow to make your user sick in 60 seconds
53mGame design for VR: Breaking Rules
46mScience based Design Decision Making for Virtual Reality
