Dashboard

The Dashboard answers the question "what is the bridge doing right now?" Flight state is on the left, stick activity is on the right, and operational state stays in the persistent top strip. Use it as a quick inspection page before and after tuning changes: Tuning is where you adjust gains, while Dashboard shows what the sim is currently reporting and which force channels the bridge is sending to the stick.

Flight state panel

The flight-state panel shows what the sim is telling the bridge. From the top:

Three numeric readouts in a row — AIRSPEED (kt), G-LOAD (g, turning amber when outside the normal range), and VERT SPEED (ft/min, turning amber past ±200 fpm).
ELEVATOR and AILERON deflection on a pair of BiBars — bidirectional meters with zero at centre, full-scale at the edges, and a signed numeric value to the right of each label.
A trim row beneath the bars showing signed elevator and aileron trim together.
Warning rows: stall and overspeed (both turn amber when active), and a conditional Mach readout that only appears once Mach ≥ 0.30 so GA tiles don't waste space on "0.005".
Autopilot status — ENGAGED / OFF, plus the flight director's bank and pitch references whenever AP is driving the aircraft. When AP is off, the reference cells collapse to "—".

The metric tiles show "—" until live sim data arrives, so a "0 kt / 0.00 g" reading is never confused for telemetry. The panel refreshes at roughly 20 Hz — the UI is a decimated view of the 50 Hz control loop underneath.

Effect groups card

Below the flight-state panel sits a dedicated card with one quick-mute checkbox per force-model family:

Stick feel — baseline spring, G-load stiffness, trim centre, dynamic deadband, rate damping, control-edge feel, and stick drop.
Engine — powerplant vibration. Uses the sim's per-engine vibration value when it reports one (turboprops, jets), else falls back to an RPM-driven ramp.
Airframe — stall, stall stick-shaker, overspeed, Mach, spoiler, flap, gear, and turbulence buffets.
Ground — runway rumble, brake shudder, touchdown thump, gear bumps, reverse rumble, nosewheel shimmy, and the ground-acceleration pitch cue.
Mechanical — gear-deploy and flap-step one-shots. Held effects show as held rather than constantly active.
Autopilot — spring-centre following while the AP is commanding the aircraft.

These are quick-mute controls for in-flight A/B comparisons. If engine rumble masks a buffet you are tuning, untick it, fly the same manoeuvre, then turn it back on. Toggling a group does not change the per-effect gains on the Tuning page; it gates that group's contribution in the active profile.

Stick activity panel

The right side explains what the bridge is sending on this tick. The headline names the strongest dynamic contributors, the stacked activity bar groups them by family, and the large activity number gives a quick sense of how busy the stick should feel.

The baseline centring spring is treated separately from dynamic effects. You will usually feel spring centring even when no rumble, buffet, or axis-load channel is active. That is why the active channel list focuses on changes above the baseline: trim centre, G-load spring changes, airspeed-loaded pitch / roll, engine rumble, ground roll, buffets, and mechanical one-shots.

Active channels are shown as chips in a 3-wide grid: cool/blue for stick-feel + aero-drag channels (axis load, spring centre, rate damp, sideslip, flap/spoiler/gear drag, propwash, ground-acceleration pitch cue), warm/orange for engine + ground + airframe buffets (engine rumble, runway, brakes, reverse, nosewheel shimmy, stall / stall-shaker / overspeed / Mach / spoiler / flap / gear buffets, turbulence), and warm-held for the mechanical one-shots (touchdown, gear deploy, flap step). Every chip is pre-populated muted at app launch so you can see the full force model up front; chips "wake up" as their channel crosses the activation threshold.

The per-aircraft control-system feel (Manual / Hydraulic-boosted / Fly-by-wire) is not a chip of its own — it lives on the Tuning page and reshapes the existing spring and aero-load channels (and, on Fly-by-wire, quiets engine rumble and the stall shaker on the stick).

Axis load shows the signed pitch and roll constant forces after the force model has summed them. Centring spring shows the current spring coefficient, deadband, and pitch / roll centre. If MSFS is paused, dynamic forces go quiet and this section should settle to a neutral default spring rather than going limp.

Operational strip

Arming, connection state, mode, profile switching, and Save stay in the persistent top status strip. They are not Dashboard-only controls:

ARM gauge — top strip, centre. Click to arm / disarm. See Arming the stick.
SIM / DEVICE / MODE lamps — top strip. Each is colour-coded; if the stick stops working, the lamp that is red tells you why.
Profile picker + Tune / Save button — top strip, right side. The active profile is highlighted in the picker; the Save button shows up whenever you have unsaved tuning changes.

What the Dashboard does NOT do

The Dashboard is not a replacement for Tuning. It shows what is happening and lets you mute groups quickly, but per-effect gains stay on Tuning. To manage a large profile library, use Profiles. To diagnose a connection issue, use the Support page.