MOZA force-feedback setup
FFB-Bridge drives supported MOZA bases on Windows, Linux, and macOS without a separate configuration utility or a special saved preset. The base keeps its own MOZA Cockpit-configured feel until you Arm, and gets it back when you Disarm and when you quit.
No MOZA Cockpit preparation is needed: you do not have to zero the spring or adjust intensity before flying. FFB-Bridge suspends the base's own feel for the flight and returns it afterwards. Keep the vendor utility closed while FFB-Bridge is running; use it for firmware, calibration, lighting, or other maintenance.
AB6 (346e:1002), AB9 (346e:1000), and AY210 (346e:1001) are separate supported device identities with model-specific capability policy. Managed configuration is supported across Windows, Linux, and macOS, and official physical Autopilot Follow is validated on all three bases.
Use MOZA Cockpit to check firmware and calibration for your exact model. Firmware numbers are model-specific: the AY90 tested for 1.5.1 reported 1.1.4.5, so an older AB9 version recommendation must not be applied to every MOZA base. Close Cockpit before a Bridge force session. If Bridge cannot read or verify the supported configuration, resolve that reported condition before arming.
What happens at startup
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 at Arm
Arm is the moment FFB-Bridge claims the feel for the flight. Until then the base feels exactly as its own configuration left it.
- The base's own spring goes to zero; FFB-Bridge centres the control on a datum that trim, force trim, and autopilot follow move.
- Bridge prepares the supported damping, friction, inertia and advanced settings for the exact model. AB6 and AB9 use their managed local mechanics; AY90 and AY210 use their native spring and condition path. The captured originals are kept for restoration.
Close MOZA Cockpit on Windows
If MOZA Cockpit is running, FFB-Bridge asks you to close it and checks again. Two applications must not write the device configuration at the same time.
What FFB-Bridge owns while 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.
- Force output, physical strength, overall gain, and game-force gain are placed in a known state.
- 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.
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
Official physical Follow moves a linked yoke or stick to the simulator's autopilot-commanded control position. Authority limits travel and Follow speed controls how quickly the base moves.
- 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.
Force Sensing input is admitted for exact AB9 hardware after guided four-direction calibration and validation. AB6, AY90, AY210 and generic MOZA-family identities remain in Position mode.
AB6, AB9, and AY210 behavior
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.
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.
MOZA AY90 has its own device identity, axis mapping, spring, trim and restoration handling. Windows testing covered trim and AP Follow in an MSFS 2024 Cessna 172, plus trim in an X-Plane 12 Baron. X-Plane AP Follow and other aircraft, firmware and platform combinations still need their own testing.
Buttons remain explicitly assigned
Use Set up… for Force Trim Release (FTR), optional force-trim on/off, optional trim reset, or beep trim. Each guide prepares device input and captures only your explicit selection. Beep trim accepts one POV hat or four buttons. Assignments are saved for the device; Bridge does not change simulator keybindings.
Disarm and restoration
Disarm, Safety Stop, and a confirmed simulator exit write the exact pre-flight values back and verify them, so between flights the base feels identical to one with FFB-Bridge closed. At quit the journaled originals are restored and verified, and the journal is deleted. The earlier app-owned Standby spring is no longer the resting state; it remains only as a fallback if the hand-back itself fails.
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.
Recovery state is kept on disk. Reconnect the same base and complete a later clean FFB-Bridge session so the journal can be reconciled and restored.
MOZA Cockpit preparation
A special zero-spring Cockpit preset is not required. Bridge captures and prepares the supported settings when you arm, then restores them when the session ends. Keep Cockpit closed so a second application cannot rewrite those settings during flight. Use Cockpit separately for firmware and vendor calibration.
When to use the vendor utility
Use it when updating firmware, calibrating the device, changing lighting, or using features outside FFB-Bridge. Close it before starting a flight session.
Troubleshooting
- Setup will not continue: close MOZA Cockpit completely, including its tray process, then choose Check again.
- Forces feel weak or too strong: set the physical ceiling under Hardware, then use aircraft gains under Tuning. Do not compensate with a second utility.
- 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 restoration fails: export a support bundle before reopening another configuration utility.