MOZA force-feedback setup

FFB-Bridge works with supported MOZA bases on Windows, Linux and macOS, with no MOZA Cockpit preset or preparation. Opening FFB-Bridge does not change how the base feels. FFB-Bridge takes over the feel when you Arm and returns your exact settings when you Disarm.

Recover a MOZA base that will not open →

Restore default force settings on an AB9 →

What happens when FFB-Bridge starts

While Disarmed, Bridge observes the device without changing its force settings. Arm captures the current supported settings, applies the managed force configuration and verifies it before starting aircraft forces. Your configured zero spring is preserved on restoration.

What happens when you Arm

Arm is the moment FFB-Bridge takes over the feel for the flight. Until then the base feels exactly as you set it up in MOZA Cockpit.

• The base's own spring is set aside for the flight. FFB-Bridge centres the control itself, and trim, force trim and autopilot follow move that centre. Autopilot follow uses the base's own built-in follow function.
• FFB-Bridge also takes over the base's damping, friction and inertia and sets them for the aircraft you fly. Your own values are kept so they can be returned after the flight.

Close MOZA Cockpit on Windows

On Windows, keep MOZA Cockpit closed while FFB-Bridge runs. If it is open, FFB-Bridge asks you to close it and checks again, because two applications must not write the base's settings at the same time.

While you are armed

MOZA ownership now also handles retained dynamic stick-pressure and native Airbus-lock settings. Bridge records the supported settings, prepares and verifies them when armed, then restores them on Disarm or normal exit. Close Cockpit and other configuration owners before arming.

• The base's strength and force output are set to known values for the flight.
• While armed, Base resistance supplies the configured damping, friction and inertia minimums. A profile can add resistance above those minimums. Reducing a profile effect to zero or holding FTR does not remove the hardware minimums. Disarm and normal exit restore the captured base settings.
• AB9 uses validated per-axis directional firmware mechanics, AY210 keeps its validated independent HID/PID conditions, and AB6 pairs its validated local mechanics with flight-validated official Autopilot Follow. FFB-Bridge selects capability per exact device and backend.

On the AY210, Bridge also manages the input mappings, direction-dependent response curves, axis configuration and torque response, capturing, verifying and restoring them with the other settings. Free covers essential travel and direction, output limits, device management, calibration and read-only configuration status; advanced overrides saved by earlier beta builds are kept without being applied.

If a base's firmware rejects optional settings, Bridge opens it with those features listed as unavailable on the Hardware page. If Bridge loses control of a MOZA base, it stops forces, disarms and tries to restore your original settings; a restoration that cannot finish is shown on the Dashboard with a prompt to export diagnostics.

The MOZA control centre

Open Hardware → MOZA to set the base-level pitch and roll output limits, the independent Vibration & detail ceiling, damping calibration, and the Base resistance resting minimums. Aircraft feel, effect gains, input mode, passive mechanics, and Autopilot Follow remain in Tuning.

Base resistance

While armed, Base resistance supplies the configured damping, friction and inertia minimums. A profile can add resistance above those minimums. Reducing a profile effect to zero or holding FTR does not remove the hardware minimums. Disarm and normal exit restore the captured base settings.

Ownership and Disarm

Armed aircraft forces use the selected profile. Disarm, Safety Stop, a confirmed simulator exit or normal quit stops Bridge forces and restores the captured native settings, including an original zero spring. Hardware Base resistance minimums apply during the armed session and end after successful restoration. Joystick input remains available.

Set the physical envelope first

Pitch and roll independently bound steady axis authority. Vibration & detail directly bounds rumble, buffet, shudders, and transient cues from 0 to 100% of device command without changing either axis limit. Until set, it follows the lower axis ceiling. All three values are saved for the selected device.

Autopilot Follow

AP Follow moves linked controls toward the simulator's autopilot command. MOZA uses full authority and strength when enabled; Follow speed adjusts movement speed for trim and autopilot. Saved authority and strength remain available for other devices, within simulator and device limits. Independent sidesticks use AP neutral hold instead. Disable AP Follow and disarm if unexpected motion occurs.

• AB6, AB9, and AY210 are all physically validated for official Follow; the AB6 renderer was accepted after live flight validation of its conditioning.
• MSFS uses AP-inclusive yoke position and X-Plane uses total control ratios, with surface-deflection fallback when needed.
• Follow motion is isolated from pilot input, while moving the control by hand still passes through to the simulator.
• A scoped heartbeat clears stale targets automatically when the Follow session expires.

MOZA model-specific behaviour

Capability is selected by the exact device and backend. AB9 has per-axis directional firmware mechanics; AB6 has scalar local mechanics and its own Follow conditioning. AY90 and AY210 use native HID/PID conditions with separate model handling. A model being recognized does not qualify every firmware or simulator combination.

The AB6 force-trim release path now suspends firmware hold while FTR is held and captures the new position before re-engaging. Release removes the trim hold; configured base resistance and other active effects can still be felt.

Base limits here, aircraft feel in Tuning

Hardware owns pitch, roll and vibration limits, damping calibration and the Base resistance minimums used while armed. Tuning owns the aircraft’s damping, friction, inertia, progressive stops, input mode, Follow and other effects. A profile can add resistance above the armed minimums. Disarm restores the captured base configuration.

Tuning guide

Airbus-style AP neutral hold

