Dashboard

The Dashboard is the cockpit view — telemetry coming in from the sim, forces going out to the stick, and the master arm toggle. This is the page you'll have open during a flight.

Telemetry panel (top-left)

The telemetry panel shows what the sim is telling the bridge. It uses two custom controls to keep the readout dense but readable:

Radial gauges — a 240° arc showing indicated airspeed, altitude, and G-load. Each gauge has a needle for the current value and a soft tick ring for reference.
BiBars — bidirectional meters showing elevator and aileron deflection. Zero at centre, full-scale at the edges.

Figure 2. Telemetry panel close-up. Left to right: airspeed gauge, altitude gauge, G-load gauge. Below: elevator and aileron BiBars.

Pitch, bank, and AoA appear as plain numeric readouts beneath the gauges. Everything refreshes at roughly 20 Hz — the UI is a decimated view of the 50 Hz control loop underneath.

Force-output meters (centre)

The centre of the Dashboard is the live force readout. Two BiBars show the pitch and roll forces the bridge is sending to the stick, expressed as a fraction of full authority: -1.0 on the left, 0 at centre, and +1.0 at full right.

Below the bars, small badges light up when individual effects are contributing — stall buffet, ground rumble, gear bump, and so on. If you ever wonder whether an effect is actually firing, this is where to look first.

Figure 3. Force-output meters with three effect badges lit: centring spring, airspeed loading, and stall buffet. The small trim marker on each bar shows the spring's shifted centre.

Arm toggle (top-right)

The big pill-shaped toggle is the master arm. It has three visual states:

Disarmed — slate grey, no motion. No forces are being sent to the stick. Safe state.
Ready to engage — the pill softly pulses blue. The bridge has a healthy connection to the sim and the device; click (or press Space) to arm.
Armed — solid blue with a lightning glyph. Forces are flowing.

The toggle refuses to arm if there's no sim connection (the Sim chip below the Ready-to-engage banner is red) or no device detected. If you're testing effects without a sim, use Mock SimConnect — the arm toggle works normally in mock mode.

Connection chips

Directly under the arm toggle, three chips show the state of the three things that have to be right for the bridge to work:

Device — green when the stick is open and taking effects; amber during open; red when missing.
Sim — green with the name (MSFS / X-Plane / MOCK); red when no data is flowing.
Profile — shows the active profile name with a dot if the profile has unsaved changes from the Tuning page.

Figure 4. Connection chips. All three green is the happy path. Any red chip is a pointer to either Doctor (for device / sim) or Tuning (for an unresolved profile).

Connection chips

The row just under the Ready-to-engage banner carries the three chips the bridge cares about: Device (joystick), Sim (MSFS / X-Plane / MOCK / offline), and a mode summary (e.g. “MOCK mode — device open, UI-driven” or “device + sim live”). Any red chip is a pointer to Doctor.

What the Dashboard does NOT do

The Dashboard is read-only apart from the arm toggle. To change how the stick feels, head to Tuning. To switch to a saved set of values, head to Profiles. To diagnose a connection issue, head to Doctor.