MOZA AB9 support

MOZA AB9 + MH16 is now validated for FFB-Bridge.

FFB-Bridge v1.1.2 adds first-class Windows support for the MOZA AB9 FFB Base with the MH16 flight stick. It uses the standard Windows DirectInput/PID force-feedback path, with MOZA-specific direction handling baked in after real simulator validation.

FFB-Bridge Settings page showing hardware compatibility controls FFB-Bridge Settings page showing hardware compatibility controls
Settings → Hardware shows the selected force-feedback device, backend choice, and the live axis-polarity pad used during hardware validation.
Validated device
Device
MOZA AB9 FFB Base + MH16 flight stick
USB VID/PID
346E:1000 / 346E:1002
Validated platform
Windows 10 / 11
Force backend
DirectInput/PID
Backend

Use DirectInput/PID.

The production MOZA path uses Windows DirectInput/PID. Raw HID/PID remains disabled for MOZA until its report IDs and layouts are mapped; the SideWinder FFB2 is still the raw-HID-validated Windows device.

Polarity

MOZA direction is corrected in code.

The AB9 reported inverted force direction during validation, so FFB-Bridge applies a MOZA-specific 180-degree correction before output. You should not need the unlisted-device polarity workaround for this base.

Validation

Tested end-to-end in real sims.

The AB9 + MH16 path was tested through Mock Sim, the Settings hardware test, and real simulator sessions. The direct stick test and the force effects now use the same validated output path.

Setup notes

What to check after installing.

The MOZA AB9 should appear as a supported force-feedback device without enabling unlisted devices. If it does not, send a support bundle so we can compare firmware, product ID, and Windows driver state.

Update MOZA firmware first Use MOZA's own tools to update the base and grip before launching FFB-Bridge.
Confirm the selected device Settings → Hardware should show MOZA AB9 FFB Base as the force-feedback device.
Leave Raw HID/PID off For MOZA, the correct production backend is DirectInput/PID. Raw HID/PID is research-only until a dedicated MOZA report map is proven.
MOZA Cockpit Telemetry mode MOZA Cockpit's Telemetry mode is for MOZA's own sim-fed telemetry path. It is not the normal default mode, and it can leave the base idle during standalone hardware tests. If the AB9 is detected but does nothing, switch MOZA Cockpit back to its normal/default mode and retry.
Use the hardware pad if feel is odd The live axis-polarity pad is still useful for diagnosing unusual firmware or driver behavior, but the normal AB9 path should already follow the puck correctly.

Ready to fly the AB9 with force feedback?

Download v1.1.2 or newer, select the MOZA AB9 device, and keep the Support page nearby for the first validation run.