PitCrew (PitManager clone)

[paoloambrosio]

Implement what RST PitManager (video) or ACC Drive (video) provide.

• Server

  • Serve Web client page
  • Receive telemetry, MFD state and MFD changes and broadcast to all connected clients
  • Support one race/team at a time
  • Single-instance in-memory storage No storage
  • Basic Authentication
    • Bearer would work better for client connections, but not for browser
    • mTLS could work for both but it might be a faff to set up (e.g. for browser)

• RaceDirector Client

  • Export telemetry when the Player field is present (rename it to LocalPlayer?)
    • Telemetry
      • Driver stint time
      • Fuel left
      • Fuel per lap
      • Tyre pressures
      • Tyre set
    • MFD state
      • Fuel to add
      • Tyres
        • Set
        • Pressures
  • Receive MFD changes from server and configure the in-game MFD (video)
    • Fuel to add
    • Tyres
      • Set
      • Compound
      • Pressures
    • Only if the game window is focused

• Web Client

  • Receive telemetry and MFD status from server and display it
  • Send MFD changes to server
  • Display requested MFD changes (useful to display when others push changes)

Out of scope:

• Client to receive remote telemetry and expose it to SecondMonitor
• Support multiple races at a time (can replace static "username" with race hash)
• ...

Links:

• How CrewChief does it for R3E and ACC.

[paoloambrosio]

R3E doesn't have values entered in the pit menu, but it has the information about the selected item.

public struct Shared
{
  // Unit: Liters (l)
  public float FuelLeft;
  // Unit: Kilopascals (KPa) (-1.0 = N/A)
  public TireData<float> TirePressure;

  // What is currently selected in pit menu, and array of states
  // (preset/buttons: -1 = not selectable, 1 = selectable)
  // (actions: -1 = N/A, 0 = unmarked for fix, 1 = marked for fix)
  public Constant.PitMenuSelection PitMenuSelection;
  public PitMenuState PitMenuState;
}

public enum PitMenuSelection
{
  Fuel = 3,
  Fronttires = 4,
  Reartires = 5
}

public struct PitMenuState
{
  // Pit menu preset
  public int Preset;

  // Pit menu actions [1 selected, 0 not selected, -1 N/A]
  public int Penalty;
  public int Driverchange;
  public int Fuel;
  public int FrontTires;
  public int RearTires;
  public int FrontWing;
  public int RearWing;
  public int Suspension;

  // Pit menu buttons
  public int ButtonTop; [-1 pit requested, 1 pit not requested]
  public int ButtonBottom; [1 pit requested, -1 pit not requested]
}

ACC doesn't have information about the selected menu item, but it has information about values entered.

public struct SPageFilePhysics
{
  public float Fuel; // Amount of fuel remaining in kg [in liters!!!]
  public Wheels<float> WheelPressure; // Tyre pressure [in PSI]
}

public struct SPageFileGraphic
{
  public float MfdFuelToAdd; // How much fuel to add on the MFD [in liters]
  public int MfdTyreSet; // # of tyre set on the MFD [0-indexed]
  public Wheels<float> MfdTyrePressure; // Tyre pressures on the MFD [in PSI]
}

[paoloambrosio]

Apply strategy on ACC:

• pit menu, 2x down
• left/right to change fuel to add
• get to determined tyre state from fuel (see below 👇🏻)
• if tyre change required
  • left/right to change tyre set
  • 1x down, 1x right if wet compound
  • 1x down, left/right to change FL pressure
  • 1x down, left/right to change FR pressure
  • 1x down, left/right to change RL pressure
  • 1x down, left/right to change RR pressure
• otherwise
  • 1x up, 1x right to close the change tyres menu
• 1x down to leave it to brakes entry

Get to determined tyre state from fuel (change tyres menu opened, on tyre set with dry tyres selected):

• 2x down, 1x right
• if it changed tyre set, we are done ✔️
  • otherwise it changed compound (tyre menu open and wet tyres) or brakes (tyre menu closed)
• 1x left to change it back, 1x up, 1x right
  • if we were in the compound, we would have changed it to dry and gone up to change tyre set ✔️
  • otherwise we would have opened the tyres menu (and we still don't know if we have wet or dry compound selected)
• 1x down, 1x right
  • if it changed the tyre set, we are done ✔️
  • otherwise we were on wet tyres and are on the tyre compound
• 1x left for dry compound, 1x up, 1x right to change tyre set
• if it changed tyre set we are done ✔️
• otherwise something went wrong ❌

Notes:

• Changes are not reflected immediately so we'll have to rely on timeouts to assume that no effect has been produced
• Going right on the last tyre set goes back to first
• Going right on wet tyres doesn't change them to dry, left does
• Minimum number of tyre sets is 5, so we will never be in a situation where it is enabled but it can't be changed
• We don't know the tyre compound that is currently selected: we have to make it up from the tyre set being disabled
• We don't know if brake or tyre change are selected
• Wet tyre compound disables tyre set selection
• Tyre menu could be closed

[paoloambrosio]

There is an edge case for ACC that CrewChief doesn't cover (but there is something about it in code:

        private static bool isStrategyOptionShown()
        {
            // maybe get this value from some clue in shared memory, for now just assume it's show.
            return true;
        }

The first pit strategy is created when you open the setup menu (no need to select one or see it). Further pit strategies are created when first seen in the setup menu. If there are no strategies available, there is going to be no menu entry. This means that we don't even know how to reach the fuel entry reliably.

• Down, Down
• "Try to change fuel"
  • If it changed fuel we are done ✔️
  • Otherwise we have been closing and opening the tyre menu
• "Try to reset entry", Up
• "Try to change fuel"
  • If it changed fuel we are done ✔️
  • Otherwise something went wrong
• Fail ❌

"Try to change fuel" can be implemented in two ways:

• Left, Left, Right to try to change value even if fuel is 0 or max - we could choose left or right based on current fuel entry
• Right if current fuel entry is 0, Left otherwise
  "Try to reset entry"
• Right if the first option above was chosen
• Left if current fuel entry is 0, Right otherwise