Simulation Sickness Testing in VR

Description

A set of practices for detecting simulation sickness in VR: expert review against known provoking factors, sampling of susceptible participants with the Simulator Sickness Questionnaire, larger samples and safety procedures.

Simulation sickness can cause eyestrain, headaches, postural instability, sweating, disorientation, nausea and vomiting. Lewis-Evans stresses that it is an individual, physiological issue affecting a significant minority, so the usual five-participant usability sample cannot detect or rule it out. He recommends three responses when large samples are not affordable. First, expert analysis against known causes: unstable frame rate or latency (he cites at least 90 frames per second and under 20 milliseconds latency), motion blur, flicker, rolling motion or moving horizons, camera movement the player does not control, zooming, low or very high camera height, artificial acceleration (vection), situations that would cause sickness in real life, and UI placed so that it demands large head or eye movements. Second, recruit vulnerable people, for example by screening with the Simulator Sickness Questionnaire and recruiting across the risk range, and including older people and those who rarely play first-person games. Third, over-recruit by at least ten per cent because some participants will stop. He adds safety and ethics checks: safe space, quick headset removal, full payment if people stop, consent wording, a recovery area, travel home, and breaks for observers watching VR footage.

Attributes

Loss type
Siloed
Data
Mixed
Effort
Days

Steps

  1. Review the build against known provoking factors (frame rate, latency, vection, camera control, flicker, UI placement).
  2. Screen candidates with the Simulator Sickness Questionnaire or sickness history and recruit across the susceptibility range, including older and less experienced players.
  3. Over-recruit by at least ten per cent and prepare a safe test space, recovery area and consent wording.
  4. Brief participants that they can stop at any time with full payment and agree a fast way to communicate.
  5. Run sessions, monitoring for symptoms and recording when and where they appear.
  6. Administer the SSQ after exposure and relate symptoms to game events and settings.
  7. Report sickness triggers and comfort options to the team.

Sources

  • Drachen, A., Mirza-Babaei, P. & Nacke, L. (eds), Games User Research (2018)

Also known as

  • Simulator sickness testing
  • Cybersickness testing
  • Simulator Sickness Questionnaire (SSQ)
  • VR comfort testing

Categories

  • Accessibility
  • Human Factors & Error