This document discusses challenges and strategies for developing free-roam virtual reality experiences. It outlines key challenges like motion sickness from frame rate and rotation speed. It recommends mapping the real world accurately with paths, doors and warnings. It also suggests roadmapping development like Spotify's release process and conducting frequent beta tests with spectator screens to gather feedback over weekly builds. War stories describe common issues in testing like throwing up or falling over. Tips include starting beta tests early and often to rebuild levels easily and testing per emotion like fear, excitement and nostalgia.

1. Product Management
Free-roam Virtual Reality

2. Challenges
● Motion Sickness
○ Frame rate
○ Rate of rotation - 1.5deg per sec (90deg/min)
○ Floor gradients
● 1:1 Real world Mapping
○ Path mapping
○ “Doors”
○ Warnings
● Visual Point of View
○ Lighting and Particle Effects
○ Voice Over

3. Roadmapping
● Hardware, Software, Web, Game
● Spotify Release “Train” (Spotify Engineering Culture Video)

4. Test & Validate
● Beta Test
○ Spectator Screens
○ Deep segmentation
○ Weekly updates and builds
○ Gameplay / Voice / Story Line / Point of View
● Full Time Operation at Dev Centre
○ Feedback Loop

5. War Stories
● Throwing Up
● Bloody Noses
● Falling Over

6. Tips for VR
● Beta test often
○ From very early
○ Level rebuilds easier early on
● Situational Reaction Tests
● Tests per emotion
○ Fear / Empathy strong
○ Excitement / Joy / Nostalgia
○ Jump Scares vs Anxious Build Up (anti-climax?)