FPV Controller Settings: Axes, Calibration and Stick Mode

Which axes should you verify?

Verify throttle, yaw, pitch and roll one at a time. Move each stick slowly through its full travel and confirm the simulator indicator follows without jumps or drift. An axis that moves in the wrong direction is an input mapping issue, not a rate issue.

The four axes and what they should do in a typical Acro setup:

Axis	Stick	Correct response	Wrong response looks like
Throttle	Left, vertical	Continuous power, no spring return	Falls to zero when released
Yaw	Left, horizontal	Nose rotates left/right	Craft banks instead of turning
Pitch	Right, vertical	Nose down when pushed forward	Nose climbs on forward input
Roll	Right, horizontal	Banks right when pushed right	Craft yaws instead of banking

If two rows are swapped, the symptom is dramatic and easy to spot. If only one is inverted, it is subtle enough that pilots often blame the flight model for weeks.

Use the controller setup guide for the connection sequence and the pre-flight checklist before your first session.

Why does stick mode matter?

Stick mode changes which physical stick controls throttle, yaw, pitch and roll. The correct mode depends on the pilot’s setup; the important part is that the simulator mapping matches the controller and stays consistent during practice.

Mode 2 — throttle and yaw on the left stick, pitch and roll on the right — is the common configuration in most of Europe and North America. Mode 1 puts throttle and pitch on the left. Neither is more correct, and neither transfers automatically: a radio configured for one mode will produce confusing results in a simulator set to the other.

Do not change stick mode and rates together. Make one change, test it in a safe environment, and write down the result.

What does calibration actually do?

Calibration tells the simulator where the centre, minimum and maximum of each axis are. Without it, the software assumes a nominal range, and any deviation shows up as drift at centre or a dead zone at the extremes.

Three details matter more than the menu path:

• Throttle is absolute, not centred. A radio throttle stays where you leave it. Calibration screens that expect a spring-return axis will never finish, and a simulator that treats throttle as centred will not hold altitude predictably.
• Endpoints matter. Move each stick to full deflection during calibration, not just to a comfortable angle. A miscalibrated endpoint compresses the usable range.
• Recalibrate after a hardware change. New gimbals, a different radio or a firmware update can shift the values slightly.

What is deadband, and when do you need it?

A deadband is a small zone around centre where input is ignored. It exists to stop a worn gimbal from producing constant tiny corrections.

Use it only when you have a reason: an axis that drifts by a degree or two at rest. A deadband added “for smoothness” costs precision exactly where precision matters — slow, framed flight. If the drift is large, the gimbal or the calibration is the problem, and a deadband is masking it.

What belongs in a controller profile?

Keep the device name, USB mode, stick mode, axis mapping and calibration notes together. If you fly more than one simulator, name profiles by simulator and controller so a change in one place does not silently affect another.

A profile note that survives six months looks like this:

Radio A, USB joystick mode, Mode 2, pitch inverted in simulator, calibrated 2026-11. Works in Liftoff and VelociDrone; Uncrashed needs throttle re-mapped.

That single line explains why a new simulator feels wrong before you spend an evening tuning rates to compensate for a mapping error.

When is it not a controller problem?

If the input indicators move correctly but the craft still behaves strangely, the fault is downstream: camera tilt, rates, or the simulator’s own model. Read rates explained before changing numbers, and check Acro mode to confirm you are interpreting the craft’s response correctly.

When the input is stable, move to Acro mode and build control before adding advanced profiles.