Content library

The Content library is your venue's single view of every car and track installed across every rig. It powers the launcher dropdowns, the public booking form's content picker, and the leaderboard's per-circuit filters. Manage it from Settings → Content.

Where content comes from

PitwallOS doesn't host content itself. Every car and track is installed on the rig PCs by you or your community using the normal sim-racing tools (Content Manager, Steam Workshop, mod launchers). The agent scans each rig's local install and reports back:

• Assetto Corsa — the agent reads content/cars and content/tracks, parsing each ui_car.json / ui_track.json for metadata.
• rFactor 2 — the agent walks Installed/Vehicles and Installed/Locations, normalising per-folder latest versions.

Rig-scoped, venue-visible

A car listed in the Content library is really the unionof what's installed on your rigs. The detail view for each item shows which rigs have it and which don't — useful when a booking fails with “content not on target rig.”

If a customer books a car that only exists on Rig 2, the platform routes the session to Rig 2. If no rig has it, the booking is refused at checkout.

Sync now

The agent auto-syncs content on every heartbeat, but the detection can lag a few minutes after a fresh mod install. Click Sync now on the Content page to force an immediate re-scan across every rig. Handy when:

• You just installed a new car via Content Manager and want it to appear before your next booking arrives.
• You removed a broken mod and want the platform to stop offering it in the launcher.
• You're debugging a “content missing” launch error and want to confirm the agent sees the same install you do.

Skins

Each car surfaces its available skins (AC) — the launcher lets operators pick a skin per rig at session start. Skins are read from content/cars/<car>/skins/ for AC. Custom customer skins can be uploaded through the customer portal (opt-in feature) and are distributed to rigs by the platform automatically.

Vehicle classes

Group cars into classes (GT3, LMP, Formula, etc.) from the Content page. Classes serve two purposes:

• Preset filtering. A presetcan be scoped to a class instead of a specific car list, so adding a new GT3 doesn't require touching every preset.
• Leaderboard grouping. The public leaderboard offers class filters as a top-level tab.

rF2 mod packages (.rfmod cache)

The Mod Packagestab shows the agent's cache of .rfmodbundles — per-content-fingerprint packages the agent builds on demand to host rF2 multiplayer sessions. You almost never need to touch this tab; it's exposed for debugging.

Full context on how the cache works and what invalidates it: rFactor 2 configuration.

Distribution jobs

When you upload customer skins or apply a platform-level content push, the system emits distribution jobs to each affected rig. The Distributiontab shows recent jobs with per-rig status. Failed jobs surface a “Retry” button.