work / race os · a'dam vr

RaceOS.

Racing at A'DAM VR ran on a supplier's software. Race OS starts and runs the races across 14 rigs itself. On 23 September the park ran its first day on it.

scroll ↓

5 / 5

rigs ready within 14 seconds of the start moment

measured · session log, 24 September

6 / 6

rigs started at once, each on the first attempt

measured · own CSP app, 23 September

29 / 29

server actions reachable from the work screen

measured · own test

rigs, the wall and the results in one session

built · race os

race os · rig screeninternal

Results screen in an A'DAM VR racing rig, with demo names

01 / the question

A start that is the same for everyone.

Racing ran on a supplier's software. At every session change, someone had to press Start on each rig. Whether a rig was ready, the front desk could not see.

02 / what we built

Racing in our own hands.

Race OS only starts the race once every rig reports ready. Our own app inside the simulation presses Start itself, on all rigs at once. Hot laps is one continuous practice. Results and leaderboard show on the rig and on the wall. The front desk runs it from Checkpoint.

03 / measured in the park+

rigs ready after the start moment5 of 5, within 14 s

automatic start on the rig6 of 6, after 1 attempt

server actions in the work screen29, all 29 reachable

own measurements in the park · 15 to 24 September 2026

how we measure this

The start times come from the session log of 24 September, with the owner in one of the rigs. The automatic start was measured on six rigs at once and confirmed on the floor.

next case

HubSpot.

adam-vr.comlive

Need something
like this?

Tell us what is going on. We look first, then we talk.

privacytermssitemap
kvk 88807797vat nl004657139b07