Calibration tells the simulator what your controller's physical positions mean. A dead zone tells it which small movements near neutral to ignore. Both influence precision, but they solve different problems: calibration establishes the usable range; a dead zone deals with noise or imperfect centering.
An oversized dead zone can make an analog stick feel almost digital. Nothing happens during the first part of travel, then the aircraft starts reacting suddenly. The aim is a stable neutral with as much useful smooth travel as the hardware allows.
Inspect raw input before flying
Open the controller's live input view and leave the sticks untouched. Identify the axis that corresponds to each physical movement. A trigger, slider or radio switch may rest at an endpoint, so do not assume every axis should sit at zero.
Move each flight axis slowly through its full travel. Look for changing intermediate values, both endpoints and a repeatable resting position. A jumping binary value may mean you selected a button or switch rather than a stick axis. No value at all points toward device recognition or binding rather than a dead-zone setting.
Calibrate neutral and endpoints separately
Drone Horizon's hardware calibration captures neutral and travel ranges, including asymmetric endpoints. During the neutral stage, let centering sticks settle without holding them off-center. During the travel stage, move every axis you intend to use to its physical limits. Follow the on-screen instructions for non-centering throttle rather than inventing a spring center.
When capture finishes, sweep each axis again. A calibrated pitch axis should respond smoothly on both sides of center. If full output appears too early, repeat the endpoint capture. If one direction never reaches full output, look for a missed endpoint or an earlier radio-side limit.
Add only the dead zone the device needs
Increase the relevant dead zone until untouched input remains neutral. Then make the smallest movement you can intentionally repeat. It should produce a small response rather than a large step. Test both sides and diagonals: a setting that feels fine along one axis may be awkward when combining pitch and roll.
Do not use a large dead zone to conceal a persistently miscentered or mechanically damaged stick. Save the profile before making large changes, and compare the raw display with the processed command to locate the problem.
| Symptom | Most useful first check |
|---|---|
| Drift with untouched stick | Neutral capture and small dead zone |
| Half the travel does nothing | Binding type, endpoint range and large dead zone |
| Only one direction reaches full output | Asymmetric calibration |
| Two commands move together | Duplicate binding or radio mix |
| Correct axis, wrong direction | Inversion at one chosen stage |
Keep throttle separate
Manual throttle often spans minimum-to-maximum collective rather than two symmetric directions around hover. Applying a large bipolar center dead zone can discard useful throttle travel. Drone Horizon's normal manual throttle path treats this differently from pitch, roll and yaw; custom profiles still need deliberate review.
Finally, save a named hardware profile, reconnect the device and repeat the sweep. A calibration that only worked before a device-ID change is not a reliable setup. Use controller troubleshooting if the device disappears, or expo tuning once the measured input itself is correct.