Current release. FFB-Bridge v1.2.0 is live. These docs track the current app described by the release manifest. If a section reads stale, flag it via the feedback form.

Cockpit Web

Cockpit Web is a local companion you open on a phone, tablet, or second browser to tune force feedback while the simulator runs. The desktop app serves it directly over your network — there is no cloud cockpit service and nothing to install on the other device.

Reach for it when you want to:

  • Tune on a larger touch surface than a slider.
  • Adjust forces from a second device without alt-tabbing out of the sim.
  • Compare A/B tuning changes quickly.
  • Attach live cockpit context to a beta report.

Start and pair

  1. Open Cockpit Web in the Pro app.
  2. Select Start.
  3. Scan the QR code, copy the pairing URL, or select Open locally to launch it in your desktop browser.

The phone, tablet, or browser must be on the same local network as the desktop app. The QR code and URL carry a private pairing token, so treat the URL like a temporary local access link — anyone on your network who has it can open the cockpit. Select Stop (or just close the app) to shut the server down and invalidate the token.

FFB-Bridge Pro desktop Cockpit Web page showing the pairing QR code and URL FFB-Bridge Pro desktop Cockpit Web page showing the pairing QR code and URL
Figure 1. The desktop Cockpit Web page after you press Start: a pairing QR code and URL. Scan it from a phone or tablet on the same network.
The browser never touches your hardware

The cockpit surface doesn't talk to the stick. It sends bounded, high-level tuning commands back to the desktop app, and the desktop stays the authority for entitlement checks, simulator and device state, tuning validation, profile writes, force-feedback safety, and diagnostics. The browser can adjust supported tuning and disarm forces — it cannot arm the stick or send raw hardware commands.

Cockpit Companion Fly view with live effect activity board and force trace Cockpit Companion Fly view with live effect activity board and force trace
Figure 2. The Fly view on the companion: every effect lights up live as you fly, with the force-output trace and the A/B feel slots on the right. (Shown in demo mode — synthetic data, no sim needed.)

A/B tuning

Cockpit Web is built around A/B drafts so exploring a change is low-risk:

  • A is your current baseline feel.
  • B is the editable draft. Cockpit changes apply to B.
  • The desktop can audition the draft live so you feel B while you fly.
  • Keeping or saving B makes the change intentional.
  • Discarding B returns to the baseline.

Exploratory edits never silently become your saved profile — they stay in B until you choose to keep or save them.

Tuning areas

Cockpit Web exposes the same high-level tuning groups as the desktop Tuning page: Master, Stick Feel, Trim, Stick Alive, Ground, Buffets, Engine, Mechanical, Aero Drag, Rate Damping, Stick Drop, Autopilot Follow, and Watchdog. Common controls include master gain, spring strength, force gain, runway rumble, brake shudder, turbulence, overspeed buffet, engine rumble, gear and flap effects, aero-drag cues, and watchdog timing.

A few parameters are guarded because they affect safety or can behave surprisingly. Autopilot Follow and Watchdog, for example, are advanced controls — treat them with care.

Cockpit Companion Tune view with parameter sliders and A/B draft banner Cockpit Companion Tune view with parameter sliders and A/B draft banner
Figure 3. The Tune view: the same parameter catalog as the desktop, with plain-language help under each slider. Every edit becomes a B draft — “Editing A → creates B” — until you keep or save it.

Calm presets

Cockpit Web and Voice Tune share plain-language "calm" presets so you can describe a problem instead of hunting for every related slider:

  • Too harsh — softens centring, airspeed load, the output ceiling, and the major vibration cues.
  • Too much vibration — turns down ground, buffet, turbulence, and engine vibration.
  • Trim feels wrong — restores trim relief and trim authority toward expected behaviour.
  • Too weak — raises the main stick forces and felt effect gains.
  • Taxi rumble too strong — calms ground-roll rumble, brake shudder, bumps, shimmy, and taxi-acceleration cues.

Auditioning and saving profiles

You can audition a profile as a draft, compare it against the baseline, and then keep, discard, or save the result. When a save overwrites an existing profile and Profile History is available, the Pro app takes a rollback snapshot first — see Profile History.

Beta reports from the cockpit

The cockpit surface has a beta report action. Reports are submitted through the desktop app so they can carry current diagnostics and safe, structured cockpit context — view, viewport, session and force state, and recent events. No screenshot or page image is captured. Describe what you were trying to tune, what you expected, and what happened instead.

Troubleshooting

The page is locked

  • Open Pro License, confirm the activation is active, and select Refresh.

The QR code or URL won't open

  • Confirm Cockpit Web is started.
  • Confirm the phone or tablet is on the same local network as the desktop.
  • Try Open locally on the desktop first to rule out the server.
  • Check Windows Firewall or a third-party firewall prompt.
  • Stop and start Cockpit Web to generate a fresh pairing URL.

Changes don't seem to reach the stick

  • Confirm the simulator is connected.
  • Confirm the force-feedback device is connected and active.
  • Check that forces are enabled in the desktop app.
  • Confirm you're editing or auditioning the profile or B draft you think you are.