Update: FFB-Bridge 1.3 is here
FFB-Bridge 1.3 is live — the largest FFB-Bridge release so far. It introduces first-class helicopter force feedback, managed MOZA hardware, native device paths, a completely rebuilt Flight Check, stronger safety systems, automatic diagnostics, improved profiles, in-app updates, and a much clearer setup and tuning workflow.
FFB-Bridge remains free, local-first, and requires no account. It supports Microsoft Flight Simulator 2020 and 2024 on Windows and Linux, runs alongside the simulator through SimConnect, and never modifies aircraft files or simulator control bindings.
Helicopters are now first-class
Version 1.3 introduces a dedicated rotorcraft control system instead of treating helicopters like lightly modified fixed-wing aircraft.
- Classic force trim holds the cyclic at its trimmed position and releases it while FTR is held.
- An optional force-trim on/off control supports pedestal-style systems that fully release and re-engage the hold.
- Continuous four-way beep trim works with either a POV hat or four ordinary buttons.
- AFCS follow-up trim can move the physical control with the aircraft’s trim system.
- New effects include ETL and VRS cues, rotor rumble, two-per-rev vibration, skid scrape, and retreating-blade-stall buffet.
- Bell 206, H125, and generic helicopter profiles provide starting points for the main trim-system families.
Guided setup now explains and captures FTR, force-trim toggle, POV hats, and button-based trim controls consistently.
MOZA hardware is now managed directly
MOZA AB6, AB9, and AY210 bases are supported on Windows, MacOS, and Linux. No need for Moza Cockpit.
FFB-Bridge now prepares a known hardware session and prevents stored device effects from fighting the live flight model. Settings owned by FFB-Bridge are captured at startup and restored when the application exits normally.
Native HID/PID paths reduce latency and mean MOZA Cockpit does not need to remain open during normal flying.
MOZA firmware 1.1.4.6 or newer is required. MOZA Cockpit is still used for firmware updates, lighting, and maintenance, but it should be closed while FFB-Bridge is running.
Flight Check is now a complete hardware bench test
The rebuilt Flight Check can test:
- Pitch and roll direction
- Centering, damping, and friction
- Trim and autopilot follow-up
- Fixed-wing and helicopter forces
- Runway, engine, buffet, and one-shot effects
- The real Safety Stop path
Each check starts from known temporary settings and restores your previous configuration afterward. Results explain what passed, what failed, and what to adjust next.
Stronger safety systems
Every device now has a Maximum physical strength ceiling that limits all output paths.
Arming begins at zero and ramps in smoothly. Safety Stop can immediately cut gain, stop all effects, latch a visible warning, and require an explicit re-arm. Optional spoken warnings make an emergency stop unmistakable.
Runaway-motion and oscillation detection have also been strengthened, while hardware changes such as polarity or axis swapping are prevented while forces are active.
Setup and diagnostics have been rebuilt
Startup health checks now inspect the selected device, force-feedback readiness, permissions, and output path automatically. Healthy launches remain quiet; actionable problems open a guided review-and-fix experience.
Linux now checks the active input node and verifies complete udev coverage. The repair wizard can install the required rules and explain when FFB-Bridge needs to be restarted.
Button learning is more reliable, POV hats and four-button hat switches are identified separately, and cancelled setup no longer leaves partial assignments behind.
Profiles and tuning are clearer
Hardware settings now own device selection, physical strength, backend, calibration, polarity, and control assignments. Aircraft profiles own how the aircraft should feel.
For normal tuning:
- Choose the closest aircraft profile.
- Adjust Master gain.
- Open Advanced mode only when you want individual effect controls.
The profile library now supports search, sorting, import, duplicate, rename, sharing, and protected starter profiles. Detected aircraft can automatically select a closer starter profile or a saved aircraft binding.
The force model also adds native control friction with separate breakout and sliding resistance, airspeed-dependent glider control feel, improved flap and buffet behavior, and refinements to autopilot back-drive, damping, trim, and device normalization.
Supported hardware
FFB-Bridge 1.3 supports:
- Microsoft SideWinder Force Feedback 2
- Logitech Flight System G940
- Logitech Force 3D Pro
- Logitech WingMan Force 3D
- MOZA AB6
- MOZA AB9
- MOZA AY210
- Experimental joystick-class force-feedback devices through the unlisted-device option
The SideWinder FFB2 now prefers its complete native HID/PID path where validated. Device-specific rendering policies handle springs, damping, friction, periodic effects, and one-shot effects according to each hardware family’s capabilities.
Updating
Your existing profiles and hardware preferences migrate forward.
After installing 1.3:
- Update MOZA firmware first, if applicable.
- Run Flight Check.
- Choose the closest aircraft profile.
- Adjust Master gain before changing individual effects.
Packaged Windows and Linux installations can now download, verify, install, and restart after explicit consent.
Get FFB-Bridge 1.3
Explore and download FFB-Bridge 1.3:
https://ffb-bridge.com/ffb-bridge-1-3
Complete release notes:
https://ffb-bridge.com/releases#1.3.0
Documentation:
https://ffb-bridge.com/docs
Support and feedback:
https://ffb-bridge.com/feedback
Community forum:
https://ffb-bridge.com/community
FFB-Bridge 1.3 is completely free. If it improves your flying or brings new life to hardware you already own, you can help fund continued hardware testing, code signing, hosting, and development here:
https://ffb-bridge.com/support-dev
Thank you to everyone who tested the betas and release candidates, sent support bundles, tested real hardware, and explained when something did not feel right. This release exists because of that feedback.
