Supported engines
PitwallOS abstracts simulators behind a single EngineDriver protocol; each engine implements the protocol and the rig agent picks the right driver based on the booking. The capability matrix below reflects what each engine supports today.
| Capability | Assetto Corsa | rFactor 2 | LMU |
|---|---|---|---|
| Solo / practice | Yes | Yes | Planned |
| Group host (LAN dedicated server) | Yes | Yes | Planned |
| Group join | Yes | Yes | Planned |
| Auto-drive (menu image recognition) | Yes | Not needed | Not needed |
| Skin upload | Yes | Roadmap | Roadmap |
| Replay save | Yes (.acreplay) | Yes (.Vcr) | Roadmap (.Vcr) |
| Server REST shutdown | No | Yes (port 5397) | Planned (port 6397) |
| .rfmod cache (mod packaging) | n/a | Yes | Planned |
| Weather per track | Global enum | Per-track .WET | Per-track .WET |
| Track limits | tyres-out | Cut points | Cut points |
Per-engine guides
Adding a new engine
Each engine is one Python package under agents/rig-agent/engines/. Add a driver.py implementing the EngineDriver protocol, register it in engines/__init__.py, ship database migrations to unlock the engine string in CHECK constraints, and add UI affordances. See the engine README in the agent repo for the full checklist.