Plug in the base. Let FFB-Bridge prepare it.
Version 1.4.2 gives AB6, AB9, and AY210 separate identities and model-specific policy. The base keeps its own configured feel until you Arm; FFB-Bridge owns the forces during flight and writes the exact pre-flight settings back at Disarm and at quit.
AB6, AB9, and AY210 are supported across Windows, Linux, and macOS
AB6, AB9, and AY210 support cross-platform managed configuration, and all three have validated official Autopilot Follow. Input, force output, passive mechanics, and Force Sensing are admitted 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.
Prepare, fly, restore
Read the base and take configuration ownership
At device open FFB-Bridge journals the base's settings and takes configuration ownership only: communication modes, output gates, and the recovery journal. Nothing the hand feels changes; the base keeps its MOZA Cockpit-configured spring, damping, friction, inertia, strength, and advanced settings until you Arm.
Arm hands the feel to the flight model
At Arm the base's own spring gives way to the app's centering, passive damping, friction, and inertia go to MOZA's factory floor on AB6 and AB9, and the advanced settings family is suspended. Exact-device paths provide axes, buttons, POV controls, flight forces, trim, and supported Follow or Force Sensing without assuming that every MOZA model behaves alike.
Return the exact previous settings
Disarm, Safety Stop, and simulator exit write the exact pre-flight values back and verify them, so between flights the base feels the same as with FFB-Bridge closed. Quit restores and verifies the journaled originals and deletes the journal. Recovery evidence survives an interrupted prior session.
On Windows, close MOZA Cockpit before the session
Two programs should not write the base configuration at the same time. FFB-Bridge detects the conflict, explains what to close, and checks again when you are ready.
Ending ownership puts the base back the way it was
Your settings are untouched until you Arm, returned exactly at Disarm, and restored and verified at quit. If a crash or power loss prevents exit work, recovery state is retained for a later clean session.
Hardware setup without taking over your buttons
Raw input fixes held controls such as beep trim, but it does not claim a hat or button. FTR and beep trim remain unassigned until you learn buttons or enable a dedicated hat.
Make the base a natural part of every flight
FFB-Bridge owns the forces only while you are armed; at every other time, and after quit, the feel is your own base configuration.





