Update: FFB-Bridge v1.4.1 Stable is live
FFB-Bridge v1.4.1 Stable is now available.
This release substantially improves MOZA flight-base support, physical Autopilot Follow, force safety, helicopter force trim, simulator accuracy, aircraft effects, and hardware diagnostics.
MOZA AB6, AB9, and AY210
FFB-Bridge now treats the AB6, AB9, and AY210 as separate devices, with behavior selected for the exact connected hardware.
Supported MOZA settings are recorded before the session, deliberately configured while FFB-Bridge owns the device, and restored when the app closes or the device changes. Recovery information is also retained if a previous session was interrupted.
On validated hardware:
- AB9 and AY210 preserve independent pitch and roll force proportions
- AB9 supports configurable Force Sensing mode
- AB9 and AY210 support official physical Autopilot Follow
- AB6 remains supported for normal input, force output, managed configuration, and local effects
AB6 physical Autopilot Follow remains disabled because its current tested firmware did not reproduce the validated AB9 and AY210 behavior reliably.
Physical Autopilot Follow
On the MOZA AB9 and AY210, the base can now physically move the connected stick or yoke to the position commanded by the autopilot.
Pitch and roll remain independent, inactive axes are released, and the controls still allow deliberate pilot pass-through.
Follow speed controls how quickly the hardware moves. Authority controls how far it may travel.
FFB-Bridge now follows the control position actually commanded by MSFS, fixing cases where the aircraft was visibly pitching or banking while the physical control remained centered or moved incorrectly.
Legacy force-feedback devices retain their existing software-rendered autopilot behavior, now with a firmer breakout-style hold that remains deliberately overridable.
Helicopter force trim
Helicopter force trim now captures one consistent physical and simulator control position.
This removes the unwanted pitch-up pull that could occur after releasing force trim and allows the hold to use the device’s available strength independently of the normal in-flight output ceiling.
MOZA rotorcraft support includes:
- Force trim on/off assignments
- One-press trim reset
- Configurable hold strength and breakout
- Beep trim
- Firmware-local position holding
- Assignments from a separate button box or controller
More accurate aircraft forces
Control loading now follows the aircraft’s actual aerodynamic state through flight-model dynamic pressure.
This means the controls can continue to feel correctly loaded even if the cockpit airspeed indicator or pitot-static system is failed, frozen, or unpowered.
The update also corrects X-Plane pressure units and audits spoiler, flap, rotor, autopilot, and control-surface telemetry.
Improved vibration and aircraft detail
Engine rumble now has more character at low power, with a new idle-roughness texture that smooths into cruise.
Helicopter vibration follows rotor speed and blade count more accurately, including windmilling rotors, two-per-rev vibration, and a tunable retreating-blade-stall effect.
Aircraft vibration, bumps, buffet, and engine effects now follow the aircraft profile and selected pitch/roll output limits without an additional hidden detail cap.
New Cessna 208B Grand Caravan profile
The Cessna 208B now has a dedicated sourced profile.
It is lighter in the pattern, more deliberate in cruise, firmer in roll than pitch, and uses a 150 KIAS reference with restrained Caravan-specific mechanical cues.
Safer force handling
Safety Stop is now a true latched force cut.
When triggered, it removes device gain, stops active effects, and requires an explicit re-Arm before forces can return. The sustained-oscillation detector also responds sooner on strong hardware.
Additional safety improvements include:
- One owned output path for all normal flight force
- Device-aware motion protection
- Gradual force application during bench tests
- Conservative test ceilings for strong or uncharacterized bases
- Reduced outward force during fast movement near travel limits
- Output-heartbeat detection for a stalled force loop
- Complete device restoration before process exit
When disarmed, generic devices return to their normal centering behavior. Managed MOZA bases enter a gentle Standby spring while aircraft forces, trim, Follow, resistance, and vibration remain off.
Better Flight Check and diagnostics
Flight Check now exercises more of the real signal path.
Guided speed and RPM sweeps can test aerodynamic loading and engine effects without requiring a live flight. Force direction, polarity, backend behavior, and saved settings now use one consistent convention.
Support bundles also record:
- Simulator and aircraft identity
- Selected profile
- Why that profile was selected
- Saved aircraft bindings
- Installed profile inventory
- Hardware and force-path diagnostics
Logitech improvements
Linux support is improved for the:
- Logitech Flight System G940
- Logitech Force 3D Pro
- Logitech WingMan Force 3D
Devices whose Linux driver exposes constant force but no native Spring can now receive synthesized centering and software-rendered periodic effects.
The G940 also receives corrected autocenter, Spring stop/restore, and force-trim release behavior.
Supported simulators and platforms
FFB-Bridge supports:
- Microsoft Flight Simulator 2024
- Microsoft Flight Simulator 2020
- X-Plane 11 and 12
- Windows
- Linux
- macOS for X-Plane on Apple Silicon
Updating
Your existing profiles and hardware settings are preserved.
After installing v1.4.1:
- Open Hardware and confirm the selected force-feedback device.
- Review your pitch and roll output limits.
- Run Flight Check, especially with a strong MOZA base.
- Confirm trim, force-trim, and Autopilot Follow assignments before relying on them in flight.
Download FFB-Bridge 1.4.1
Download:
https://ffb-bridge.com/download
Complete release notes:
https://ffb-bridge.com/releases#1.4.1
Documentation:
Support and feedback:
https://ffb-bridge.com/feedback
FFB-Bridge remains free.
Thank you to everyone who tested the release candidates, submitted support bundles, and helped validate the physical hardware behavior behind this release.