PitwallOS documentation

Everything you need to run a sim racing venue on PitwallOS — from the first signup through the trickier Assetto Corsa and rFactor 2 edge cases.

Getting to your first race

A brand-new venue is four short guides away from running paid sessions. Do them in order — each one builds on the previous.

One Windows installer per rig PC. Registers each rig with your venue in a couple of clicks.

Confirmed-working versions of Content Manager, CSP, and the runtime settings the agent expects.

Connect Razorpay or PhonePe so customers can book online. Skip and add later if you're testing.

The dashboard operators live on. Launch solo sessions and group races, approve rigs, handle walk-ins.

Reusable launch bundles — track, cars, weather, AI, race rules. Powers Sim Control's launch flows.

Cars and tracks discovered from your rigs. Sync after installing mods; group into vehicle classes.

Weekly schedule and blocked slots that gate the customer-facing booking page.

Per-duration prices used across bookings, walk-ins, and reconciliation.

Owners, admins, and staff. Invites, permissions, removal, audit trail.

Circuit records, hotlap competitions, and the /tv kiosk page for your lobby television.

Announce time attacks, leagues, and championships. Cover images, registrations, drafts.

Segments, campaigns, and automations. Post-session reviews, win-back at 30/60/90 days.

Fourth PC that auto-joins every group race and broadcasts it to the venue TV.

Capability matrix across Assetto Corsa, rFactor 2, and everything on the multi-title roadmap.

Dual Steam apps, auto-installed dedicated server, .rfmod cache, cut-points, .WET weather.

What each health-check status means and how to recover from common install issues.

Logo, colours, tagline, and the vanity subdomain your customers see.

Can't find what you need? Open the audit log inside your admin console or email hello@pitwallos.com.