A sim racer's work rarely stays on a single PC. You fine-tune tyre pressures, damper clicks, and wing angles on your dedicated rig. You review telemetry traces and tyre wear curves on your laptop over coffee. You check league schedules and race results on your phone.
It makes sense to want setups, lap history, and overlay layouts synchronized everywhere.
The trouble is how standard software approaches cloud sync. Typical web tools assume an office environment: you click save, a spinner appears, and a network request fires immediately in the background. On an office laptop, a momentary network spike or disk flush passes unnoticed.
Put that same behavior onto a sim racing rig pushing high frame rates, and it causes immediate friction. A sudden background upload can saturate your home connection, causing ping spikes on your multiplayer connection right when you are battling for position. Even worse, unthrottled background disk writes can cause a micro-stutter mid-corner.
Local first, sync in the pits
When building APEX, we treated cloud sync as an opportunistic background task layered on top of an offline-first foundation. The driving loop never depends on the network.
We built the architecture around three practical habits:
- Instant local writes: Every setup adjustment, stint summary, and HUD position change writes immediately to local storage in less than a millisecond. The in-sim HUD reads strictly from local memory.
- Session-aware transport: APEX monitors the car's status. While the car is on track turning laps, cloud synchronization stays completely idle. Only when the driver enters the pit lane, stops in the garage, or exits the session does the background worker wake up to send data.
- Small binary diffs: Instead of uploading entire configuration files whenever a damper click changes, APEX transmits compact binary diffs. A complete suspension and aerodynamic change compresses down to a few hundred bytes.
Zero interruption on track
This setup means clicking save or crossing the start-finish line never triggers a loading spinner or stalls a thread. If your rig is on garage Wi-Fi and the connection drops during an hour-long race stint, nothing crashes and no data is lost. The local log keeps growing, and everything merges quietly once the connection recovers.
Good software on a racing rig should get out of the way of driving: save instantly to disk, upload when the car stops, and keep the multiplayer connection clear.
Take a look at how we designed the rest of APEX for the cockpit.
