MOZA force-feedback setup

MOZA force-feedback bases (AB6, AB9, AY210 and similar) need a one-time setup in MOZA Cockpit before they feel right with FFB-Bridge. Their DirectInput mode ships with a couple of quirks that the bridge cannot detect or change, so it reminds you instead. Set this up once and you are done. FFB-Bridge opens this page from the first-connect reminder and from Support → Health checks.

Why this is needed

These quirks are in MOZA's DirectInput mode, not in FFB-Bridge. They were documented publicly by the XPForce developer and confirmed by FFB-Bridge user reports: MOZA force feedback support (fsmissioneditor.com). Sincere thanks to the XPForce developer for investigating these MOZA quirks and sharing the findings openly — FFB-Bridge users benefit directly from that work.

1. The centre spring stays on and ignores "autocenter off." In DirectInput mode MOZA's own spring (default 50%) stays enabled and the base ignores the standard command to turn it off. That residual spring blends with the spring FFB-Bridge commands: trim and autopilot positions come out roughly halved, and at low or zero spring strength — parked, stalled, sloppy low-speed controls — the always-on return-to-centre can override and even reverse the bridge's subtle push/pull cues. Symptom: the stick gets lighter as you deflect it, or trim and centring pull the wrong way.
2. Pitch is inverted for one effect type only. For a single effect type the pitch-axis force is inverted, and unlike every other effect it does not follow axis-input inversion. Symptom: roll feels right but pitch feels backwards, or only the pitch axis settles the wrong way.
3. Firmware version always reports "1", so software cannot tell which firmware is installed or whether a fix has shipped. This is why FFB-Bridge reminds rather than auto-corrects — a silent pitch flip would become wrong the moment MOZA fixes the inversion.

One-time MOZA Cockpit setup

Windows MOZA Cockpit is Windows-only. Do this setup on Windows; the saved preset then applies wherever the base is used, including Linux and macOS.

1. Force-Feedback Mode = DirectInput. In MOZA Cockpit → Basic Settings, set the Force-Feedback Mode to DirectInput.
2. Set Spring to 0. On the same page set Spring to 0. (Damper, Inertia and Friction are low by default and can be left alone.) Under Special, make sure Hardware Trim Mode is OFF.
3. Save a preset, auto-switch off. Save these as a new preset and turn Auto-switch preset OFF — otherwise MOZA Cockpit reverts to the spring-on Idle preset and you would have to reselect the preset every session. (MOZA's auto-switch only follows their own plugins, not which app last sent commands.)

If pitch still feels reversed

That is MOZA's pitch-only inversion. Fix it in FFB-Bridge, not by inverting the whole stick:

• Open Settings → Hardware → Axis polarity → Advanced — per-axis fine control.
• If forces are correct on roll but wrong on pitch, tick Invert pitch force direction. If the stick settles or trims the wrong way on pitch only, tick Invert pitch centering instead. Toggle until both the force direction and where the stick settles are correct on each axis independently.

The four advanced toggles invert the directed force and the centring (spring / trim) sign separately, per axis, because some sticks have those two handednesses opposed or have one axis inverted alone.

What FFB-Bridge does about it

• Shows a one-time reminder the first time a MOZA base connects.
• Shows a Support → Health checks row ("MOZA force-feedback setup") whenever a MOZA base is connected, with these steps and a link to this page.
• Cannot read or change the MOZA Cockpit settings or the firmware version, so the setup stays manual.

For more on the validated MOZA AB9 + MH16 hardware, see the MOZA AB9 support page. If something still feels wrong after this setup, export a support bundle from the Support page's Diagnostics tab and open a feedback report.