AP neutral hold adds an Airbus-style centred sidestick while autopilot is engaged. It uses Bridge's shared force path, so it is not restricted to AB9. It is separate from moving-control AP Follow and does not implement a simulator autopilot-disconnect threshold.

Trim compensation

AY90 and AY210 trim compensation supports matching MSFS 2024 aircraft. X-Plane 12.2 and later uses its native trim support for compatible aircraft across supported FFB devices. Aircraft with custom control systems can behave differently.

In MSFS, the cockpit yoke animation can differ from your physical yoke while trim compensation is active. Standard simulator input cannot independently position the animation. Assess trim using pressure relief and aircraft response.

Buttons stay as you assign them

Under Hardware → Helicopter, use Set up… for the controls your trim mode needs: FTR, optional force-trim on/off and optional trim reset. Set up 4-way control… assigns beep trim as one POV hat or four buttons, independently of FTR. Assignments belong to the device and do not change simulator keybindings.

When Arm or restoration is blocked

If Arm is refused, read the displayed reason before retrying. A rejected required MOZA command is identified in the message; optional unsupported firmware settings are shown as unavailable. A lost configuration connection can be recovered at the next explicit Arm attempt.

If restoration is incomplete, Bridge can reconnect to the simulator while remaining Disarmed and showing a recovery notice. It does not resume forces automatically. Resolve the stated condition before selecting Arm. When Bridge cannot confirm that force output stopped, the notice requires an application restart. Keep the recovery journal and export a support bundle if recovery remains blocked.

Recover a MOZA base that will not open

Open Hardware → Device and read the recovery reason. Reconnect the same base, check its USB connection and power, and close MOZA Cockpit and other Free or Pro instances. Select Retry recovery, then confirm the restart. Bridge reopens the selected device and tries to recover its saved original settings.

Keep the recovery files. After an interrupted session or a disconnection, they hold the original settings needed to return this base to its previous state. If recovery remains blocked, export a support bundle before changing settings or trying another utility.

Restore default force settings on an AB9

Use this only when an AB9 cannot open because its saved recovery data cannot be restored. This restores force settings. It does not update firmware or perform a complete factory reset. It replaces custom force strength, spring and force-response curves with defaults for the detected firmware.

1. Connect exactly one AB9. Keep Bridge Disarmed, close MOZA Cockpit and other Bridge instances, and finish any other hardware operation. Recovery is unavailable while Bridge has a physical device open.
2. Under Hardware → Device, select Restore default force settings (AB9)… in the recovery section. Bridge identifies the base and firmware before showing the confirmation.
3. Read the firmware version and replacement warning. Select Confirm restore defaults to proceed, or Cancel to leave settings unchanged. Keep USB and power connected while recovery runs.
4. Wait for Default force settings verified. The result shows where the original recovery files and settings backup were saved. Select Restart and reopen AB9 and confirm the restart; recovery itself does not arm the base.

Calibration, travel limits, input mappings, identity, activation and lighting are preserved. Bridge backs up the original recovery files and readable settings before writing, verifies the restored force settings, and creates a replacement recovery journal. Do not delete the backup.

Default sets are included for firmware 1.1.1.46, 1.1.2.5, 1.1.2.10, 1.1.2.12, 1.1.3.4, 1.1.4.6 and 1.1.5.2. The version must match exactly and the device checks must pass; an entry in this list does not guarantee that old firmware supports every required read. No nearby-version defaults are substituted.

If recovery fails, keep the same base connected and read the displayed error. The original backups remain. A retry must use the same device and firmware. Export a support bundle if it remains blocked; default-force recovery cannot repair every USB, firmware or hardware fault.

Disarm and your settings

When you Disarm, after a Safety Stop and when the simulator closes, FFB-Bridge stops its forces and returns the exact settings you had before you armed. When you quit, it checks that your settings are back before it removes its recovery files. An unplugged base gets its settings back once you reconnect it. If something cannot be returned, FFB-Bridge keeps the recovery files and tells you.

While Disarmed, Bridge observes the device without changing its force settings. Arm captures the current supported settings, applies the managed force configuration and verifies it before starting aircraft forces. Your configured zero spring is preserved on restoration.

Preparing the base in MOZA Cockpit

There is nothing to prepare. You do not need a special preset or a zero spring. Keep MOZA Cockpit closed during a flight so the two applications do not change the base's settings at the same time. FFB-Bridge Pro adds MOZA Base, which sets up the base's own feel, travel stops, buttons and lights from inside FFB-Bridge.

When to use MOZA Cockpit

MOZA Cockpit is MOZA's own utility for the base, and MOZA Racing and FFB-Bridge have an official partnership. Use MOZA Cockpit while FFB-Bridge is closed to update firmware, calibrate the base, change lighting or use other MOZA features. Close it again before you start a flight with FFB-Bridge.

Troubleshooting

• Setup does not continue: close MOZA Cockpit completely, including its icon in the system tray, then choose Check again.
• Forces feel too weak or too strong: set the base's strength limit under Hardware, then adjust the aircraft under Tuning. Leave the strength in other utilities unchanged.
• Use one physical hat-shaped control for top, bottom, left, and right. FFB-Bridge listens to both input formats and saves either one POV hat or four buttons—whichever the device actually reports. The tested AY210 uses four buttons. Cancel or failed verification restores the previous assignment.
• Setup or restoring settings fails: export a support bundle before you open another configuration utility.

See the MOZA overview