Tuning

Tuning controls how the aircraft feels. Device selection, physical limits, calibration, and button assignments belong under Hardware.

One rule keeps the interface understandable

If a setting describes the physical device, find it under Hardware. If it describes this aircraft, find it under Tuning.

Start with the essentials

The normal view is deliberately short. Make one change at a time and test the aircraft before opening Advanced.

1. Confirm the selected aircraft profile and aircraft type.
2. Set Master gain for the overall aircraft-force level within the hardware ceiling.
3. Use the standard Advanced controls switch when you need the full model; it sits after Master gain and before Control system.
4. Select the control-system style that matches the aircraft, including Rotorcraft for helicopters.
5. Adjust only the effect groups relevant to that aircraft and the problem you are trying to solve.

Advanced is one deliberate switch

Advanced reveals the detailed effect gains and shaping controls without turning the default page into a wall of sliders. Leave it closed until the essentials are correct.

Turning Advanced on reveals and opens every available effect group at once, creating one continuous scroll. You can collapse individual groups afterward; changing profile family while Advanced stays on opens the newly relevant groups too.

Aircraft type removes irrelevant controls

Rotorcraft profiles show force trim, cyclic damping, and rotor cues. Fixed-wing profiles show their own aerodynamic, ground, trim, and stall controls instead.

Flight-model evidence and guarded fallbacks

Control loading derives feel airspeed from flight-model dynamic pressure in MSFS and X-Plane, so pitot/static or cockpit-indicator failures do not freeze the aerodynamic load. Indicated airspeed remains a guarded fallback when pressure evidence is unavailable.

Surface, rotor, and configuration evidence

Spoiler effects follow actual surface deployment, X-Plane 11 flap fallback is restored, and rotor vibration follows rotor speed and blade count even while windmilling. Missing or implausible optional values use explicit guarded fallbacks.

Control input and local mechanics

Control input chooses how pilot force becomes the aircraft command. Position / displacement is the normal mode. Exact AB9 hardware can use Force Sensing after guided four-direction calibration and validation. Damping, friction, inertia, and progressive stops remain aircraft-profile feel, while Hardware enforces the physical envelope and selects the exact-device renderer.

Autopilot follow

moves a linked control toward the simulator's AP-inclusive command. On MOZA AB6, AB9, and AY210, Follow runs through the base's official firmware mechanism: Authority limits travel, Follow speed controls how quickly the base moves, and pilot hand input still passes through. Other devices render Follow through the app, with the full saved authority on the X-Plane owned-axis path and a bounded 20% cue on MSFS. Independent sidesticks remain excluded.

Engine rumble

Engine rumble follows engine RPM and power evidence. Idle roughness adds a coarser low-speed texture that blends away into cruise without changing steady centering or pitch and roll load.

Edited values stay obvious

Dirty indicators show unsaved edits and reset arrows restore individual defaults. Compare a change in a real flight or use Flight Check to validate the affected force channel under controlled telemetry.

Save to the intended profile

Save only after confirming the correct aircraft profile is selected. Auto-select can then load the values when that aircraft connects.

Tune in a controlled order

For a practical sequence from safe defaults to a finished aircraft profile, continue with the Tuning guide.

See the MOZA family overview