Best Moza AB6 force-feedback settings for fighters?

For fighter jets, start the Moza AB6 at 60% maximum output, 75% game force-feedback gain, 10–15% damping, 0–5% friction and inertia, and zero hardware spring when the simulator supplies native centring forces. Use a linear axis with no dead zone. For non-FFB aircraft, add a 25–35% centring spring.

These are general flight-simulator starting values, not one universal profile. The simulator, aircraft module, grip weight, extension length and mounting stiffness all change the result. DCS World supports native force feedback, but the quality and behaviour still vary by aircraft; other simulators may provide telemetry-generated effects or only conventional spring resistance.

What Moza AB6 settings should I start with?

The best baseline preserves subtle trim and buffet effects without allowing the strongest forces to dominate the stick. Moza software labels can change, so use the nearest equivalent control if your version uses different wording.

Maximum output is the safety and comfort ceiling. Game FFB intensity determines how much dynamic range remains before effects clip. If every manoeuvre feels equally heavy, reduce game gain first rather than merely lowering the torque ceiling.

A grip extension increases leverage and can make the same setting feel substantially stronger. Begin below these values when using an extension, a heavy grip or a desk mount. Keep any emergency-stop or hands-off protection offered by the base available during initial testing.

Should the AB6 centring spring be enabled?

Disable the AB6 hardware spring when an aircraft supplies native centring, trim and aerodynamic forces. Adding a permanent spring on top creates double centring, masks changing control loads and can make the stick jump towards geometric centre after trimming.

• Conventional or hydraulically assisted fighters: use native FFB, no hardware spring and modest damping. This preserves changes in stick loading and buffet.
• Fly-by-wire fighters: accept the module's intended force behaviour rather than adding exaggerated shake. Some aircraft deliberately provide relatively consistent artificial feel.
• Aircraft without useful FFB output: use a 25–35% hardware spring and 15–20% damping. This is a fallback profile, not native force feedback.
• Force-sensing side-stick aircraft: an AB6 with a moving grip cannot reproduce a real force-sensing controller exactly. If native forces are absent, use a firm but comfortable spring instead of maximum torque.

Trim is the quickest test. In a correctly implemented native-FFB aircraft, trimming changes the force equilibrium or physical neutral point as the module intends. After trimming, relax pressure on the grip; do not force it back to its original geometric centre.

How should fighter-jet axis curves be configured?

A linear axis is the correct starting point for a direct-drive base: use zero curve, full saturation and no dead zone unless the centred input visibly flickers. Add only a 1–2% dead zone for genuine sensor noise.

With a short desktop grip, pilots who overcontrol pitch can try a small curve in 5-point steps, usually stopping by 10. Do not reduce saturation to tame sensitivity because that makes the aircraft reach full control deflection before the grip reaches its physical stop. Avoid applying curves in both Moza software and the simulator.

Before tuning forces, follow a conflict-free HOTAS calibration and binding process. Duplicate pitch or roll assignments are a common cause of apparent FFB faults. DCS users should then use aircraft-by-aircraft DCS axis tuning guidance, because one profile rarely suits every fighter module.

1. Mount and calibrate: secure the base, attach the grip or extension that will actually be used, then calibrate and centre it.
2. Remove duplicate axes: check every connected controller for unwanted pitch, roll and trim bindings.
3. Set a safe first limit: use 40–50% maximum output while confirming input direction, force direction and trim behaviour.
4. Test a representative flight: include low-speed handling, a trimmed cruise condition and a high-load turn rather than judging the profile on the ground.
5. Increase gradually: raise maximum output in 5% steps until normal manoeuvring has useful weight without making recovery inputs uncomfortable.
6. Save per-aircraft profiles: keep separate configurations for native-FFB fighters, fly-by-wire aircraft and modules requiring a spring fallback.

Why does the Moza AB6 oscillate or feel too heavy?

Oscillation normally comes from excessive gain, insufficient damping, mounting movement or a heavy grip feeding momentum back into the base. Reduce game FFB gain by 5–10 points, add about 5 points of damping and check that the base and desk are not flexing.

• Rapid shaking around centre: lower game gain, add damping and remove unnecessary inertia. Do not hide it with a large dead zone.
• Slow, sticky movement: damping or friction is too high. Reduce those effects before changing the control curve.
• All forces feel equally strong: the signal is clipping. Lower the simulator or telemetry-effect gain until small and large loads become distinguishable.
• The stick pushes in the wrong direction: reverse the relevant FFB force axis, not the aircraft's input axis. Test pitch and roll separately at low output.
• Trim snaps back to centre: disable the added hardware spring and check for a second centring effect running alongside native FFB.
• Input works but forces are absent: confirm that the simulator and specific aircraft provide FFB, that force feedback is enabled, and that the correct Moza profile is active.
• The centre is offset: clear trim, recalibrate with the final grip fitted and verify that no second controller is sending trim commands.

If those checks do not restore the expected effects, use our full force-feedback diagnostic sequence to separate hardware, software, simulator and aircraft-specific problems.