Tsqaro - Playtest and Pitch Console for a Standalone VR Puzzle Demo

Dashboard, sessions calendar and list, the live session run sheet, build detail with 5 tabs and comfort results. The date range, filters, seat actions and checklist results all change what you see.

An in-headset comfort check every 10 minutes of play. A score of 7 or above turns the seat red and shows the break protocol: remove the headset, seat the tester, offer water, do not resume within 10 minutes.

72 fps on target devices, boundary handling, pause on headset removal, comfort vignette, seated reach, subtitles and the health and safety screen. Items not checked against Meta's documentation in 90 days show as review due.

4 playtest rounds, 30 playtesters, 10 builds including processing, failed and known-bad ones, 10 bugs, 7 crash groups and 109 comfort survey respondents.

Comfort Is the First Question

Publishers want to know who feels sick and why. The answer depends on the settings each player chose (teleport or smooth movement, snap or smooth turning, vignette strength, seated or standing), so scores mean nothing unless they are tied to the settings in force at the time.

Symptom Answers Are Health Data

Motion sickness answers can reveal information about a person's health, which Georgian law treats as a special category with stricter conditions. They need their own consent that a tester can refuse and still play, and must never be shown one person at a time.

Movement Data Can Identify People

Head and hand tracking is distinctive enough to help identify a person. Telemetry has to be linked to a pseudonymous id rather than a name, sampled at a low rate and shown only as aggregates, with no eye or face tracking at all.

Builds Nobody Could Trace

Without release channels and a checklist, the team could not say which build a tester or publisher had, whether it held 72 fps on a Quest 2, or whether it paused when the headset came off, checks that map to Meta's published requirements.