Manage Station Settings

Pista manages Assetto Corsa settings as exact named game settings captured from a simulator's live settings. Game and third-party runtime mods such as CSP, Pure, and Real Penalty remain manually installed through their licensed tooling; Pista does not assign or inspect a supported runtime baseline.

Required Station Identity

Every Windows station uses the SteamID64 selected in Content Manager under that simulator's Windows account. Setup also requires CM to select a valid AC or AC PRO root before pairing. If the machine page does not show the expected SteamID64, confirm CM's selected account and default storage, then run the current Pista Setup and choose REPAIR.

Capture and Share Settings

Each simulator runs one Display and one Controls setting. Stations › Game settings lists the venue's settings; each setting's page is where it is applied, retried and re-captured. Under Stations › Hardware, the Game settings column names the two each simulator runs, flags a problem and links to the setting; it appears once the venue has a setting. Capture needs a current Pista Agent with the game detected.

To switch what a simulator runs:

1. Go to Stations › Game settings and open the setting.
2. On its Simulators tab, select Apply in the simulator's row. The button exists only where the setting is available.
3. Check the row. It reads Revision N not applied yet (or the revision it still has) until Assetto Corsa is closed, then Revision N applied.

To capture a setting:

1. Set up a simulator in Content Manager the way it should run.
2. Go to Stations › Game settings, select Capture new, choose Display setting or Controls setting, enter a name and pick the simulator to capture from. To update an existing setting, open it, select Re-capture and pick the simulator.
3. Each simulator in the list says what it runs now. Capture saves exactly what that simulator runs at that moment. If it would save another setting's files under this name, the button reads Capture anyway; load the right settings first.
4. Only simulators that are on can be picked. A capture the simulator does not start within 10 minutes fails; start it again once the simulator is on.
5. Open the setting. On its Simulators tab, tick Available for the simulators that may use it. A ticked simulator with no setting of that kind takes it right away. The others keep what they run and gain the choice on their tablet.
6. Select Apply for the simulators that must run it now, and check that each one shows Revision N applied for the newest revision once idle.

A name belongs to one setting. Capturing it from another simulator with the same equipment makes its next revision; the setting's History tab shows where each one came from. Simulators running a setting follow its new revisions. Content Manager can stay open. Applying waits for Assetto Corsa to close. Unticking Available stops future updates on that simulator and leaves its current settings in place. A simulator's Machine page names its two settings and links to them.

Display contains video, VR, triple-screen geometry, cockpit view, the CSP module settings that belong to that view and the HUD layout. Triples and VR each carry their own. To change the HUD, arrange it in the game on the source simulator, quit the game, then capture: the game saves the layout only when it exits, and capture waits until it has closed. Every tablet launch puts the captured layout back; a launch from Content Manager does not.

If CMRT is installed, Display also records whether its Scale Automatically setting is on, and each simulator switches its own CMRT to match. After a CMRT update, the Display status on that simulator's Machine page notes that the setting was captured with another CMRT version: check the HUD on the source simulator and capture again.

Use matching CSP installations; Pista does not install missing modules. FFB Tweaks belongs to Controls with the wheel, pedals and bindings.

A Controls setting only works on simulators with the devices its bindings use, so Pista checks the wheelbase, pedals and button box each simulator reports:

• Each Controls setting lists its equipment.
• Its Simulators tab cannot tick Available for a simulator that lacks one of them and names the missing device. Re-capture cannot pick that simulator either. The tablet never offers such a setting.
• Capture is refused when the controls on the simulator point at a device it does not have, for example another simulator's settings loaded there. Load this simulator's own settings in Content Manager, then capture again.
• A wheelbase that is switched off still counts as that simulator's. The simulator is flagged Equipment not connected until it is switched on.

Per-car FFB gains (user_ff.ini) stay on each machine; Controls settings neither capture nor overwrite them. The CSP half of a Display setting does not include plugin state or separate Pure settings.

A tablet only lists the settings its own simulator can use, so a drift setup never shows on a simulator without a drift rim. Selecting a setting on the tablet or dashboard asks the machine to apply it within seconds while the game is closed. Apply now on the tablet repeats the request and rewrites the files even when the machine believes it already holds them.

Pista does not fight hand edits. Every minute the agent compares the managed files with what it last applied and, when they differ, Stations › Hardware, the Machine page and the tablet show the setting as changed on the simulator; nothing is rewritten. Every launch from the tablet and every Apply now puts the settings back. So: test from Content Manager, then either re-capture the setting you are on from that simulator to make your change the new revision everywhere, capture it under a new name, or launch from the tablet to discard it. On the setting's page, Re-capture keeps the change and the changed simulator's row offers Re-apply to discard it.

If capture reports that the agent needs updating, update Pista Agent on that simulator and capture again. An apply failure flags the setting in the simulator's row under Stations › Hardware; the setting's page shows the error in that simulator's row. Fix that cause and select Retry there. A failed file update restores the previous settings.

Portable or custom Content Manager storage is unsupported.

Uninstall

Before the first managed settings write, the agent stores the exact original bytes or absence locally. Interactive uninstall asks whether to restore those originals or keep the current settings. It never restores a whole game directory.

A managed simulator is ready when it is paired, has reported recently, its venue content is ready, and any assigned game setting is applied.